From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Jean-Luc Lachance <jllachan@nsd.ca>
Cc: Michael S. Tibbetts <mtibbetts@head-cfa.cfa.harvard.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: min() and NaN
Date: Tue, 22 Jul 2003 16:19:57 -0400 (EDT)
Message-ID: <200307222019.h6MKJvP20649@candle.pha.pa.us> (raw)
In-Reply-To: <15160.1058902399@sss.pgh.pa.us>
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Well, my 2 cents is that though we consider NULL when ordering via ORDER
> > BY, we ignore it in MAX because it really isn't a value, and NaN seems
> > to be similar to NULL.
>
> Good idea, but I don't think we can get away with it. The spec says
> that MAX/MIN have to be consistent with the comparison operators (and
> therefore with ORDER BY):
>
> iii) If MAX or MIN is specified, then the result is respec-
> tively the maximum or minimum value in TXA. These results
> are determined using the comparison rules specified in
> Subclause 8.2, "<comparison predicate>".
>
> NULL can be special, because it acts specially in comparisons anyway.
> But NaN is just a value of the datatype.
>
> I'd be willing to go against the spec if I thought that having
> ignore-NaNs behavior was sufficiently important, but I don't think it's
> important enough to disregard the spec...
Yep.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, sszabo@megazone.bigpanda.com, jllachan@nsd.ca, mtibbetts@head-cfa.cfa.harvard.edu
Subject: Re: min() and NaN
In-Reply-To: <200307222019.h6MKJvP20649@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox