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 A4D67537-D09B-4C67-A03C-4A59F7C5C238@yandex-team.ru
Whole thread
In response to Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-hackers
Hi Dean,

On 23 Sep 2026, Dean Rasheed wrote:
> Grepping on PGXN, I see no use of ExecCheckIndexConstraints(), so it's
> probably your fix is OK.

I found a caller in pg_lake [0] that creates its own EState without
setting es_snapshot. It pushes an active snapshot, but passes the
unchanged EState to ExecCheckIndexConstraints(). Your proposed
InvalidSnapshot guard would cover this too.

Thank you!


Best regards, Andrey Borodin.

[0]
https://github.com/Snowflake-Labs/pg_lake/blob/44befc068dda9346bca2b0982929d99508d43fdf/pg_lake_table/src/fdw/update_tracking.c#L105-L284




pgsql-hackers by date:

Previous
From: Nikhil Kumar Veldanda
Date:
Subject: Re: ZSTD TOAST compression, and an extensible compression method encoding
Next
From: shveta malik
Date:
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation