| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Boris Folgmann <misc(at)folgmann(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 1.0 in function call not regarded as REAL in 7.3.2 |
| Date: | 2003-08-21 14:49:10 |
| Message-ID: | 8052.1061477350@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Boris Folgmann <misc(at)folgmann(dot)com> writes:
> Look closely: postmaster now thinks that the first argument 1.0 is NUMERIC,
Yup. This is not a bug, it's intentional (and per SQL spec, AFAICT).
Your problem is that 123::real/25 yields a double precision result,
which is not implicitly castable to real anymore. I'd suggest
switching the function arguments to double precision.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mike | 2003-08-21 16:28:53 | index not used afer VACUUM ANALYZE |
| Previous Message | Tom Lane | 2003-08-21 14:23:32 | Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 |