| From: | James Cloos <cloos(at)jhcloos(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Subject: | Re: Floating-point timestamps versus Range Types |
| Date: | 2010-10-25 20:35:23 |
| Message-ID: | m3aam2ui1o.fsf@jhcloos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "TL" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
JC> That said, the possiblity of hex i/o format for the float datatypes
JC> would be welcome.
TL> It's unportable, for two different reasons:
TL> 2. The printf specifiers you want us to rely on are not standard.
They are in C99.
TL> 1. pg_dump output would become platform-specific. This is highly
TL> undesirable.
It is true that pg would have to test for them in configure and supply
alternative code wherever libc fails to support them.
I can readily accept that there are many more pressing needs.
But would such a patch for master be rejected?
-JimC
--
James Cloos <cloos(at)jhcloos(dot)com> OpenPGP: 1024D/ED7DAEA6
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-10-25 20:51:02 | Re: Postgres insert performance and storage requirement compared to Oracle |
| Previous Message | Tom Lane | 2010-10-25 20:31:09 | Re: add label to enum syntax |