Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Date
Msg-id 9CFB16FF-26A4-482A-8D86-272CB67B4224@yandex-team.ru
Whole thread
In response to Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row  (Zsolt Parragi <zsolt.parragi@percona.com>)
Responses Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
List pgsql-hackers

> On 1 Oct 2026, at 13:28, Zsolt Parragi <zsolt.parragi@percona.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.



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: REPACK: warn about skipping foreign partitions
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: pgindent to ignore build directories