Re: autonomous transactions

Gregory Stark <stark@enterprisedb.com>

From: Gregory Stark <stark@enterprisedb.com>
To: "Neil Conway" <neilc@samurai.com>
Cc: "Pavel Stehule" <pavel.stehule@gmail.com>, "Alvaro Herrera" <alvherre@commandprompt.com>, "Roberts\, Jon" <Jon.Roberts@asurion.com>, <pgsql-hackers@postgresql.org>
Date: 2008-01-23T09:30:54Z
Lists: pgsql-hackers
"Neil Conway" <neilc@samurai.com> writes:

> 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.

I think the hard part would be error handling. You have to be able to catch
any errors and resume the outer transaction.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's 24x7 Postgres support!