| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Roberts\, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autonomous transactions |
| Date: | 2008-01-23 09:30:54 |
| Message-ID: | 87zluw99dd.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Neil Conway" <neilc(at)samurai(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2008-01-23 10:24:41 | Re: Errors with run_build.pl - 8.3RC2 |
| Previous Message | Pavel Stehule | 2008-01-23 09:05:50 | Re: autonomous transactions |