From: | Morris de Oryx <morrisdeoryx(at)gmail(dot)com> |
---|---|
To: | Pepe TD Vo <pepevo(at)yahoo(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Merge statement |
Date: | 2019-09-21 05:57:32 |
Message-ID: | CAKqnccjTyo9TEYMp1YdFvf9RCOJv7vg5dOYKd852vOsM7P7e2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2019-09-21 12:20:10 | Re: Merge statement |
Previous Message | Pepe TD Vo | 2019-09-20 22:15:57 | Re: Merge statement |