From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Joel Jacobson <joel(at)trustly(dot)com> |
Cc: | Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, 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:27:55 |
Message-ID: | CAFj8pRAS03iwBJoJFkYzwvp9Ytw8FeB-Cm8WMKHD2XtRfATV7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2016-08-31 15:09 GMT+02:00 Joel Jacobson <joel(at)trustly(dot)com>:
> 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.
>
I like this idea - it allows better (cleaner) snapshot isolation.
Regards
Pavel
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-08-31 13:32:00 | Re: WAL consistency check facility |
Previous Message | Simon Riggs | 2016-08-31 13:24:13 | Re: [COMMITTERS] pgsql: Fix pg_receivexlog --synchronous |