Horton

Re: MERGE behavior with REPEATABLE READ isolation level

Alexander Korotkov <aekorotkov@gmail.com>

View thread View on postgr.es
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Tender Wang <tndrwang@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Dean Rasheed <dean.a.rasheed@gmail.com>
Date: 2026-03-01T22:32:12Z
Lists: pgsql-hackers 
On Fri, Feb 27, 2026 at 2:54 PM Tender Wang <tndrwang@gmail.com> wrote:
> Alexander Korotkov <aekorotkov@gmail.com> 于2026年2月27日周五 01:03写道：
> > Thank you for the confirmation and for the patch.  Regarding the test
> > case, can we handle this without introducing a new .spec file?  I
> > think we can add 1-2 permutations to merge-update.spec.  Even existing
> > step should work, you only need one new which begins transaction in RR
> > isolation mode.
>
> Done
> Please see the v2 patch.

Looks good to me.  I'll push it if no objections.

------
Regards,
Alexander Korotkov
Supabase

Commits

  1. Fix handling of updated tuples in the MERGE statement