On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova <jaime.casan...@2ndquadrant.com> wrote: > > On 30 August 2016 at 23:10, Joel Jacobson <j...@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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
