Re: Nested Transactions, Abort All

From: "Scott Marlowe" <smarlowe(at)qwest(dot)net>
To: "Greg Stark" <gsstark(at)mit(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nested Transactions, Abort All
Date: 2004-07-07 15:27:28
Message-ID: 1089214048.14278.7.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2004-07-06 at 23:36, Greg Stark wrote:
> "Scott Marlowe" <smarlowe(at)qwest(dot)net> writes:
>
> > Why not rollback all or commit all?
> >
> > I really really don't like subbegin and subcommit. I get the feeling
> > they'll cause more problems we haven't foreseen yet, but I can't put my
> > finger on it.
>
> Well I've already pointed out one problem. It makes it impossible to write
> generic code or reuse existing code and embed it within a transaction. Code
> meant to be a nested transaction within a larger transaction becomes
> non-interchangeable with code meant to be run on its own.

Would a rollback N / abort N where N is the number of levels to rollback
/ abort work?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pierre Emmanuel Gros 2004-07-07 16:26:24 storage manager
Previous Message Scott Marlowe 2004-07-07 15:26:07 Re: Nested Transactions, Abort All