Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: bobergj(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
Date: 2026-07-08 20:29:35
Message-ID: CAEZATCUv-szt_X8KuNTg2VQzxsoty8ojj2WtVX9OmCXQCLFD0Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 7 Jul 2026 at 08:38, Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Sorry for the late response. I took a look at the v2 patch, tested it
> locally, and it looks good to me. I think we should backpatch this fix
> down to PG18 (commit 80feb727c86).
>

Thanks for reviewing.

Pushed and back-patched to v18.

Regards,
Dean

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message surya poondla 2026-07-08 18:25:54 Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function