From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | 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-18 13:58:48 |
Message-ID: | e3fbc15b-9aef-b076-d72e-20b537186342@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2021/02/17 3:03, Arthur Nascimento wrote:
> Hi, Fujii-san,
>
> On Tue, 16 Feb 2021 at 01:49, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>> In the server side, ISTM that CommitTransactionCommand() needs to handle
>> the COMMIT AND CHAIN in TBLOCK_SUBCOMMIT case, but it forgot to do that.
>> Patch attached. I'm not sure if this is a bug or an intentional behavior.
>> Probably we need to look at the past discussion about AND CHAIN feature.
>
> I can confirm that your patch solved it for me. Thanks for looking into it.
Thanks for testing the patch!
As far as I read the past discussion about chain transaction,
I could not find any mention that current behavior that you reported
is intentional.
Barring any objection, I will commit the patch that you wrote
for psql and the patch I wrote.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2021-02-18 14:10:32 | Re: BUG #16867: savepoints vs. commit and chain |
Previous Message | Kasahara Tatsuhito | 2021-02-18 11:29:16 | Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. |