From: Heikki Linnakangas Date: Tue, 28 Nov 2023 12:08:43 +0000 (+0200) Subject: Fix comment about ressortgrouprefs being unique in setop plans. X-Git-Tag: REL_17_BETA1~1383 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=10a59925a378bd67aa3834c842dad19de9c5e4c0;p=thirdparty%2Fpostgresql.git Fix comment about ressortgrouprefs being unique in setop plans. Author: Richard Guo, Tom Lane Discussion: https://www.postgresql.org/message-id/CAMbWs49rAfFS-yd7=QxtDUrZDFfRBGy4rGBJNyGDH7=CLipFPg@mail.gmail.com --- diff --git a/src/backend/optimizer/plan/setrefs.c b/src/backend/optimizer/plan/setrefs.c index fc3709510d2..4bb68ac90e7 100644 --- a/src/backend/optimizer/plan/setrefs.c +++ b/src/backend/optimizer/plan/setrefs.c @@ -2936,7 +2936,14 @@ search_indexed_tlist_for_sortgroupref(Expr *node, { TargetEntry *tle = (TargetEntry *) lfirst(lc); - /* The equal() check should be redundant, but let's be paranoid */ + /* + * Usually the equal() check is redundant, but in setop plans it may + * not be, since prepunion.c assigns ressortgroupref equal to the + * column resno without regard to whether that matches the topmost + * level's sortgrouprefs and without regard to whether any implicit + * coercions are added in the setop tree. We might have to clean that + * up someday; but for now, just ignore any false matches. + */ if (tle->ressortgroupref == sortgroupref && equal(node, tle->expr)) {