Skip site navigation (1) Skip section navigation (2)

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "news(dot)postgresql(dot)org" <smith(at)pooteeweet(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Date: 2007-01-02 16:42:36
Message-ID: 20070102164236.GC21867@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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

In response to

Responses

pgsql-hackers by date

Next:From: Lukas Kahwe SmithDate: 2007-01-02 16:48:15
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Previous:From: news.postgresql.orgDate: 2007-01-02 16:34:05
Subject: Re: TODO: Add a GUC to control whether BEGIN inside

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group