Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit e2fe327

Browse files
committed
Improve error wording of ORDER BY in UNION that uses new expressions in
ORDER BY.
1 parent ad429fe commit e2fe327

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/parser/analyze.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
* Portions Copyright (c) 1996-2007, PostgreSQL Global Development Group
77
* Portions Copyright (c) 1994, Regents of the University of California
88
*
9-
* $PostgreSQL: pgsql/src/backend/parser/analyze.c,v 1.355 2007/01/09 02:14:13 tgl Exp $
9+
* $PostgreSQL: pgsql/src/backend/parser/analyze.c,v 1.356 2007/01/11 18:44:53 momjian Exp $
1010
*
1111
*-------------------------------------------------------------------------
1212
*/
@@ -2547,7 +2547,7 @@ transformSetOperationStmt(ParseState *pstate, SelectStmt *stmt)
25472547
if (tllen != list_length(qry->targetList))
25482548
ereport(ERROR,
25492549
(errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
2550-
errmsg("ORDER BY on a UNION/INTERSECT/EXCEPT result must be on one of the result columns")));
2550+
errmsg("ORDER BY on a UNION/INTERSECT/EXCEPT result must match existing result columns")));
25512551

25522552
qry->limitOffset = transformLimitClause(pstate, limitOffset,
25532553
"OFFSET");

0 commit comments

Comments
 (0)