Re: Infinity confuses planner (was Re: query plan)

> The reason I didn't see it here is that on my platform, the infinity
> timestamp values aren't represented as real IEEE infinities, and so the
> result isn't NAN.
>
> Seems like we could fix this either by forbidding use of real infinity
> for timestamp and float8 values ... probably not workable for float8,
> even if it's okay for timestamp ... or by trying to defend against
> infinity and NAN results in the selectivity subroutines.

Shouldn't infinity be treated similar to NULL.  I know they are
different but they are clearly off-the-scale type values.  The problem
is that it is type-specific and not general enough for the optimizer.
Tough one.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026