Keh-Cheng Chu writes:
> I have been running a locally modified postgresql server with
> extra_float_digits' upper limit increased by one to 3 and a
> modified pg_dump which sets extra_float_digits to 3; I have
> verified that the modification does what I need and it does
> not seem to have any s
On Wed, Sep 9, 2009 at 6:04 PM, Tom Lane wrote:
> Keh-Cheng Chu writes:
>> While 17 decimal digits are sufficient to guarantee the
>> complete recovery of all 64-bit double values, some 32-bit
>> reals actually require NINE significant figures.
>
> Hm, annoying. Seems like we could do one of two
Keh-Cheng Chu writes:
> While 17 decimal digits are sufficient to guarantee the
> complete recovery of all 64-bit double values, some 32-bit
> reals actually require NINE significant figures.
Hm, annoying. Seems like we could do one of two things:
1. Increase the max extra_float_digits value
I have applications that require IEEE floating-point data
to remain unchanged to the last bit after a dump/restore
cycle. Currently on all our linux systems, pg_dump uses
8 significant figures (FLT_DIG + 2) to dump 32-bit reals
and 17 significant figures (DBL_DIG + 2) to dump 64-bit
doubles, wh
