pgsql: Fix ExecCheckPermissions call in RI_Initial_Check - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Fix ExecCheckPermissions call in RI_Initial_Check
Date
Msg-id E1pudDm-000Tck-BV@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix ExecCheckPermissions call in RI_Initial_Check

RI_Initial_Check was setting up a list of RTEPermissionInfo for
ExecCheckPermissions() wrong, and the problem is subtle enough that it
doesn't have any immediate effect in core code.  However, if an
extension is using the ExecutorCheckPerms_hook, then it would get the
wrong parameters and perhaps arrive at a wrong conclusion, or outright
malfunction.  Fix by constructing that list and the RTE list more
honestly.

We also add an assertion check to verify that these lists match.  This
new assertion would have caught this bug.

Co-authored-by: Олег Целебровский (Oleg Tselebrovskii) <o.tselebrovskiy@postgrespro.ru>
Co-authored-by: Álvaro Herrera <alvherre@alvh.no-ip.org>
Reviewed-by: Amit Langote <amitlangote09@gmail.com>
Discussion: https://postgr.es/m/3722b7a2cbe27a1796ee40824bd86dd1@postgrespro.ru

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f75cec4fff877ef24e4932a628fc974f3116ed16

Modified Files
--------------
src/backend/executor/execMain.c     | 22 +++++++++++++++++++
src/backend/utils/adt/ri_triggers.c | 42 +++++++++++++++++++++----------------
2 files changed, 46 insertions(+), 18 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: In array_position()/array_positions(), beware of empty input arr
Next
From: Nathan Bossart
Date:
Subject: pgsql: Move return statements out of PG_TRY blocks.