| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(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 13:09:21 |
| Message-ID: | CAASwCXfaC7dAfj-NOQMD=NBMBktWHBLc6AUn89rk8bzfdd-Etg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova
<jaime(dot)casanova(at)2ndquadrant(dot)com> wrote:
>
> 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
My idea on how to deal with this would be to mark the function to be
"AUTONOMOUS" similar to how a function is marked to be "PARALLEL
SAFE",
and to throw an error if a caller that has blocked autonomous
transactions tries to call a function that is marked to be autonomous.
That way none of the code that needs to be audited would ever get executed.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-31 13:12:40 | Re: Leftover member in openssl part of Port struct |
| Previous Message | Maksim Milyutin | 2016-08-31 13:09:15 | Re: [WIP] Patches to enable extraction state of query execution from external session |