Re: BUG #16867: savepoints vs. commit and chain - Mailing list pgsql-bugs

From Vik Fearing
Subject Re: BUG #16867: savepoints vs. commit and chain
Date
Msg-id 10736536-3146-7f50-fdf6-aa5390e9c011@postgresfriends.org
Whole thread Raw
In response to Re: BUG #16867: savepoints vs. commit and chain  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: BUG #16867: savepoints vs. commit and chain  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-bugs
On 2/19/21 5:02 AM, Fujii Masao wrote:
> 
> 
> On 2021/02/18 23:10, Vik Fearing wrote:
>>
>> No objection from me.  According to the standard, a COMMIT should
>> destroy all savepoints and terminate the transaction, even if AND CHAIN
>> is specified.
> 
> You imply that the standard says that COMMIT AND CHAIN should just
> terminate
> the transaction if there are savepoints defined, i.e., should not start new
> transaction? Since I can (maybe wrongly) interpret your comment like that,
> please let me confirm what the standard says just in case.

The COMMIT terminates the transaction, the AND CHAIN starts a new one.

> I was thinking that COMMIT AND CHAIN should destroy all the savepoints,
> terminate the transaction and start new transaction with the same
> transaction
> characteristics immediately.

Your thinking is correct!
-- 
Vik Fearing



pgsql-bugs by date:

Previous
From: Andriy Bartash
Date:
Subject: Re: BUG #16873: CREATE SUBSCRIPTION command hangs (Cross version logical replication) Wait event LibPQWalReceiverRec
Next
From: Richard Guo
Date:
Subject: Re: BUG #16869: GROUP BY on primary key unnecessarily triggers a full table scan