Re: BUG #16867: savepoints vs. commit and chain

From: Arthur Nascimento <tureba(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16867: savepoints vs. commit and chain
Date: 2021-02-16 18:03:53
Message-ID: CALVFHFanjZ_K=xVbHE31QiAHcLfQU8g1Z-UYMHoPw1q-kAnDyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Tureba - Arthur Nascimento

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-02-17 00:30:13 BUG #16870: ADD COLUMN IF NOT EXISTS with GENERATED ALWAYS AS IDENTITY can cause duplicate sequence
Previous Message Tom Lane 2021-02-16 17:08:07 Re: BUG #16865: Regression: GIN Negated prefix search returns results that contain the search term