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

From Bruce Momjian
Subject Re: Nested Transactions, Abort All
Date
Msg-id 200407091614.i69GEEU27139@candle.pha.pa.us
Whole thread Raw
In response to Re: Nested Transactions, Abort All  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
Responses Re: Nested Transactions, Abort All  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-hackers
Pavel Stehule wrote:
> > 
> > An 'END SUB' after a 'BEGIN SUB' in plpgsql could be required, and could
> > mean start/end block and subtx. I do not really see a downside.
> > But, it would imho only make sense if the 'END SUB' would commit sub
> > or abort sub iff subtx is in aborted state (see my prev posting)
> > 
> > Andreas
> > 
> Hello,
> 
> is good idea use keywords "begin sub" and "end sub"? Programmers like me 
> will be an problems with reading and writing SP, because begin sub and 
> mostly end sub are keywords from visual basic with different sense. 
> BEGIN SUBTRANSACTION and END SUBTRANSACTION is longer but more readable

I think we agreed on BEGIN NESTED/COMMIT NESTED, and START NESTED
TRANSACTION and COMMIT NESTED TRANSACTION.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: User Quota Implementation
Next
From: "Jonah H. Harris"
Date:
Subject: Re: User Quota Implementation