Re: Ryu floating point output patch
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>, 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-17T23:04:22Z
Lists: pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > Here's a patch without docco. How much do we actually want to document > this? I'm not sure it has any great value outside of cross-version > upgrade testing. I think we have to document it, but it can be fairly terse perhaps. Use the specified value of extra_float_digits when dumping floating-point data, rather than pg_dump's default. I don't think we need to go into detail about when/why you might want to use it; I can see people thinking of their own reasons. regards, tom lane
Commits
-
Provide an extra-float-digits setting for pg_dump / pg_dumpall
- af25bc03e17e 12.0 landed
-
Change floating-point output format for improved performance.
- 02ddd499322a 12.0 landed
-
Use strtof() and not strtod() for float4 input.
- f397e08599a3 12.0 landed