pgsql: Check misplaced window functions before checking aggregate/group

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Check misplaced window functions before checking aggregate/group
Date: 2012-02-08 18:15:18
Message-ID: E1RvC34-0006JZ-Fm@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Check misplaced window functions before checking aggregate/group by sanity.

If somebody puts a window function in WHERE, we should complain about that
in so many words. The previous coding tended to complain about the window
function's arguments instead, which is likely to be misleading to users who
are unclear on the semantics of window functions; as seen for example in
bug #6440 from Matyas Novak.

Just another example of how "add new code at the end" is frequently a bad
heuristic.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/cb7c84fae8a6780d836687aa2c9655eb936ebd25

Modified Files
--------------
src/backend/parser/analyze.c | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-02-08 20:23:06 pgsql: Fix up dumping conditions for extension configuration tables.
Previous Message Tom Lane 2012-02-08 17:41:58 pgsql: Support min/max index optimizations on boolean columns.