The fast path's ri_CheckPermissions() called ExecCheckOneRelPerms() directly, so ExecutorCheckPerms_hook never saw the referenced-table access that the SPI path's query exposed to it via ExecutorStart(). Modules such as sepgsql that rely on this hook therefore lost control over FK checks against referenced tables that go through the fast path. So, build a one-entry range table and permission-info list and call ExecCheckPermissions(). The hook now sees the same relation and requiredPerms as before, once per check that goes through the fast path. This also drops the shortcut that skipped the column-level check when table-level privileges sufficed, since the hook must run regardless. While at it, drop the explicit frees in the old code, because both callers run ri_CheckPermissions() in a per-tuple context that is reset after each check, so they were redundant. Reported-by: Noah Misch <noah@leadboat.com> Discussion: https://postgr.es/m/20260705210533.ee.noahmisch%40microsoft.com Backpatch-through: 19
PostgreSQL Database Management System
This directory contains the source code distribution of the PostgreSQL database management system.
PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. This distribution also contains C language bindings.
Copyright and license information can be found in the file COPYRIGHT.
General documentation about this version of PostgreSQL can be found at https://www.postgresql.org/docs/19/. In particular, information about building PostgreSQL from the source code can be found at https://www.postgresql.org/docs/19/installation.html.
The latest version of this software, and related software, may be obtained at https://www.postgresql.org/download/. For more information look at our web site located at https://www.postgresql.org/.