Re: Improper const-evaluation of HAVING with grouping sets and subquery pullup

Andrew Gierth <andrew@tao11.riddles.org.uk>

From: Andrew Gierth <andrew@tao11.riddles.org.uk>

To: Heikki Linnakangas <hlinnaka@iki.fi>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Pg Bugs <pgsql-bugs@postgresql.org>

Date: 2017-10-17T09:50:24Z

Lists: pgsql-bugs

>>>>> "Andrew" == Andrew Gierth <andrew@tao11.riddles.org.uk> writes:

 Andrew> To my knowledge this is the correct result. (Though neither
 Andrew> version of the query is legal per the SQL spec; allowing
 Andrew> expressions and aliases in GROUP BY are nonstandard
 Andrew> extensions.)

And neither Oracle nor MSSQL (at least the versions available on
sqlfiddle) allow either query, so there's nothing I can compare against.

-- 
Andrew (irc:RhodiumToad)

Commits

Fix incorrect handling of subquery pullup in the presence of grouping sets.
- ff99d7761aa4 9.5.11 landed
- d3ca1a6c3721 10.2 landed
- 90947674fc98 11.0 landed
- 6520d4a96928 9.6.7 landed
Make setrefs.c match by ressortgroupref even for plain Vars.
- 6a81ba1d4d26 10.1 landed
- 37b4e0fe9964 9.6.6 landed
- 08f1e1f0a47b 11.0 landed
Make the upper part of the planner work by generating and comparing Paths.
- 3fc6e2d7f5b6 9.6.0 cited