From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mike Rylander <miker(at)purplefrog(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Nested Transactions, Abort All |
Date: | 2004-07-10 19:56:34 |
Message-ID: | 20040710195634.GA5238@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jul 10, 2004 at 09:46:00PM +0200, Dennis Bjorklund wrote:
> One can have many different semantics, here are 3 versions:
>
> 1) You release savepoints in any order
> 2) You release savepoints in reverse order
> 3) You release any savepoints and later ones then the
> one you released are automatically released.
>
> I don't see any of these as absurd. The ansi spec uses number 3.
Ah-ha, now I see what I failed to see previously: all later savepoints
are also released! This makes a lot more sense. So "release" is
exactly like commit nested, allowing several levels to be "committed".
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La fuerza no está en los medios físicos
sino que reside en una voluntad indomable" (Gandhi)
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-07-10 20:01:13 | Re: Recovery Features |
Previous Message | Dennis Bjorklund | 2004-07-10 19:46:00 | Re: Nested Transactions, Abort All |