Re: pgsql: Lock RI fast-path rows as of the scan snapshot's command ID - Mailing list pgsql-committers

From Amit Langote
Subject Re: pgsql: Lock RI fast-path rows as of the scan snapshot's command ID
Date
Msg-id CA+HiwqH=D4d_SRZoo4fnE-sKRu_DO8UjJMyhATgaBcFUu7ANRg@mail.gmail.com
Whole thread
In response to pgsql: Lock RI fast-path rows as of the scan snapshot's command ID  (Amit Langote <amitlan@postgresql.org>)
List pgsql-committers
On Thu, Oct 8, 2026 at 12:50 PM Amit Langote <amitlan@postgresql.org> wrote:
> This is mostly hardening.  With FK values that need a cast now checked
> through SPI, the only user code that can run there is the opclass's
> equality function, and it would have to write to the referenced table.
> That's unlikely, but the fast path should still behave like SPI.

Oops, the "FK values that need a cast now checked through SPI" part is
not true as of now because I had assumed when writing it that I'd
commit the patch at [1] to make it true before this one but that
didn't happen.  The fix itself isn't invalidated (it still accounts
for user actions in cast functions), but the description is
unfortunately incorrect at this moment.

--
Thanks, Amit Langote

[1] https://www.postgresql.org/message-id/CA%2BHiwqGDY_T4NxBi-kg4Y3V%3DD1CmRhUmj_tyo8aP-ZGO145%3DEQ%40mail.gmail.com



pgsql-committers by date:

Previous
From: Amit Langote
Date:
Subject: pgsql: Lock RI fast-path rows as of the scan snapshot's command ID
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Fix warning message translatability