From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: float8 strtod weirdness |
Date: | 2009-01-07 16:44:19 |
Message-ID: | 2615.1231346659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> This example does seem to be confounded by PG's somewhat eccentric type
> system. Things would "just work" (in this case, and there have been
> other cases recently[1]) if type decisions could be delayed slightly.
There's been previous speculation about having numeric literals be
initially typed as "unknown_numeric", and then the existing preference
for resolving "var op unknown" as a same-types operator could do the
trick here. However, this would help only for float4 --- float8 tends
to behave as expected already. Given that anyone working in float4 had
better be well aware of its limited precision, I'm not convinced that
there's much to be gained by fooling with this.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2009-01-07 16:44:31 | Re: Solve a problem of LC_TIME of windows. |
Previous Message | David Fetter | 2009-01-07 16:37:30 | Re: about truncate |