Bruce Momjian wrote:
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.
Interesting Oracle doesn't support RELEASE or savepoint levels:
T271, Savepoints Oracle supports this feature, except:
* Oracle does not support RELEASE SAVEPOINT.
* 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
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html