Commit 148326b9 authored by Alvaro Herrera's avatar Alvaro Herrera

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
parent d2e71ff7
...@@ -5366,6 +5366,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; ...@@ -5366,6 +5366,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
partially-significant digits; this is especially useful for dumping partially-significant digits; this is especially useful for dumping
float data that needs to be restored exactly. Or it can be set float data that needs to be restored exactly. Or it can be set
negative to suppress unwanted digits. negative to suppress unwanted digits.
See also <xref linkend="datatype-float">.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
......
...@@ -681,6 +681,17 @@ NUMERIC ...@@ -681,6 +681,17 @@ NUMERIC
from zero will cause an underflow error. from zero will cause an underflow error.
</para> </para>
<note>
<para>
The <xref linkend="guc-extra-float-digits"> setting controls the
number of extra significant digits included when a floating point
value is converted to text for output. With the default value of
<literal>0</literal>, the output is the same on every platform
supported by PostgreSQL. Increasing it will produce output that
more accurately represents the stored value, but may be unportable.
</para>
</note>
<indexterm> <indexterm>
<primary>not a number</primary> <primary>not a number</primary>
<secondary>double precision</secondary> <secondary>double precision</secondary>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment