Re: Nested Transactions, Abort All - Mailing list pgsql-hackers

From Dennis Bjorklund
Subject Re: Nested Transactions, Abort All
Date
Msg-id Pine.LNX.4.44.0407102235100.2838-100000@zigo.dhs.org
Whole thread Raw
In response to Re: Nested Transactions, Abort All  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Nested Transactions, Abort All
List pgsql-hackers
On Sat, 10 Jul 2004, Bruce Momjian wrote:

> > > >     SAVEPOINT == BEGIN NESTED
> > > >     RELEASE SAVEPOINT == COMMIT NESTED
> > > >     ROLLBACK TO SAVEPOINT == ROLLBACK NESTED
> > > 
> > > Here it should be:
> > > 
> > >     ROLLBACK TO SAVEPOINT == ROLLBACK NESTED; SAVEPOINT;
> > > 
> > > And just to clearify, this is an extension to the spec that we then have
> > > to support for a long time. Adding this now and then replacing it with the
> > > standard syntax is not very sexy. If we add this we should support 
> > > it "for ever".
> 
> Sorry, I confused folks.  I should have corrected this line too:
> 
> > >     ROLLBACK TO SAVEPOINT == ROLLBACK NESTED; BEGIN NESTED;

Hmm, yes. Correct.

Luckily, we already had: SAVEPOINT == BEGIN NESTED so it all worked out 
:-)

> It is not a non-standard behavior.  It is only an implementation detail
> used internally that allows nested transactions to implement savepoints.

The non-standard part I was talking about was the savepoints without
names, and that is what we should support for ever if we introduce them. 

-- 
/Dennis Björklund



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Nested Transactions, Abort All
Next
From: Bruce Momjian
Date:
Subject: Re: Nested Transactions, Abort All