Re: autonomous transactions - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: autonomous transactions
Date
Msg-id CAASwCXfaC7dAfj-NOQMD=NBMBktWHBLc6AUn89rk8bzfdd-Etg@mail.gmail.com
Whole thread Raw
In response to Re: autonomous transactions  (Jaime Casanova <jaime.casanova@2ndquadrant.com>)
Responses Re: autonomous transactions  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: autonomous transactions  (Simon Riggs <simon@2ndquadrant.com>)
Re: autonomous transactions  (Vik Fearing <vik@2ndquadrant.fr>)
List pgsql-hackers
On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova
<jaime.casanova@2ndquadrant.com> wrote:
>
> On 30 August 2016 at 23:10, Joel Jacobson <joel@trustly.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.



pgsql-hackers by date:

Previous
From: Maksim Milyutin
Date:
Subject: Re: [WIP] Patches to enable extraction state of query execution from external session
Next
From: Tom Lane
Date:
Subject: Re: Leftover member in openssl part of Port struct