Skip to content

Commit 148326b

Browse files
committed
Mention extra_float_digits in floating point docs
Make it easier for readers of the FP docs to find out about possibly truncated values. Per complaint from Tom Duffey in message F0E0F874-C86F-48D1-AA2A-0C5365BF5118@trillitech.com Author: Albe Laurenz Reviewed by: Abhijit Menon-Sen
1 parent d2e71ff commit 148326b

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

doc/src/sgml/config.sgml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5366,6 +5366,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
53665366
partially-significant digits; this is especially useful for dumping
53675367
float data that needs to be restored exactly. Or it can be set
53685368
negative to suppress unwanted digits.
5369+
See also <xref linkend="datatype-float">.
53695370
</para>
53705371
</listitem>
53715372
</varlistentry>

doc/src/sgml/datatype.sgml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -681,6 +681,17 @@ NUMERIC
681681
from zero will cause an underflow error.
682682
</para>
683683

684+
<note>
685+
<para>
686+
The <xref linkend="guc-extra-float-digits"> setting controls the
687+
number of extra significant digits included when a floating point
688+
value is converted to text for output. With the default value of
689+
<literal>0</literal>, the output is the same on every platform
690+
supported by PostgreSQL. Increasing it will produce output that
691+
more accurately represents the stored value, but may be unportable.
692+
</para>
693+
</note>
694+
684695
<indexterm>
685696
<primary>not a number</primary>
686697
<secondary>double precision</secondary>

0 commit comments

Comments
 (0)