Re: Floating-point timestamps versus Range Types

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Cloos <cloos(at)jhcloos(dot)com>
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:09:20
Message-ID: 4936.1288037360@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James Cloos <cloos(at)jhcloos(dot)com> writes:
> That said, the possiblity of hex i/o format for the float datatypes
> would be welcome.

It's unportable, for two different reasons:

1. pg_dump output would become platform-specific. This is highly
undesirable.

2. The printf specifiers you want us to rely on are not standard.
Cf Single Unix Spec,
http://www.opengroup.org/onlinepubs/007908799/xsh/fprintf.html
which does not define either %A or %a.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2010-10-25 20:10:21 Re: foreign keys for array/period contains relationships
Previous Message Pavel Stehule 2010-10-25 20:03:56 Re: add label to enum syntax