| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Gsets: ROW expression semantic broken between 9.4 and 9.5 |
| Date: | 2015-07-22 18:42:42 |
| Message-ID: | 20150722184242.GA21169@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Hi,
On 2015-07-22 23:53:26 +0530, Jeevan Chalke wrote:
> It looks like we have broken the ROW expression without explicit
> ROW keyword in GROUP BY.
That was "intentional", and is actually standards required
behaviour. GROUP BY (a, b) is the same as GROUP BY a,b. It'd otherwise
be pretty confusing because parens in GROUPING SETS would mean something
different than in GROUP BY.
We should probably add a release note entry about it...
Thanks for testing gsets!
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-07-22 20:13:01 | Re: BUG #13497: Build with dtrace fails |
| Previous Message | Jeevan Chalke | 2015-07-22 18:23:26 | Gsets: ROW expression semantic broken between 9.4 and 9.5 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-07-22 18:45:03 | Re: pgbench stats per script & other stuff |
| Previous Message | Fabien COELHO | 2015-07-22 18:39:22 | Re: pgbench stats per script & other stuff |