From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Third thoughts about the DISTINCT MAX() problem |
Date: | 2008-03-29 08:54:13 |
Message-ID: | 1206780853.4285.1793.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 2008-03-29 at 07:07 +0530, Gurjeet Singh wrote:
> On Sat, Mar 29, 2008 at 3:21 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> regression=# select max(unique1), generate_series(1,3) as g
> from tenk1 order by g desc;
> max | g
> ------+---
> 9999 | 1
> 9999 | 2
> 9999 | 3
> (3 rows)
>
>
> In the past I had seen suggestions (perhaps from you) that we should
> disallow SRFs in target list... Although not for 8.3, but would this
> be a good time for 8.4 to deprecate the usage of SRFs in targetlist?
I think it makes sense to throw an error if we have both ungrouped
aggregates and SRFs in the targetlist. The two concepts seem at odds
with each other anyhow.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-29 12:03:20 | Re: [PATCHES] Implemented current_query |
Previous Message | Gurjeet Singh | 2008-03-29 01:37:10 | Re: Third thoughts about the DISTINCT MAX() problem |