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

From Fabien COELHO
Subject Re: BUG #15977: Inconsistent behavior in chained transactions
Date
Msg-id alpine.DEB.2.21.1909071900170.15836@lancre
Whole thread Raw
In response to Re: BUG #15977: Inconsistent behavior in chained transactions  (fn ln <emuser20140816@gmail.com>)
Responses Re: BUG #15977: Inconsistent behavior in chained transactions
List pgsql-hackers
>> Now, I'd prefer error in all cases, no doubt about that, which might be
>> considered a regression. A way around that could be to have a GUC decide
>> between a strict behavior (error) and the old behavior (warning).
>
> I think it's more better to have a GUC to disable implicit transaction
> 'block' feature, because that's probably the root of all issues.

Hmmm… I'm not sure that erroring out on "SELECT 1" because there is no 
explicit "BEGIN" is sellable, even under some GUC.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: fn ln
Date:
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions
Next
From: fn ln
Date:
Subject: Re: BUG #15977: Inconsistent behavior in chained transactions