Re: Bug / feature request for floating point to string conversion - Mailing list pgsql-hackers

From Daniel Frey
Subject Re: Bug / feature request for floating point to string conversion
Date
Msg-id 493B53F4-7798-4D65-AE34-0B00BAFC9645@gmx.de
Whole thread Raw
In response to Re: Bug / feature request for floating point to string conversion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10.10.2012, at 20:26, Tom Lane wrote:

> Daniel Frey <d.frey@gmx.de> writes:
>>  INSERT INTO dummy VALUES ( '0X1P-1022' );
>
>> this value itself is the problem. If I use pg_dump / pg_restore, the restore fails with:
>
>>  COPY failed for table "dummy": ERROR:  "2.22507385850720138e-308" is out of range for type double precision
>
>> This behavior might depend on the system's implementation of strtod(), I'm using Ubuntu 12.04.
>
> That is definitely a bug in strtod, which you should report.  If it
> doesn't accept a value that sprintf output, something is broken at the
> libc level.

Who guarantees that? While I would have hoped for strtod() to accept everything generated from sprintf() from a valid
float/double,I don't see anyone giving you this guarantee. I'd be happy to be wrong about this, but until then, I think
thatpg_dump/pg_restore can not be guaranteed to work, right? 

Regards, Daniel




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: change in LOCK behavior
Next
From: Tom Lane
Date:
Subject: Re: Move postgresql_fdw_validator into dblink