diff options
author | Tatsuo Ishii <ishii@postgresql.org> | 2020-01-05 19:45:37 +0900 |
---|---|---|
committer | Tatsuo Ishii <ishii@postgresql.org> | 2020-01-05 19:45:37 +0900 |
commit | 955f1213012361e32d88976c3ce03ae62153c355 (patch) | |
tree | dac3a08b8bea0a7073f16733b506c2de97848ef9 | |
parent | 48e03583cd373ce67827f4d8a99dcef8242364b0 (diff) | |
download | postgresql-955f1213012361e32d88976c3ce03ae62153c355.tar.gz postgresql-955f1213012361e32d88976c3ce03ae62153c355.zip |
Docs: use more standard terminology "round-to-nearest-even" instead of "round-to-even".
Per suggestion from Tom Lane.
Discussion: https://postgr.es/m/flat/20191230.093451.1762483750956466101.t-ishii%40sraoss.co.jp
-rw-r--r-- | doc/src/sgml/datatype.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 01a9ab76aa9..d1d033178ff 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -731,7 +731,7 @@ FROM generate_series(-3.5, 3.5, 1) as x; representable in the same binary precision. (However, the output value is currently never <emphasis>exactly</emphasis> midway between two representable values, in order to avoid a widespread bug where input - routines do not properly respect the round-to-even rule.) This value will + routines do not properly respect the round-to-nearest-even rule.) This value will use at most 17 significant decimal digits for <type>float8</type> values, and at most 9 digits for <type>float4</type> values. </para> |