From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Fixing the representation of ORDER BY/GROUP BY/DISTINCT |
Date: | 2008-08-01 16:19:53 |
Message-ID: | 20080801161953.GA29929@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 31, 2008 at 08:54:49PM -0400, Tom Lane wrote:
> So while I was fooling with Steve Midgley's problem I got a bit of a bee
> in my bonnet about the way that the parser emits ORDER BY, GROUP BY,
> and DISTINCT lists.
There's an open TODO item in this area: namely that a GROUP BY referring
to a primary key is equivalent to a GROUP BY involving all the rest of
the fields. Now, I don't think anyone has proposed a way to support
that, but I wanted to check we arn't making it harder to do with these
changes...
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-08-01 16:26:05 | Re: Fixing the representation of ORDER BY/GROUP BY/DISTINCT |
Previous Message | Tom Lane | 2008-08-01 14:55:04 | Re: Fixing the representation of ORDER BY/GROUP BY/DISTINCT |