Re: Merge statement
Carrie Berlin <[email protected]> Sat, 21 Sep 2019 08:50:14 -0400
| Newsgroups | gmane.comp.db.postgresql.admin |
|---|---|
| Message-ID | <CAPyCnLnpz+y3dnxyoM1PnF_isr=wmA44ttrkDooKOaE3kOZaJg@mail.gmail.com> |
I know that it is a procedure and not a function, On Sat, Sep 21, 2019 at 08:20 Pepe TD Vo <[email protected]> wrote: > Thank you all. Will look into it on Monday. > > Have a pleasant weekend. > > V/r, > > Bach Nga > > Sent from my iPad > > On Sep 21, 2019, at 1:57 AM, Morris de Oryx <[email protected]> > wrote: > > Postgres has had stored functions for ages, but only added stored > procedures in version 11. Historically, you'll see people calling stored > functions in Postgres "stored procedures" as that's what other folks call > them. It didn't matter because Postgres only had the one thing. For what's > new in Postgres 11 stored procedures, here's a place to look: > > > https://severalnines.com/database-blog/overview-new-stored-procedures-postgresql-11 > > The change you're referring to is that a stored procedure (but not a > function) has the ability to manage its own transaction blocks. > > I actually have no clue...I've only read about the new stored procedures. > But if you're coming from Oracle, you're likely looking for PG 11 stored > procedures, at least some of the time. > >>