Horton

Re: Ryu floating point output patch

Andrew Dunstan <andrew.dunstan@2ndquadrant.com>

View thread View on postgr.es
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: pgsql-hackers@postgresql.org, "David G. Johnston" <david.g.johnston@gmail.com>, Donald Dong <xdong@csumb.edu>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, Chapman Flack <chap@anastigmatix.net>
Date: 2019-02-18T13:56:19Z
Lists: pgsql-hackers 
On 2/17/19 6:49 PM, Tom Lane wrote:
> Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
>> "Andrew" == Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>>  Andrew> Would you like to reformulate this, then?
>> How about:
>>     Use the specified value of extra_float_digits when dumping
>>     floating-point data, instead of the maximum available precision.
>>     Routine dumps made for backup purposes should not use this option.
> OK by me.
>
> 			


Done.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Provide an extra-float-digits setting for pg_dump / pg_dumpall

  2. Change floating-point output format for improved performance.

  3. Use strtof() and not strtod() for float4 input.