Re: audit table containing Select statements submitted - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: audit table containing Select statements submitted
Date
Msg-id 65937bea0605161952o27a8afaev1e23c1dfc2b0f67c@mail.gmail.com
Whole thread Raw
In response to Re: audit table containing Select statements submitted  (Josh Berkus <josh@agliodbs.com>)
Responses Re: audit table containing Select statements submitted
Re: audit table containing Select statements submitted
List pgsql-hackers
    Do we have any plans of introducing 'AUTONOMOUS TRANSACTION'  like feature?
   Again, it might not be a part of the standard.... but it is very
helpful in situations like these!!! You can run a trigger with an
autonomous transaction attached to it, which guarantees that the work
done by trigger persists even though the calling transaction rolls
back (potentially a hacker trying to cover his tracks)!!!

(http://asktom.oracle.com/~tkyte/autonomous/index.html)

Gurjeet.

On 5/16/06, Josh Berkus <josh@agliodbs.com> wrote:
> Doug,
>
> > But what if the user calls the access function, sees the data, then
> > issues a ROLLBACK?  The audit record would be rolled back as well (as
> > Tom pointed out earlier).


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PL/pgSQL 'i = i + 1' Syntax
Next
From: David Wheeler
Date:
Subject: Re: PL/pgSQL 'i = i + 1' Syntax