From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Barry Lind <blind(at)xythos(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Nested transactions |
Date: | 2004-06-18 22:47:10 |
Message-ID: | 4213.1087598830@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-patches |
Barry Lind <blind(at)xythos(dot)com> writes:
> I like the functionality of nested transactions, I just think that there
> needs to be different commands other than BEGIN/COMMIT to work with
> them. So that there is no possiblity for misunderstanding what COMMIT
> really means.
There's something to be said for that view. Another thing in its favor
is that if we choose names like SUBBEGIN and SUBCOMMIT, then we get rid
of the syntax conflict with plpgsql's BEGIN/END. A function cannot
legally issue a true COMMIT, as it has to be inside an outer transaction
--- so it only needs to be able to say SUBBEGIN and SUBCOMMIT.
I'm not at all wedded to those particular names, of course. Just
thinking that it'd simplify life if they were spelled differently than
BEGIN and END.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2004-06-18 23:07:03 | Re: Prepare Statement |
Previous Message | Kris Jurka | 2004-06-18 21:47:53 | Re: Prepare Statement |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2004-06-18 22:53:13 | Re: Tablespace patch review |
Previous Message | Gavin Sherry | 2004-06-18 22:33:49 | Re: Tablespace patch review |