| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Nested Transactions, Abort All |
| Date: | 2004-07-10 07:50:32 |
| Message-ID: | 40EF9FC8.2000509@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
>Interesting Oracle doesn't support RELEASE or savepoint levels:
>
>T271, Savepoints Oracle supports this feature, except:
>
> * Oracle does not support RELEASE SAVEPOINT.
>
>
Yes, and IMHO it's just some housekeeping stuff, informing the backend
that you'll never want to rollback to that savepoint any more. If there
are no resources to release internally, a noop.
> * Oracle does not support savepoint levels.
>
>
The levels are created implicitely, because a rollback to savepoint1
will rollback *all* work done since then. This effectively makes all
subsequent savepoints children of the first. The effect of RELEASE
SAVEPOINT would be to restrict the tree depth, by concentrating all
released savepoints into their parents.
>
>This is not a nested transaction. It is "autonomous" meaning it can
>commit independent of the outer transaction:
>
I like that too... in 7.6.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-07-10 07:59:14 | Re: bug in DROP TABLESPACE |
| Previous Message | Andreas Pflug | 2004-07-10 07:34:26 | Re: Nested Transactions, Abort All |