From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Basic subtransaction facility |
Date: | 2004-04-29 17:06:34 |
Message-ID: | 200404291706.i3TH6Y107047@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Manfred Koizar wrote:
> On Wed, 28 Apr 2004 12:02:44 -0400, Alvaro Herrera
> <alvherre(at)dcc(dot)uchile(dot)cl> wrote:
> >In fact, I think we should mark ERROR as aborting the whole transaction
> >tree, and create a new level which would abort the innermost
> >subtransaction. We would then change whatever is appropiate to the new
> >elevel. Doing otherwise would leave us open to unexpected conditions
> >causing only subtrans abort, which could lead to unreliable behavior.
>
> Why? Subtransaction commit propagates an error state to the parent
> transaction. And if a subtransaction is rolled back the parent can
> continue cleanly no matter what was the reason for the subtrans abort.
I think his point was that there are some errors that should abort the
outer transaction too. I think Alvaro mentioned out of memory, but that
is a FATAL error. Alvaro, what error were you thinking of that should
abort the outer transaction?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-04-29 17:29:07 | Re: Basic subtransaction facility |
Previous Message | Manfred Koizar | 2004-04-29 16:42:31 | Re: Basic subtransaction facility |