Tom Lane <tgl@sss.pgh.pa.us> writes:
> NULL can be special, because it acts specially in comparisons anyway.
> But NaN is just a value of the datatype.
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?
If not it seems more useful to just use the handy unknown-value thing SQL
already has and turn NaN into a NULL.
--
greg
