| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, <pgsql-sql(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Our FLOAT(p) precision does not conform to spec |
| Date: | 2003-06-17 18:04:42 |
| Message-ID: | Pine.LNX.4.44.0306171659440.2043-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Tom Lane writes:
> This is a straightforward change and would not break pg_dump files,
> since fortunately pg_dump always references the underlying types and
> never refers to anything as FLOAT(p). But I wonder whether it is
> likely to break many existing applications. There is a hazard of some
> existing app asking for (what it thinks is) float8 and getting float4
> instead.
Considering that the data type float(x) isn't documented anywhere, I'm not
worried.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-06-17 18:05:23 | Re: Reordered .conf file ... need help with LC_vars |
| Previous Message | Peter Eisentraut | 2003-06-17 18:03:18 | Re: Domains and function arguments |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-06-17 18:09:56 | Re: date question |
| Previous Message | Josh Berkus | 2003-06-17 17:58:44 | Re: disabling triggers |