| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Jean-Luc Lachance <jllachan(at)nsd(dot)ca>, "Michael S(dot) Tibbetts" <mtibbetts(at)head-cfa(dot)cfa(dot)harvard(dot)edu>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: min() and NaN |
| Date: | 2003-07-24 18:44:10 |
| Message-ID: | 13316.1059072250@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Does postgres intend to support all the different types of NaN? Does you
> intend to have +Inf and -Inf and underflow detection and all the other goodies
> you actually need to make it useful?
We have some of that; it needs work, and it's always going to be
dependent on the platform having proper IEEE support, but that's no
excuse to throw it away.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | elein | 2003-07-24 19:03:51 | Re: obtuse plpgsql function needs |
| Previous Message | Greg Stark | 2003-07-24 18:35:46 | Re: min() and NaN |