Re: autonomous transactions - Mailing list pgsql-hackers

From Neil Conway
Subject Re: autonomous transactions
Date
Msg-id 1201076812.6730.6.camel@goldbach
Whole thread Raw
In response to Re: autonomous transactions  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Responses Re: autonomous transactions  (Gregory Stark <stark@enterprisedb.com>)
Re: autonomous transactions  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Tue, 2008-01-22 at 20:53 +0100, Pavel Stehule wrote:
> And there is most important question about data visibility - is
> autonomous transaction independent on main transaction (isolation)?

>From looking at how Oracle does them, autonomous transactions are
completely independent of the transaction that originates them -- they
take a new database snapshot. This means that uncommitted changes in the
originating transaction are not visible to the autonomous transaction.

On Wed, 2008-01-23 at 08:13 +0000, Simon Riggs wrote:
> Yes, I think autonomous transactions should be on the TODO. They're
> useful for
> - error logging
> - auditing
> - creating new partitions automatically

I think they would also be useful to implement procedures that perform
DDL operations or COMMITs / ROLLBACKs.

-Neil




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: autonomous transactions
Next
From: "Pavel Stehule"
Date:
Subject: Re: autonomous transactions