| From: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autonomous transactions |
| Date: | 2016-08-31 04:41:36 |
| Message-ID: | CAJGNTeNCD1DgtG2KE_YsbCJbeBipLdFXZFHDYMUog7E+KO4T_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30 August 2016 at 23:10, Joel Jacobson <joel(at)trustly(dot)com> wrote:
>
> There should be a way to within the session and/or txn permanently
> block autonomous transactions.
>
This will defeat one of the use cases of autonomous transactions: auditing
>
> Coding conventions, rules and discipline are all good and will help
> against misuse of the feature, but some day someone will make a
> mistake and wrongly use the autonomous transaction and cause unwanted
> unknown side-effect I as a caller function didn't expect or know
> about.
>
well, if the feature is not guilty why do you want to put it in jail?
--
Jaime Casanova www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-08-31 04:58:55 | Re: standalone backend PANICs during recovery |
| Previous Message | Michael Paquier | 2016-08-31 04:32:26 | Re: ICU integration |