diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 8 | ||||
| -rw-r--r-- | doc/src/sgml/datatype.sgml | 55 | ||||
| -rw-r--r-- | doc/src/sgml/installation.sgml | 22 |
3 files changed, 14 insertions, 71 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 95afc2c483d..1b390a257ae 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -7695,11 +7695,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' </term> <listitem> <para> - Reports whether <productname>PostgreSQL</> was built with - support for 64-bit-integer dates and times. This can be - disabled by configuring with <literal>--disable-integer-datetimes</> - when building <productname>PostgreSQL</>. The default value is - <literal>on</literal>. + Reports whether <productname>PostgreSQL</> was built with support for + 64-bit-integer dates and times. As of <productname>PostgreSQL</> 10, + this is always <literal>on</literal>. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 387ba53ef09..35610307d9a 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1580,7 +1580,7 @@ SELECT E'\\xDEADBEEF'; <entry>both date and time (no time zone)</entry> <entry>4713 BC</entry> <entry>294276 AD</entry> - <entry>1 microsecond / 14 digits</entry> + <entry>1 microsecond</entry> </row> <row> <entry><type>timestamp [ (<replaceable>p</replaceable>) ] with time zone</type></entry> @@ -1588,7 +1588,7 @@ SELECT E'\\xDEADBEEF'; <entry>both date and time, with time zone</entry> <entry>4713 BC</entry> <entry>294276 AD</entry> - <entry>1 microsecond / 14 digits</entry> + <entry>1 microsecond</entry> </row> <row> <entry><type>date</type></entry> @@ -1604,15 +1604,15 @@ SELECT E'\\xDEADBEEF'; <entry>time of day (no date)</entry> <entry>00:00:00</entry> <entry>24:00:00</entry> - <entry>1 microsecond / 14 digits</entry> + <entry>1 microsecond</entry> </row> <row> <entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry> <entry>12 bytes</entry> - <entry>times of day only, with time zone</entry> + <entry>time of day (no date), with time zone</entry> <entry>00:00:00+1459</entry> <entry>24:00:00-1459</entry> - <entry>1 microsecond / 14 digits</entry> + <entry>1 microsecond</entry> </row> <row> <entry><type>interval [ <replaceable>fields</replaceable> ] [ (<replaceable>p</replaceable>) ]</type></entry> @@ -1620,7 +1620,7 @@ SELECT E'\\xDEADBEEF'; <entry>time interval</entry> <entry>-178000000 years</entry> <entry>178000000 years</entry> - <entry>1 microsecond / 14 digits</entry> + <entry>1 microsecond</entry> </row> </tbody> </tgroup> @@ -1643,41 +1643,7 @@ SELECT E'\\xDEADBEEF'; <replaceable>p</replaceable> which specifies the number of fractional digits retained in the seconds field. By default, there is no explicit bound on precision. The allowed range of - <replaceable>p</replaceable> is from 0 to 6 for the - <type>timestamp</type> and <type>interval</type> types. - </para> - - <note> - <para> - When <type>timestamp</> values are stored as eight-byte integers - (currently the default), microsecond precision is available over - the full range of values. In this case, the internal representation - is the number of microseconds before or after midnight 2000-01-01. - When <type>timestamp</> values are stored as double precision - floating-point numbers (a deprecated compile-time option), the - internal representation is the number of seconds before or after - midnight 2000-01-01. With this representation, the effective limit - of precision might be less than 6; in practice, - microsecond precision is achieved for dates within a few - years of 2000-01-01, but the precision degrades for dates further - away. Note that using floating-point datetimes allows a larger - range of <type>timestamp</type> values to be represented than - shown above: from 4713 BC up to 5874897 AD. - </para> - - <para> - The same compile-time option also determines whether - <type>time</type> and <type>interval</type> values are stored as - floating-point numbers or eight-byte integers. In the - floating-point case, large <type>interval</type> values degrade in - precision as the size of the interval increases. - </para> - </note> - - <para> - For the <type>time</type> types, the allowed range of - <replaceable>p</replaceable> is from 0 to 6 when eight-byte integer - storage is used, or from 0 to 10 when floating-point storage is used. + <replaceable>p</replaceable> is from 0 to 6. </para> <para> @@ -1760,9 +1726,10 @@ MINUTE TO SECOND specification giving the number of fractional digits in the seconds field. Precision can be specified for <type>time</type>, <type>timestamp</type>, and - <type>interval</type> types. The allowed values are mentioned - above. If no precision is specified in a constant specification, - it defaults to the precision of the literal value. + <type>interval</type> types, and can range from 0 to 6. + If no precision is specified in a constant specification, + it defaults to the precision of the literal value (but not + more than 6 digits). </para> <sect3> diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml index be0931326bc..568995c9f2f 100644 --- a/doc/src/sgml/installation.sgml +++ b/doc/src/sgml/installation.sgml @@ -956,28 +956,6 @@ su - postgres </varlistentry> <varlistentry> - <term><option>--disable-integer-datetimes</option></term> - <listitem> - <para> - Disable support for 64-bit integer storage for timestamps and - intervals, and store datetime values as floating-point - numbers instead. Floating-point datetime storage was the - default in <productname>PostgreSQL</productname> releases - prior to 8.4, but it is now deprecated, because it does not - support microsecond precision for the full range of - <type>timestamp</type> values. However, integer-based - datetime storage requires a 64-bit integer type. Therefore, - this option can be used when no such type is available, or - for compatibility with applications written for prior - versions of <productname>PostgreSQL</productname>. See - <![%standalone-include[the documentation about datetime datatypes]]> - <![%standalone-ignore[<xref linkend="datatype-datetime">]]> - for more information. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><option>--disable-float4-byval</option></term> <listitem> <para> |