From: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Thomas Swan <tswan(at)idigx(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Nested Transactions, Abort All |
Date: | 2004-07-07 06:16:56 |
Message-ID: | Pine.LNX.4.44.0407070806560.2838-100000@zigo.dhs.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 6 Jul 2004, Alvaro Herrera wrote:
> We can later implement savepoints, which will have "SAVEPOINT foo" and
> "ROLLBACK TO foo" as interface. (Note that a subtransaction is slightly
> different from a savepoint, so we can't use ROLLBACK TO <foo> in
> subtransactions because that has a different meaning in savepoints).
What is the semantic difference?
In my eye the subtransactions and the savepoints are basically the
same thing except the label that is used. If that is the only difference?
why are we implementing our own extension for subtransactions instead of
implementing this standard feature.
Of course the label stuff is a little more complicated, but all the really
hard parts should be the same as what have already been done. The most
naive implementation of the labels is to have a mapping from a label to
the number of subcommit (for RELEASE SAVEPOINT) or subrolllbacks (for
ROLLBACK TO SAVEPOINT) to execute.
--
/Dennis Björklund
From | Date | Subject | |
---|---|---|---|
Next Message | Honza Pazdziora | 2004-07-07 07:03:39 | Re: Adding VERSION to startup log output |
Previous Message | Greg Stark | 2004-07-07 05:36:53 | Re: Nested Transactions, Abort All |