Re: TODO: Add a GUC to control whether BEGIN inside

news.postgresql.org wrote:

> While we are on the topic, I have implemented a poor mans nested 
> transaction feature into my database access layer. essentially 
> subsequent calls to begin a transaction after the initial begin simply 
> increase an internal counter and set a savepoint. as you commit the 
> transactions the counter is decreased and the savepoints are released. 
> maybe this could be implemented inside postgresql to make the life of 
> modular programmers easier?

Yeah, it's called "SAVEPOINT foo" and "RELEASE foo".

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support