Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit10a5992

Browse files
committed
Fix comment about ressortgrouprefs being unique in setop plans.
Author: Richard Guo, Tom LaneDiscussion:https://www.postgresql.org/message-id/CAMbWs49rAfFS-yd7=QxtDUrZDFfRBGy4rGBJNyGDH7=CLipFPg@mail.gmail.com
1 parentf36b636 commit10a5992

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

‎src/backend/optimizer/plan/setrefs.c

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2936,7 +2936,14 @@ search_indexed_tlist_for_sortgroupref(Expr *node,
29362936
{
29372937
TargetEntry*tle= (TargetEntry*)lfirst(lc);
29382938

2939-
/* The equal() check should be redundant, but let's be paranoid */
2939+
/*
2940+
* Usually the equal() check is redundant, but in setop plans it may
2941+
* not be, since prepunion.c assigns ressortgroupref equal to the
2942+
* column resno without regard to whether that matches the topmost
2943+
* level's sortgrouprefs and without regard to whether any implicit
2944+
* coercions are added in the setop tree. We might have to clean that
2945+
* up someday; but for now, just ignore any false matches.
2946+
*/
29402947
if (tle->ressortgroupref==sortgroupref&&
29412948
equal(node,tle->expr))
29422949
{

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp