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: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, pgsql-hackers mailing list <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-10-01 08:59:38
Message-ID: 9CFB16FF-26A4-482A-8D86-272CB67B4224@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 1 Oct 2026, at 13:28, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> Maybe we should open a bug report to pg_lake about this? Even if we
> allow for this here, the documentation still requires es_snapshot to
> be set.

It's the cost of breaking old pg_lake users and possible unknown buggy users
against cost of extra runtime check for all others.

I don't have personal preferences in this choice. But I suspect that project
policy is that Postgres works. Without much surprises.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2026-10-01 09:00:57 Re: pgindent to ignore build directories
Previous Message Zsolt Parragi 2026-10-01 08:54:05 Re: REPACK: warn about skipping foreign partitions