On Wed, Sep 9, 2009 at 6:04 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Keh-Cheng Chu <kehcheng(at)solar2(dot)Stanford(dot)EDU> 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 to 3 and have pg_dump use
> 2. Split extra_float_digits into two settings so that float4 and float8
> can use different settings.
> Offhand the only argument I can see for #2 is that #1 might bloat dump
> files unnecessarily --- but it's not likely to be significant on a
> percentage basis.
> We'd also need to check the code to be sure it's leaving room for the
> extra digit in all cases, though I doubt there's really any problem.
(2) seems like overkill to me, FWIW.
In response to
pgsql-bugs by date
|Next:||From: Heikki Linnakangas||Date: 2009-09-10 05:36:23|
|Subject: Re: BUG #5038: WAL file is pending deletion in pg_xlog folder,
this interferes with WAL archiving.|
|Previous:||From: Tom Lane||Date: 2009-09-09 22:04:29|
|Subject: Re: need higher extra_float_digits value (3) |