]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Fix unsafe RTE_GROUP removal in simplify_EXISTS_query
authorRichard Guo <rguo@postgresql.org>
Wed, 25 Feb 2026 02:13:21 +0000 (11:13 +0900)
committerRichard Guo <rguo@postgresql.org>
Wed, 25 Feb 2026 02:15:05 +0000 (11:15 +0900)
commit1c7358099cbe77bc622bc817ec4e9d919ca91fcf
tree5a8090eb6ddedc6fb18d78cb506e451fc293811a
parent1b2773179f31b25bc560e06a35970fdd9b1a6d90
Fix unsafe RTE_GROUP removal in simplify_EXISTS_query

When simplify_EXISTS_query removes the GROUP BY clauses from an EXISTS
subquery, it previously deleted the RTE_GROUP RTE directly from the
subquery's range table.

This approach is dangerous because deleting an RTE from the middle of
the rtable list shifts the index of any subsequent RTE, which can
silently corrupt any Var nodes in the query tree that reference those
later relations.  (Currently, this direct removal has not caused
problems because the RTE_GROUP RTE happens to always be the last entry
in the rtable list.  However, relying on that is extremely fragile and
seems like trouble waiting to happen.)

Instead of deleting the RTE_GROUP RTE, this patch converts it in-place
to be RTE_RESULT type and clears its groupexprs list.  This preserves
the length and indexing of the rtable list, ensuring all Var
references remain intact.

Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Author: Richard Guo <guofenglinux@gmail.com>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/3472344.1771858107@sss.pgh.pa.us
Backpatch-through: 18
src/backend/optimizer/plan/subselect.c