Re: Optimizing maximum/minimum queries (yet again) - Mailing list pgsql-hackers

From Bruno Wolff III
Subject Re: Optimizing maximum/minimum queries (yet again)
Date
Msg-id 20050409024432.GA4026@wolff.to
Whole thread Raw
In response to Optimizing maximum/minimum queries (yet again)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Optimizing maximum/minimum queries (yet again)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Apr 08, 2005 at 20:50:09 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Comments?  Anyone see anything I missed?

Thinking about the case for NULLs some more, I am wondering if you are
going to treat aggregates with strict state functions different than
those that don't? It seems for ones with strict state functions you need
to not include NULL values when doing using ORDER BY. For aggregates
that aren't strict it may be possible that it is desired that NULL
be returned if there is a NULL value in one of the rows.


pgsql-hackers by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: Optimizing maximum/minimum queries (yet again)
Next
From: Mark Kirkwood
Date:
Subject: Re: Optimizing maximum/minimum queries (yet again)