| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mike Quinn <mquinn(at)co(dot)merced(dot)ca(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Infinity confuses planner (was Re: query plan) |
| Date: | 2001-10-13 23:39:57 |
| Message-ID: | 200110132339.f9DNdvg23161@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-13 23:43:32 | Re: Infinity confuses planner (was Re: query plan) |
| Previous Message | Tom Lane | 2001-10-13 20:17:57 | Infinity confuses planner (was Re: query plan) |