Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date: 2026-08-26 12:58:45
Message-ID: F5260B0C-D0AA-408C-A067-445C49F5B5D4@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 26 Aug 2026, at 03:38, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> <v3-0001-Take-SIREAD-lock-on-rows-read-by-ON-CONFLICT-DO-S.patch>

I think the patch is Ready for Committer.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vaibhav Dalvi 2026-08-26 13:01:54 Re: [PATCH] Add support for INSERT ... SET syntax
Previous Message Dilip Kumar 2026-08-26 12:56:05 Re: Proposal: Conflict log history table for Logical Replication