From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org>, Arthur Nascimento <tureba(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16867: savepoints vs. commit and chain |
Date: | 2021-02-19 13:05:25 |
Message-ID: | 0c903ec5-8f4f-0fd5-7861-abc11b2c8457@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2021/02/19 17:29, Vik Fearing wrote:
> 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!
Thanks! I pushed the patches.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2021-02-19 18:28:54 | Re: BUG #16874: Postgres Server crashes at commit |
Previous Message | PG Bug reporting form | 2021-02-19 10:00:38 | BUG #16874: Postgres Server crashes at commit |