From dc73819f2ef459696502877e89e46f41406c8d6b Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 20 Jul 2005 23:57:46 +0000
Subject: [PATCH] Fix breakage of INSTALL document build.

---
 doc/src/sgml/installation.sgml | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 4f9f50cc01..c5bca8dacf 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.240 2005/07/06 21:04:14 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.241 2005/07/20 23:57:46 tgl Exp $ -->
 
 <chapter id="installation">
  <title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -870,10 +870,12 @@ su - postgres
          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.
+         the full range (see
+         <![%standalone-include[the documentation about datetime datatypes]]>
+         <![%standalone-ignore[<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>