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