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

On Thu, Oct 8, 2026 at 12:50 PM Amit Langote <amitlan(at)postgresql(dot)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