Re: BUG #15977: Inconsistent behavior in chained transactions - Mailing list pgsql-hackers

From fn ln
Subject Re: BUG #15977: Inconsistent behavior in chained transactions
Date
Msg-id CA+99BHqSVBpJZ9pD=QczBs5L8KfuAvi3rYkKRbXXNE0cADoB+A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15977: Inconsistent behavior in chained transactions  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: BUG #15977: Inconsistent behavior in chained transactions
List pgsql-hackers
> Looking at the latest patch, the comment blocks on top of TBLOCK_STARTED
> and TBLOCK_IMPLICIT_INPROGRESS in EndTransactionBlock() need an update
> to mention the difference of behavior with chained transactions.  And
> the same comment rework should be done in UserAbortTransactionBlock()
> for TBLOCK_IMPLICIT_INPROGRESS/TBLOCK_STARTED?
I made another patch for that.
I don't have much confidence with my English spelling so further improvements may be needed.

> If it is too much a change and potential regression, then I think that the
> "and chain" variants should be consistent and just raise warnings.
We don't have an exact answer for implicit transaction chaining behavior yet.
So I think it's better to disable this feature until someone discovers the use cases for this.
Permitting AND CHAIN without a detailed specification might cause troubles in future.
Attachment

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions
Next
From: Andres Freund
Date:
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions