Re: Autonomous subtransactions - Mailing list pgsql-hackers

From Marti Raudsepp
Subject Re: Autonomous subtransactions
Date
Msg-id CABRT9RC4kzL+qBwbNCBFtWPUyzMZHQ=xjs0pE2pcPoG7Xsx4RA@mail.gmail.com
Whole thread Raw
In response to Re: Autonomous subtransactions  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Autonomous subtransactions  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Autonomous subtransactions  (Gianni Ciolli <gianni.ciolli@2ndquadrant.it>)
List pgsql-hackers
On Mon, Dec 19, 2011 at 20:34, Simon Riggs <simon@2ndquadrant.com> wrote:
> It's not clear to me why you think there would be a limitation to
> exactly 2 autonomous transactions.

Sorry my bad, I didn't read the proposal carefully. Nesting does
indeed allow multiple autonomous subtransactions.

Maybe that's just my paranoia, but the fact that subtransactions
aren't named means it's pretty easy to accidentally get "out of step"
and commit the wrong subtransaction. I see app developers often
messing up BEGIN/COMMIT/ROLLBACK already. This is why I like the
SAVEPOINT style; it's obvious when there's a bug.

(I do realize that allowing subtransactions to commit out of order
also makes it failure prone)

Regards,
Marti


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Page Checksums
Next
From: Richard Huxton
Date:
Subject: Re: Escaping ":" in .pgpass - code or docs bug?