Re: BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Tender Wang <tndrwang(at)gmail(dot)com>
Cc: 303677365(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19912: MERGE NOT MATCHED BY SOURCE sees stale source values after concurrent update (EPQ)
Date: 2026-11-21 12:31:08
Message-ID: CAEZATCWUmTvc-xEpWTi8dtLtQwncxRLH17w5HgVyxp0BA8nB1A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 18 Nov 2026 at 12:30, Tender Wang <tndrwang(at)gmail(dot)com> wrote:
>
> The updated v2 patch is attached.

I spent a while thinking about this and I think it's correct. Setting
all the values in the new slot to NULL gave me pause, because it also
contains "junk" target attributes, but I managed to convince myself
that they're no longer needed, so it's OK to leave them NULL.

I wrote a new isolation test, and pushed it, back-patching to v17.

Regards,
Dean

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2026-11-21 13:37:50 Re: BUG #19779: Backend SIGSEGV in UPDATE with FOR UPDATE CTE joined to UNION ALL subquery
Previous Message Zsolt Parragi 2026-11-21 09:22:38 Re: pg_rewind and hint bits leads to visibility corruption