From f52a34229b868249409e73365d42cab097a923e9 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 12 Jun 2005 15:51:50 +0000
Subject: [PATCH] Document the --enable-integer-datetimes configure option
where the other configure options are documented. Per Michael Glaesemann.
---
doc/src/sgml/installation.sgml | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index b772a23e583..85ae00e8de6 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.234 2005/06/04 20:42:41 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.235 2005/06/12 15:51:50 tgl Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -873,6 +873,21 @@ su - postgres
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>--enable-integer-datetimes</option></term>
+ <listitem>
+ <para>
+ Use 64-bit integer storage for datetimes and intervals, rather
+ than the default floating-point storage. This reduces the range
+ of representable values but guarantees microsecond precision across
+ the full range (see <xref linkend="datatype-datetime"> for more
+ information). Note also that the integer datetimes code is newer
+ than the floating-point code, and we still find bugs in it from time
+ to time.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><option>--disable-spinlocks</option></term>
<listitem>
--
GitLab