| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Serge Rielau <srielau(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autonomous transactions |
| Date: | 2016-09-15 12:53:43 |
| Message-ID: | 605e2970-428d-9b55-5ea9-6ce231edc02b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/3/16 9:08 AM, Serge Rielau wrote:
> Interestingly, despite being supported in PL/SQL on nested BEGIN END blocks,
> we nearly exclusively see AT’s covering the entire function or trigger.
Oracle only supports an entire PL/SQL function to be declared
autonomous. But it was pretty easy in my implementation to allow that
for arbitrary blocks. In fact, it would have been harder not to do that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2016-09-15 12:58:05 | Re: Declarative partitioning - another take |
| Previous Message | Peter Eisentraut | 2016-09-15 12:49:13 | Re: autonomous transactions |