From ade455e95ebc2300b5d7a76e8f6b2167406f69db Mon Sep 17 00:00:00 2001 From: Steve Lau Date: Thu, 27 Nov 2025 22:21:42 +0800 Subject: [PATCH v1] Mention TABLEFUNC to make comment consistent with code Commit [1] that implemented the XMLTABLE table function didn't update this comment, leaving code and comment inconsistent. This commit updates the comment to make it consistent. [1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=fcec6caafa2346b6c9d3ad5065e417733bd63cd9 --- src/backend/optimizer/plan/planner.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/optimizer/plan/planner.c b/src/backend/optimizer/plan/planner.c index c4fd646b999..9f1404b9bad 100644 --- a/src/backend/optimizer/plan/planner.c +++ b/src/backend/optimizer/plan/planner.c @@ -1298,8 +1298,8 @@ preprocess_expression(PlannerInfo *root, Node *expr, int kind) * we may extract from the joinaliasvars lists have not been preprocessed. * For example, if we did this after sublink processing, sublinks expanded * out from join aliases would not get processed. But we can skip this in - * non-lateral RTE functions, VALUES lists, and TABLESAMPLE clauses, since - * they can't contain any Vars of the current query level. + * non-lateral RTE functions, VALUES lists, TABLESAMPLE, and TABLEFUNC + * clauses, since they can't contain any Vars of the current query level. */ if (root->hasJoinRTEs && !(kind == EXPRKIND_RTFUNC || -- 2.51.2