From 63ee91fc451f11422371baec7e6041bd77cc414e Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 3 Jan 2008 21:36:15 +0000
Subject: [PATCH] Update release notes for security releases.

Security: CVE-2007-4769, CVE-2007-4772, CVE-2007-6067, CVE-2007-6600, CVE-2007-6601
---
 doc/src/sgml/release.sgml | 9588 +++++++++++++++++++------------------
 1 file changed, 4926 insertions(+), 4662 deletions(-)

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 12873c5c4e9..79d776cefd2 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.58 2007/09/16 03:03:55 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.235.2.59 2008/01/03 21:36:15 tgl Exp $ -->
 <!--
 
 Typical markup:
@@ -26,7 +26,7 @@ non-ASCII characters            convert to HTML4 entity (&) escapes
 wrap long lines
 
 For new features, add links to the documentation sections.  Use </link>
-so that perl can remove it so HISTORY.html can be created with no
+so that Perl can remove it so HISTORY.html can be created with no
 links to the main documentation.  This was added only in 8.2, so don't
 do it for earlier branch release files.
 
@@ -35,387 +35,539 @@ do it for earlier branch release files.
 <appendix id="release">
  <title>Release Notes</title>
 
-  <sect1 id="release-7-4-18">
-   <title>Release 7.4.18</title>
+ <sect1 id="release-7-4-19">
+  <title>Release 7.4.19</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2007-09-17</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2008-01-07</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.18,
+   including fixes for significant security issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.19</title>
 
    <para>
-    This release contains fixes from 7.4.17.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.18</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
-    </para>
+  <sect2>
+   <title>Changes</title>
 
-   </sect2>
+   <itemizedlist>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+     <para>
+      Prevent functions in indexes from executing with the privileges of
+      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
+     </para>
 
-    <itemizedlist>
+     <para>
+      Functions used in index expressions and partial-index
+      predicates are evaluated whenever a new table entry is made.  It has
+      long been understood that this poses a risk of trojan-horse code
+      execution if one modifies a table owned by an untrustworthy user.
+      (Note that triggers, defaults, check constraints, etc. pose the
+      same type of risk.)  But functions in indexes pose extra danger
+      because they will be executed by routine maintenance operations
+      such as <command>VACUUM FULL</>, which are commonly performed
+      automatically under a superuser account.  For example, a nefarious user
+      can execute code with superuser privileges by setting up a
+      trojan-horse index definition and waiting for the next routine vacuum.
+      The fix arranges for standard maintenance operations
+      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
+      and <command>CLUSTER</>) to execute as the table owner rather than
+      the calling user, using the same privilege-switching mechanism already
+      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
+      this security measure, execution of <command>SET SESSION
+      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
+      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Prevent index corruption when a transaction inserts rows and
-       then aborts close to the end of a concurrent <command>VACUUM</>
-       on the same table (Tom)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Repair assorted bugs in the regular-expression package (Tom, Will Drewry)
+     </para>
 
-     <listitem>
-      <para>
-       Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-      </para>
-     </listitem>
+     <para>
+      Suitably crafted regular-expression patterns could cause crashes,
+      infinite or near-infinite looping, and/or massive memory consumption,
+      all of which pose denial-of-service hazards for applications that
+      accept regex search patterns from untrustworthy sources.
+      (CVE-2007-4769, CVE-2007-4772, CVE-2007-6067)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Fix excessive logging of <acronym>SSL</> error messages (Tom)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Require non-superusers who use <filename>/contrib/dblink</> to use only
+      password authentication, as a security measure (Joe)
+     </para>
 
-     <listitem>
-      <para>
-       Fix crash when <varname>log_min_error_statement</> logging runs out
-       of memory (Tom)
-      </para>
-     </listitem>
+     <para>
+      The fix that appeared for this in 7.4.18 was incomplete, as it plugged
+      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
+      CVE-2007-3278)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Prevent <command>CLUSTER</> from failing
-       due to attempting to process temporary tables of other sessions (Alvaro)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Fix planner failure in some cases of <literal>WHERE false AND var IN
+      (SELECT ...)</> (Tom)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Require non-superusers who use <filename>/contrib/dblink</> to use only
-       password authentication, as a security measure (Joe)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Fix potential crash in <function>translate()</> when using a multibyte
+      database encoding (Tom)
+     </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+     <para>
+      Fix PL/Python to not crash on long exception messages (Alvaro)
+     </para>
+    </listitem>
 
-   </sect2>
-  </sect1>
- 
-  <sect1 id="release-7-4-17">
-   <title>Release 7.4.17</title>
+    <listitem>
+     <para>
+      <application>ecpg</> parser fixes (Michael)
+     </para>
+    </listitem>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2007-04-23</simpara>
-   </note>
+    <listitem>
+     <para>
+      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
+      NULL rowid as a category in its own right, rather than crashing (Joe)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Fix <type>tsvector</> and <type>tsquery</> output routines to
+      escape backslashes correctly (Teodor, Bruce)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Fix crash of <function>to_tsvector()</> on huge input strings (Teodor)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Require a specific version of <productname>Autoconf</> to be used
+      when re-generating the <command>configure</> script (Peter)
+     </para>
+
+     <para>
+      This affects developers and packagers only.  The change was made
+      to prevent accidental use of untested combinations of
+      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
+      You can remove the version check if you really want to use a
+      different <productname>Autoconf</> version, but it's
+      your responsibility whether the result works or not.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
+ <sect1 id="release-7-4-18">
+  <title>Release 7.4.18</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2007-09-17</simpara>
+  </note>
+
+  <para>
+   This release contains fixes from 7.4.17.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.18</title>
 
    <para>
-    This release contains fixes from 7.4.16,
-    including a security fix.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.17</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
-    </para>
+  <sect2>
+   <title>Changes</title>
 
-   </sect2>
+   <itemizedlist>
 
-   <sect2>
-    <title>Changes</title>
-
-    <itemizedlist>
-
-     <listitem>
+    <listitem>
      <para>
-      Support explicit placement of the temporary-table schema within
-      <varname>search_path</>, and disable searching it for functions
-      and operators (Tom)
+      Prevent index corruption when a transaction inserts rows and
+      then aborts close to the end of a concurrent <command>VACUUM</>
+      on the same table (Tom)
      </para>
+    </listitem>
+
+    <listitem>
      <para>
-      This is needed to allow a security-definer function to set a
-      truly secure value of <varname>search_path</>.  Without it,
-      an unprivileged SQL user can use temporary objects to execute code
-      with the privileges of the security-definer function (CVE-2007-2138).
-      See <command>CREATE FUNCTION</> for more information.
+      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
      </para>
-     </listitem>
+    </listitem>
 
-     <listitem>
+    <listitem>
      <para>
-      <filename>/contrib/tsearch2</> crash fixes (Teodor)
+      Fix excessive logging of <acronym>SSL</> error messages (Tom)
      </para>
-     </listitem>
+    </listitem>
 
-     <listitem>
+    <listitem>
      <para>
-      Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-      <command>UPDATE</> chains (Tom, Pavan Deolasee)
+      Fix crash when <varname>log_min_error_statement</> logging runs out
+      of memory (Tom)
      </para>
-     </listitem>
+    </listitem>
 
-     <listitem>
+    <listitem>
      <para>
-      Fix PANIC during enlargement of a hash index (bug introduced in 7.4.15)
-      (Tom)
+      Prevent <command>CLUSTER</> from failing
+      due to attempting to process temporary tables of other sessions (Alvaro)
      </para>
-     </listitem>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+     <para>
+      Require non-superusers who use <filename>/contrib/dblink</> to use only
+      password authentication, as a security measure (Joe)
+     </para>
+    </listitem>
 
-   </sect2>
-  </sect1>
- 
-  <sect1 id="release-7-4-16">
-   <title>Release 7.4.16</title>
+   </itemizedlist>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2007-02-05</simpara>
-   </note>
+  </sect2>
+ </sect1>
+
+ <sect1 id="release-7-4-17">
+  <title>Release 7.4.17</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2007-04-23</simpara>
+  </note>
+
+  <para>
+   This release contains fixes from 7.4.16,
+   including a security fix.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.17</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.15, including
-    a security fix.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.16</title>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
+
+   <itemizedlist>
+
+    <listitem>
     <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
+     Support explicit placement of the temporary-table schema within
+     <varname>search_path</>, and disable searching it for functions
+     and operators (Tom)
     </para>
+    <para>
+     This is needed to allow a security-definer function to set a
+     truly secure value of <varname>search_path</>.  Without it,
+     an unprivileged SQL user can use temporary objects to execute code
+     with the privileges of the security-definer function (CVE-2007-2138).
+     See <command>CREATE FUNCTION</> for more information.
+    </para>
+    </listitem>
 
-   </sect2>
+    <listitem>
+    <para>
+     <filename>/contrib/tsearch2</> crash fixes (Teodor)
+    </para>
+    </listitem>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+    <para>
+     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
+     <command>UPDATE</> chains (Tom, Pavan Deolasee)
+    </para>
+    </listitem>
 
-    <itemizedlist>
+    <listitem>
+    <para>
+     Fix PANIC during enlargement of a hash index (bug introduced in 7.4.15)
+     (Tom)
+    </para>
+    </listitem>
 
-     <listitem>
-     <para>
-      Remove security vulnerability that allowed connected users
-      to read backend memory (Tom)
-     </para>
-     <para>
-      The vulnerability involves suppressing the normal check that a SQL
-      function returns the data type it's declared to, or changing the
-      data type of a table column used in a SQL function (CVE-2007-0555).
-      This error can easily be exploited to cause a backend crash, and in
-      principle might be used to read database content that the user
-      should not be able to access.
-     </para>
-     </listitem>
+   </itemizedlist>
 
-     <listitem>
-     <para>
-      Fix rare bug wherein btree index page splits could fail
-      due to choosing an infeasible split point (Heikki Linnakangas)
-     </para>
-     </listitem>
+  </sect2>
+ </sect1>
 
-     <listitem>
-     <para>
-      Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
-     </para>
-     </listitem>
+ <sect1 id="release-7-4-16">
+  <title>Release 7.4.16</title>
 
-     <listitem>
-     <para>
-      Tighten security of multi-byte character processing for UTF8 sequences
-      over three bytes long (Tom)
-     </para>
-     </listitem>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-02-05</simpara>
+  </note>
 
-    </itemizedlist>
+  <para>
+   This release contains a variety of fixes from 7.4.15, including
+   a security fix.
+  </para>
 
-   </sect2>
-  </sect1>
-
-  <sect1 id="release-7-4-15">
-   <title>Release 7.4.15</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2007-01-08</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.4.16</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.14.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.15</title>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
+
+   <itemizedlist>
+
+    <listitem>
     <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
+     Remove security vulnerability that allowed connected users
+     to read backend memory (Tom)
     </para>
+    <para>
+     The vulnerability involves suppressing the normal check that a SQL
+     function returns the data type it's declared to, or changing the
+     data type of a table column used in a SQL function (CVE-2007-0555).
+     This error can easily be exploited to cause a backend crash, and in
+     principle might be used to read database content that the user
+     should not be able to access.
+    </para>
+    </listitem>
 
-   </sect2>
+    <listitem>
+    <para>
+     Fix rare bug wherein btree index page splits could fail
+     due to choosing an infeasible split point (Heikki Linnakangas)
+    </para>
+    </listitem>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+    <para>
+     Fix for rare Assert() crash triggered by <literal>UNION</> (Tom)
+    </para>
+    </listitem>
 
-    <itemizedlist>
+    <listitem>
+    <para>
+     Tighten security of multi-byte character processing for UTF8 sequences
+     over three bytes long (Tom)
+    </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Improve handling of <function>getaddrinfo()</> on AIX (Tom)
-      </para>
+   </itemizedlist>
 
-      <para>
-       This fixes a problem with starting the statistics collector,
-       among other things.
-      </para>
-     </listitem>
+  </sect2>
+ </sect1>
 
-      <listitem>
-       <para>
-        Fix <quote>failed to re-find parent key</> errors in
-        <command>VACUUM</> (Tom)
-       </para>
-      </listitem>
+ <sect1 id="release-7-4-15">
+  <title>Release 7.4.15</title>
 
-      <listitem>
-       <para>
-        Fix bugs affecting multi-gigabyte hash indexes (Tom)
-       </para>
-      </listitem>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-01-08</simpara>
+  </note>
 
-     <listitem>
-      <para>
-       Fix error when constructing an <literal>ARRAY[]</> made up of multiple
-       empty elements (Tom)
-      </para>
-     </listitem>
+  <para>
+   This release contains a variety of fixes from 7.4.14.
+  </para>
 
-     <listitem>
-      <para>
-       <function>to_number()</> and <function>to_char(numeric)</>
-       are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-       new <application>initdb</> installs (Tom)
-      </para>
-
-      <para>
-       This is because <varname>lc_numeric</> can potentially
-       change the output of these functions.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Improve index usage of regular expressions that use parentheses (Tom)
-      </para>
-
-      <para>
-       This improves <application>psql</> <literal>\d</> performance also.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-
-   </sect2>
-  </sect1>
-
-  <sect1 id="release-7-4-14">
-   <title>Release 7.4.14</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2006-10-16</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.4.15</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.13.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.14</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
-    </para>
+  <sect2>
+   <title>Changes</title>
 
-   </sect2>
+   <itemizedlist>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+     <para>
+      Improve handling of <function>getaddrinfo()</> on AIX (Tom)
+     </para>
+
+     <para>
+      This fixes a problem with starting the statistics collector,
+      among other things.
+     </para>
+    </listitem>
+
+     <listitem>
+      <para>
+       Fix <quote>failed to re-find parent key</> errors in
+       <command>VACUUM</> (Tom)
+      </para>
+     </listitem>
+
+     <listitem>
+      <para>
+       Fix bugs affecting multi-gigabyte hash indexes (Tom)
+      </para>
+     </listitem>
+
+    <listitem>
+     <para>
+      Fix error when constructing an <literal>ARRAY[]</> made up of multiple
+      empty elements (Tom)
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      <function>to_number()</> and <function>to_char(numeric)</>
+      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
+      new <application>initdb</> installs (Tom)
+     </para>
+
+     <para>
+      This is because <varname>lc_numeric</> can potentially
+      change the output of these functions.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Improve index usage of regular expressions that use parentheses (Tom)
+     </para>
+
+     <para>
+      This improves <application>psql</> <literal>\d</> performance also.
+     </para>
+    </listitem>
+
+   </itemizedlist>
+
+  </sect2>
+ </sect1>
+
+ <sect1 id="release-7-4-14">
+  <title>Release 7.4.14</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2006-10-16</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.13.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.14</title>
+
+   <para>
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
+   </para>
+
+  </sect2>
+
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix core dump when an untyped literal is taken as
 ANYARRAY</para></listitem>
 <listitem><para>Fix <function>string_to_array()</> to handle overlapping
-  matches for the separator string</para>
+ matches for the separator string</para>
 <para>For example, <literal>string_to_array('123xx456xxx789', 'xx')</>.
 </para></listitem>
 <listitem><para>Fix corner cases in pattern matching for
-  <application>psql</>'s <literal>\d</> commands</para></listitem>
+ <application>psql</>'s <literal>\d</> commands</para></listitem>
 <listitem><para>Fix index-corrupting bugs in /contrib/ltree
-  (Teodor)</para></listitem>
+ (Teodor)</para></listitem>
 <listitem><para>Fix backslash escaping in /contrib/dbmirror</para></listitem>
 <listitem><para>Adjust regression tests for recent changes in US DST laws
 </para> </listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-13">
-   <title>Release 7.4.13</title>
+ <sect1 id="release-7-4-13">
+  <title>Release 7.4.13</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-05-23</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-05-23</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.12,
+   including patches for extremely serious security issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.13</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.12,
-    including patches for extremely serious security issues.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.13</title>
+   <para>
+    Full security against the SQL-injection attacks described in
+    CVE-2006-2313 and CVE-2006-2314 might require changes in application
+    code.  If you have applications that embed untrustworthy strings
+    into SQL commands, you should examine them as soon as possible to
+    ensure that they are using recommended escaping techniques.  In
+    most cases, applications should be using subroutines provided by
+    libraries or drivers (such as <application>libpq</>'s
+    <function>PQescapeStringConn()</>) to perform string escaping,
+    rather than relying on <foreignphrase>ad hoc</> code to do it.
+   </para>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
-    </para>
-
-    <para>
-     Full security against the SQL-injection attacks described in
-     CVE-2006-2313 and CVE-2006-2314 might require changes in application
-     code.  If you have applications that embed untrustworthy strings
-     into SQL commands, you should examine them as soon as possible to
-     ensure that they are using recommended escaping techniques.  In
-     most cases, applications should be using subroutines provided by
-     libraries or drivers (such as <application>libpq</>'s
-     <function>PQescapeStringConn()</>) to perform string escaping,
-     rather than relying on <foreignphrase>ad hoc</> code to do it.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Change the server to reject invalidly-encoded multibyte
@@ -481,33 +633,33 @@ Fuhr)</para></listitem>
 <listitem><para>Fix various minor memory leaks</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-12">
-   <title>Release 7.4.12</title>
+ <sect1 id="release-7-4-12">
+  <title>Release 7.4.12</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-02-14</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-02-14</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.11.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.12</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.11.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.11, see the release
+    notes for 7.4.11.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.4.12</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.11, see the release
-     notes for 7.4.11.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -542,36 +694,36 @@ and <function>isinf</> during configure (Tom)</para></listitem>
 
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-11">
-   <title>Release 7.4.11</title>
+ <sect1 id="release-7-4-11">
+  <title>Release 7.4.11</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-01-09</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-01-09</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.10.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.11</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.10.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.8, see the release
+    notes for 7.4.8.
+    Also, you might need to <command>REINDEX</> indexes on textual
+    columns after updating, if you are affected by the locale or
+    <application>plperl</> issues described below.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.4.11</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.8, see the release
-     notes for 7.4.8.
-     Also, you might need to <command>REINDEX</> indexes on textual
-     columns after updating, if you are affected by the locale or
-     <application>plperl</> issues described below.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -607,33 +759,33 @@ what's actually returned by the query (Joe)</para></listitem>
 
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-10">
-   <title>Release 7.4.10</title>
+ <sect1 id="release-7-4-10">
+  <title>Release 7.4.10</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-12-12</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-12-12</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.9.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.10</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.9.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.8, see the release
+    notes for 7.4.8.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.4.10</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.8, see the release
-     notes for 7.4.8.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -658,33 +810,33 @@ only supported with merge-joinable join conditions</>.</para></listitem>
 table has been dropped</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-9">
-   <title>Release 7.4.9</title>
+ <sect1 id="release-7-4-9">
+  <title>Release 7.4.9</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-10-04</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-10-04</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.8.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.9</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.8.
+    A dump/restore is not required for those running 7.4.X.  However,
+    if you are upgrading from a version earlier than 7.4.8, see the release
+    notes for 7.4.8.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.4.9</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     if you are upgrading from a version earlier than 7.4.8, see the release
-     notes for 7.4.8.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix error that allowed <command>VACUUM</> to remove
@@ -725,119 +877,119 @@ the variable is of pass-by-reference type</para></listitem>
 code</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-8">
-   <title>Release 7.4.8</title>
+ <sect1 id="release-7-4-8">
+  <title>Release 7.4.8</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-05-09</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-05-09</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.7, including several
+   security-related issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.8</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.7, including several
-    security-related issues.
+    A dump/restore is not required for those running 7.4.X.  However,
+    it is one possible way of handling two significant security problems
+    that have been found in the initial contents of 7.4.X system
+    catalogs.  A dump/initdb/reload sequence using 7.4.8's initdb will
+    automatically correct these problems.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.4.8</title>
+   <para>
+    The larger security problem is that the built-in character set encoding
+    conversion functions can be invoked from SQL commands by unprivileged
+    users, but the functions were not designed for such use and are not
+    secure against malicious choices of arguments.  The fix involves changing
+    the declared parameter list of these functions so that they can no longer
+    be invoked from SQL commands.  (This does not affect their normal use
+    by the encoding conversion machinery.)
+   </para>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     it is one possible way of handling two significant security problems
-     that have been found in the initial contents of 7.4.X system
-     catalogs.  A dump/initdb/reload sequence using 7.4.8's initdb will
-     automatically correct these problems.
-    </para>
+   <para>
+    The lesser problem is that the <filename>contrib/tsearch2</> module
+    creates several functions that are misdeclared to return
+    <type>internal</> when they do not accept <type>internal</> arguments.
+    This breaks type safety for all functions using <type>internal</>
+    arguments.
+   </para>
 
-    <para>
-     The larger security problem is that the built-in character set encoding
-     conversion functions can be invoked from SQL commands by unprivileged
-     users, but the functions were not designed for such use and are not
-     secure against malicious choices of arguments.  The fix involves changing
-     the declared parameter list of these functions so that they can no longer
-     be invoked from SQL commands.  (This does not affect their normal use
-     by the encoding conversion machinery.)
-    </para>
+   <para>
+    It is strongly recommended that all installations repair these errors,
+    either by initdb or by following the manual repair procedures given
+    below.  The errors at least allow unprivileged database users to crash
+    their server process, and might allow unprivileged users to gain the
+    privileges of a database superuser.
+   </para>
 
-    <para>
-     The lesser problem is that the <filename>contrib/tsearch2</> module
-     creates several functions that are misdeclared to return
-     <type>internal</> when they do not accept <type>internal</> arguments.
-     This breaks type safety for all functions using <type>internal</>
-     arguments.
-    </para>
-
-    <para>
-     It is strongly recommended that all installations repair these errors,
-     either by initdb or by following the manual repair procedures given
-     below.  The errors at least allow unprivileged database users to crash
-     their server process, and might allow unprivileged users to gain the
-     privileges of a database superuser.
-    </para>
-
-    <para>
-     If you wish not to do an initdb, perform the following procedures instead.
-     As the database superuser, do:
+   <para>
+    If you wish not to do an initdb, perform the following procedures instead.
+    As the database superuser, do:
 
 <programlisting>
 BEGIN;
 UPDATE pg_proc SET proargtypes[3] = 'internal'::regtype
 WHERE pronamespace = 11 AND pronargs = 5
-      AND proargtypes[2] = 'cstring'::regtype;
+     AND proargtypes[2] = 'cstring'::regtype;
 -- The command should report having updated 90 rows;
 -- if not, rollback and investigate instead of committing!
 COMMIT;
 </programlisting>
 
-     Next, if you have installed <filename>contrib/tsearch2</>, do:
+    Next, if you have installed <filename>contrib/tsearch2</>, do:
 
 <programlisting>
 BEGIN;
 UPDATE pg_proc SET proargtypes[0] = 'internal'::regtype
 WHERE oid IN (
-    'dex_init(text)'::regprocedure,
-    'snb_en_init(text)'::regprocedure,
-    'snb_ru_init(text)'::regprocedure,
-    'spell_init(text)'::regprocedure,
-    'syn_init(text)'::regprocedure
+   'dex_init(text)'::regprocedure,
+   'snb_en_init(text)'::regprocedure,
+   'snb_ru_init(text)'::regprocedure,
+   'spell_init(text)'::regprocedure,
+   'syn_init(text)'::regprocedure
 );
 -- The command should report having updated 5 rows;
 -- if not, rollback and investigate instead of committing!
 COMMIT;
 </programlisting>
 
-     If this command fails with a message like <quote>function
-     "dex_init(text)" does not exist</>, then either <filename>tsearch2</>
-     is not installed in this database, or you already did the update.
-    </para>
+    If this command fails with a message like <quote>function
+    "dex_init(text)" does not exist</>, then either <filename>tsearch2</>
+    is not installed in this database, or you already did the update.
+   </para>
 
-    <para>
-     The above procedures must be carried out in <emphasis>each</> database
-     of an installation, including <literal>template1</>, and ideally
-     including <literal>template0</> as well.  If you do not fix the
-     template databases then any subsequently created databases will contain
-     the same errors.  <literal>template1</> can be fixed in the same way
-     as any other database, but fixing <literal>template0</> requires
-     additional steps.  First, from any database issue:
+   <para>
+    The above procedures must be carried out in <emphasis>each</> database
+    of an installation, including <literal>template1</>, and ideally
+    including <literal>template0</> as well.  If you do not fix the
+    template databases then any subsequently created databases will contain
+    the same errors.  <literal>template1</> can be fixed in the same way
+    as any other database, but fixing <literal>template0</> requires
+    additional steps.  First, from any database issue:
 <programlisting>
 UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
 </programlisting>
-      Next connect to <literal>template0</> and perform the above repair
-      procedures.  Finally, do:
+     Next connect to <literal>template0</> and perform the above repair
+     procedures.  Finally, do:
 <programlisting>
 -- re-freeze template0:
 VACUUM FREEZE;
 -- and protect it against future alterations:
 UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
 </programlisting>
-    </para>
-   </sect2>
+   </para>
+  </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Change encoding function signature to prevent
@@ -874,10 +1026,10 @@ This error only occurred when the
 <listitem><para>Ensure operations done during backend shutdown are counted by
 statistics collector</para>
 <para>
- This is expected to resolve reports of <application>pg_autovacuum</>
- not vacuuming the system catalogs often enough &mdash; it was not being
- told about catalog deletions caused by temporary table removal during
- backend exit.
+This is expected to resolve reports of <application>pg_autovacuum</>
+not vacuuming the system catalogs often enough &mdash; it was not being
+told about catalog deletions caused by temporary table removal during
+backend exit.
 </para></listitem>
 <listitem><para>Additional buffer overrun checks in plpgsql
 (Neil)</para></listitem>
@@ -907,32 +1059,32 @@ holder of the lock released it within a very narrow window.
 <command>ALTER TABLE SET WITHOUT OIDS</></para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-7">
-   <title>Release 7.4.7</title>
+ <sect1 id="release-7-4-7">
+  <title>Release 7.4.7</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-01-31</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-01-31</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.6, including several
+   security-related issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.4.7</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.6, including several
-    security-related issues.
+    A dump/restore is not required for those running 7.4.X.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.4.7</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Disallow <command>LOAD</> to non-superusers</para>
@@ -965,32 +1117,32 @@ datestyles</para></listitem>
 GMT</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-6">
-   <title>Release 7.4.6</title>
+ <sect1 id="release-7-4-6">
+  <title>Release 7.4.6</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-10-22</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-10-22</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.5.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.6</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.5.
+    A dump/restore is not required for those running 7.4.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.4.6</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair possible failure to update hint bits on disk</para>
@@ -1035,32 +1187,32 @@ This could arise in cases such as CLUSTER after ALTER TABLE DROP COLUMN.
 ECPG prepare statement</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-5">
-   <title>Release 7.4.5</title>
+ <sect1 id="release-7-4-5">
+  <title>Release 7.4.5</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-08-18</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-08-18</simpara>
+  </note>
+
+  <para>
+   This release contains one serious bug fix over 7.4.4.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.5</title>
 
    <para>
-    This release contains one serious bug fix over 7.4.4.
+    A dump/restore is not required for those running 7.4.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.4.5</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair possible crash during concurrent B-tree index insertions</para>
@@ -1071,32 +1223,32 @@ still worth a re-release.  The bug does not exist in pre-7.4 releases.
 </para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-4">
-   <title>Release 7.4.4</title>
+ <sect1 id="release-7-4-4">
+  <title>Release 7.4.4</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-08-16</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-08-16</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.3.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.4</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.3.
+    A dump/restore is not required for those running 7.4.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.4.4</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Prevent possible loss of committed transactions during crash</para>
@@ -1121,32 +1273,32 @@ aggregate plan</para></listitem>
 <listitem><para>Translation updates (various contributors)</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-3">
-   <title>Release 7.4.3</title>
+ <sect1 id="release-7-4-3">
+  <title>Release 7.4.3</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-06-14</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-06-14</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.2.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.3</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.2.
+    A dump/restore is not required for those running 7.4.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.4.3</title>
-
-    <para>
-     A dump/restore is not required for those running 7.4.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix temporary memory leak when using non-hashed aggregates (Tom)</para></listitem>
@@ -1171,64 +1323,64 @@ names from outer query levels.
 <listitem><para>Do not generate <quote>NATURAL CROSS JOIN</> when decompiling rules (Tom)</para></listitem>
 <listitem><para>Add checks for invalid field length in binary COPY (Tom)</para>
 <para>
-  This fixes a difficult-to-exploit security hole.
+ This fixes a difficult-to-exploit security hole.
 </para></listitem>
 <listitem><para>Avoid locking conflict between <command>ANALYZE</command> and <command>LISTEN</command>/<command>NOTIFY</command></para></listitem>
 <listitem><para>Numerous translation updates (various contributors)</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-2">
-   <title>Release 7.4.2</title>
+ <sect1 id="release-7-4-2">
+  <title>Release 7.4.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-03-08</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-03-08</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.1.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.2</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.1.
+    A dump/restore is not required for those running 7.4.X.  However,
+    it might be advisable as the easiest method of incorporating fixes for
+    two errors that have been found in the initial contents of 7.4.X system
+    catalogs.  A dump/initdb/reload sequence using 7.4.2's initdb will
+    automatically correct these problems.
    </para>
 
+   <para>
+    The more severe of the two errors is that data type <type>anyarray</>
+    has the wrong alignment label; this is a problem because the
+    <structname>pg_statistic</> system catalog uses <type>anyarray</>
+    columns.  The mislabeling can cause planner misestimations and even
+    crashes when planning queries that involve <literal>WHERE</> clauses on
+    double-aligned columns (such as <type>float8</> and <type>timestamp</>).
+    It is strongly recommended that all installations repair this error,
+    either by initdb or by following the manual repair procedure given
+    below.
+   </para>
 
-   <sect2>
-    <title>Migration to version 7.4.2</title>
+   <para>
+    The lesser error is that the system view <structname>pg_settings</>
+    ought to be marked as having public update access, to allow
+    <literal>UPDATE pg_settings</> to be used as a substitute for
+    <command>SET</>.  This can also be fixed either by initdb or manually,
+    but it is not necessary to fix unless you want to use <literal>UPDATE
+    pg_settings</>.
+   </para>
 
-    <para>
-     A dump/restore is not required for those running 7.4.X.  However,
-     it might be advisable as the easiest method of incorporating fixes for
-     two errors that have been found in the initial contents of 7.4.X system
-     catalogs.  A dump/initdb/reload sequence using 7.4.2's initdb will
-     automatically correct these problems.
-    </para>
-
-    <para>
-     The more severe of the two errors is that data type <type>anyarray</>
-     has the wrong alignment label; this is a problem because the
-     <structname>pg_statistic</> system catalog uses <type>anyarray</>
-     columns.  The mislabeling can cause planner misestimations and even
-     crashes when planning queries that involve <literal>WHERE</> clauses on
-     double-aligned columns (such as <type>float8</> and <type>timestamp</>).
-     It is strongly recommended that all installations repair this error,
-     either by initdb or by following the manual repair procedure given
-     below.
-    </para>
-
-    <para>
-     The lesser error is that the system view <structname>pg_settings</>
-     ought to be marked as having public update access, to allow
-     <literal>UPDATE pg_settings</> to be used as a substitute for
-     <command>SET</>.  This can also be fixed either by initdb or manually,
-     but it is not necessary to fix unless you want to use <literal>UPDATE
-     pg_settings</>.
-    </para>
-
-    <para>
-     If you wish not to do an initdb, the following procedure will work
-     for fixing <structname>pg_statistic</>.  As the database superuser,
-     do:
+   <para>
+    If you wish not to do an initdb, the following procedure will work
+    for fixing <structname>pg_statistic</>.  As the database superuser,
+    do:
 
 <programlisting>
 -- clear out old data in pg_statistic:
@@ -1245,46 +1397,46 @@ UPDATE pg_attribute SET attalign = 'd' WHERE atttypid = 2277;
 ANALYZE;
 </programlisting>
 
-     This can be done in a live database, but beware that all backends
-     running in the altered database must be restarted before it is safe to
-     repopulate <structname>pg_statistic</>.
-    </para>
+    This can be done in a live database, but beware that all backends
+    running in the altered database must be restarted before it is safe to
+    repopulate <structname>pg_statistic</>.
+   </para>
 
-    <para>
-     To repair the <structname>pg_settings</> error, simply do:
+   <para>
+    To repair the <structname>pg_settings</> error, simply do:
 <programlisting>
 GRANT SELECT, UPDATE ON pg_settings TO PUBLIC;
 </programlisting>
-    </para>
+   </para>
 
-    <para>
-     The above procedures must be carried out in <emphasis>each</> database
-     of an installation, including <literal>template1</>, and ideally
-     including <literal>template0</> as well.  If you do not fix the
-     template databases then any subsequently created databases will contain
-     the same errors.  <literal>template1</> can be fixed in the same way
-     as any other database, but fixing <literal>template0</> requires
-     additional steps.  First, from any database issue:
+   <para>
+    The above procedures must be carried out in <emphasis>each</> database
+    of an installation, including <literal>template1</>, and ideally
+    including <literal>template0</> as well.  If you do not fix the
+    template databases then any subsequently created databases will contain
+    the same errors.  <literal>template1</> can be fixed in the same way
+    as any other database, but fixing <literal>template0</> requires
+    additional steps.  First, from any database issue:
 <programlisting>
 UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
 </programlisting>
-      Next connect to <literal>template0</> and perform the above repair
-      procedures.  Finally, do:
+     Next connect to <literal>template0</> and perform the above repair
+     procedures.  Finally, do:
 <programlisting>
 -- re-freeze template0:
 VACUUM FREEZE;
 -- and protect it against future alterations:
 UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
 </programlisting>
-    </para>
-   </sect2>
+   </para>
+  </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <para>
-    Release 7.4.2 incorporates all the fixes included in release 7.3.6,
-    plus the following fixes:
+   Release 7.4.2 incorporates all the fixes included in release 7.3.6,
+   plus the following fixes:
 </para>
 
 <itemizedlist>
@@ -1318,82 +1470,82 @@ inconveniences associated with the <literal>i/I</> problem.</para></listitem>
 <listitem><para>Various JDBC fixes</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-4-1">
-   <title>Release 7.4.1</title>
+ <sect1 id="release-7-4-1">
+  <title>Release 7.4.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2003-12-22</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2003-12-22</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.4.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.4.1</title>
 
    <para>
-    This release contains a variety of fixes from 7.4.
+    A dump/restore is <emphasis>not</emphasis> required for those
+    running 7.4.
    </para>
 
-
-   <sect2>
-    <title>Migration to version 7.4.1</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those
-     running 7.4.
-    </para>
-
-    <para>
-     If you want to install the fixes in the information schema
-     you need to reload it into the database.
-     This is either accomplished by initializing a new cluster
-     by running <command>initdb</command>, or by running the following
-     sequence of SQL commands in each database (ideally including
-     <literal>template1</literal>) as a superuser in
-     <application>psql</application>, after installing the new release:
+   <para>
+    If you want to install the fixes in the information schema
+    you need to reload it into the database.
+    This is either accomplished by initializing a new cluster
+    by running <command>initdb</command>, or by running the following
+    sequence of SQL commands in each database (ideally including
+    <literal>template1</literal>) as a superuser in
+    <application>psql</application>, after installing the new release:
 <programlisting>
 DROP SCHEMA information_schema CASCADE;
 \i /usr/local/pgsql/share/information_schema.sql
 </programlisting>
-     Substitute your installation path in the second command.
-    </para>
+    Substitute your installation path in the second command.
+   </para>
 
-   </sect2>
+  </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fixed bug in <command>CREATE SCHEMA</command> parsing in ECPG (Michael)</para></listitem>
 <listitem><para>Fix compile error when <option>--enable-thread-safety</option> and <option>--with-perl</option> are used together (Peter)</para></listitem>
 <listitem><para>Fix for subqueries that used hash joins (Tom)</para>
 <para>
-    Certain subqueries that used hash joins would crash because of
-    improperly shared structures.
+   Certain subqueries that used hash joins would crash because of
+   improperly shared structures.
 </para></listitem>
 <listitem><para>Fix free space map compaction bug (Tom)</para>
 <para>
-    This fixes a bug where compaction of the free space map could lead
-    to a database server shutdown.
+   This fixes a bug where compaction of the free space map could lead
+   to a database server shutdown.
 </para>
 </listitem>
 <listitem><para>Fix for Borland compiler build of libpq (Bruce)</para></listitem>
 <listitem><para>Fix <function>netmask()</function> and <function>hostmask()</function> to return the maximum-length masklen (Tom)</para>
 <para>
-    Fix these functions to return values consistent with pre-7.4
-    releases.
+   Fix these functions to return values consistent with pre-7.4
+   releases.
 </para>
 </listitem>
 <listitem><para>Several <filename>contrib/pg_autovacuum</filename> fixes</para>
 <para>
-    Fixes include improper variable initialization, missing vacuum after
-    <command>TRUNCATE</command>, and duration computation overflow for long vacuums.
+   Fixes include improper variable initialization, missing vacuum after
+   <command>TRUNCATE</command>, and duration computation overflow for long vacuums.
 </para>
 </listitem>
 <listitem><para>Allow compile of <filename>contrib/cube</filename> under Cygwin (Jason Tishler)</para></listitem>
 <listitem><para>Fix Solaris use of password file when no passwords are defined (Tom)</para>
 <para>
-    Fix crash on Solaris caused by use of any type of password
-    authentication when no passwords were defined.
+   Fix crash on Solaris caused by use of any type of password
+   authentication when no passwords were defined.
 </para>
 </listitem>
 <listitem><para>JDBC fix for thread problems, other fixes</para></listitem>
@@ -1404,9 +1556,9 @@ DROP SCHEMA information_schema CASCADE;
 <listitem><para>Make <function>PQescapeBytea</function> and <function>byteaout</function> consistent with each other (Joe)</para></listitem>
 <listitem><para>Escape <type>bytea</type> output for bytes &gt; 0x7e(Joe)</para>
 <para>
-  If different client encodings are used for <type>bytea</type> output and input, it
-  is possible for <type>bytea</type> values to be corrupted by the differing
-  encodings.  This fix escapes all bytes that might be affected.
+ If different client encodings are used for <type>bytea</type> output and input, it
+ is possible for <type>bytea</type> values to be corrupted by the differing
+ encodings.  This fix escapes all bytes that might be affected.
 </para>
 </listitem>
 <listitem><para>Added missing <function>SPI_finish()</function> calls to dblink's <function>get_tuple_of_interest()</function> (Joe)</para></listitem>
@@ -1417,2148 +1569,2260 @@ DROP SCHEMA information_schema CASCADE;
 <listitem><para>Allow <literal>COUNT('x')</literal> to work (Tom)</para></listitem>
 <listitem><para>Install ECPG include files for Informix compatibility into separate directory (Peter)</para>
 <para>
-  Some names of ECPG include files for Informix compatibility conflicted with operating system include files.
-  By installing them in their own directory, name conflicts have been reduced.
+ Some names of ECPG include files for Informix compatibility conflicted with operating system include files.
+ By installing them in their own directory, name conflicts have been reduced.
 </para>
 </listitem>
 <listitem><para>Fix SSL memory leak (Neil)</para>
 <para>
-  This release fixes a bug in 7.4 where SSL didn't free all memory it allocated.
+ This release fixes a bug in 7.4 where SSL didn't free all memory it allocated.
 </para>
 </listitem>
 <listitem><para>Prevent <filename>pg_service.conf</filename> from using service name as default dbname (Bruce)</para></listitem>
 <listitem><para>Fix local ident authentication on FreeBSD (Tom)</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
- <sect1 id="release-7-4">
-  <title>Release 7.4</title>
+<sect1 id="release-7-4">
+ <title>Release 7.4</title>
+
+ <note>
+  <title>Release date</title>
+  <simpara>2003-11-17</simpara>
+ </note>
+
+ <sect2>
+  <title>Overview</title>
+
+  <para>
+   Major changes in this release:
+  </para>
+
+  <variablelist>
+   <varlistentry>
+    <term>
+     <literal>IN</literal> / <literal>NOT IN</literal> subqueries are
+     now much more efficient
+    </term>
+
+    <listitem>
+     <para>
+      In previous releases, <literal>IN</literal>/<literal>NOT
+      IN</literal> subqueries were joined to the upper query by
+      sequentially scanning the subquery looking for a match.  The
+      7.4 code uses the same sophisticated techniques used by
+      ordinary joins and so is much faster.  An
+      <literal>IN</literal> will now usually be as fast as or faster
+      than an equivalent <literal>EXISTS</literal> subquery; this
+      reverses the conventional wisdom that applied to previous
+      releases.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Improved <literal>GROUP BY</literal> processing by using hash buckets
+    </term>
+
+    <listitem>
+     <para>
+      In previous releases, rows to be grouped had to be sorted
+      first.  The 7.4 code can do <literal>GROUP BY</literal>
+      without sorting, by accumulating results into a hash table
+      with one entry per group.  It will still use the sort
+      technique, however, if the hash table is estimated to be too
+      large to fit in <varname>sort_mem</>.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     New multikey hash join capability
+    </term>
+
+    <listitem>
+     <para>
+      In previous releases, hash joins could only occur on single
+      keys.  This release allows multicolumn hash joins.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Queries using the explicit <literal>JOIN</literal> syntax are
+     now better optimized
+    </term>
+
+    <listitem>
+     <para>
+      Prior releases evaluated queries using the explicit
+      <literal>JOIN</literal> syntax only in the order implied by
+      the syntax. 7.4 allows full optimization of these queries,
+      meaning the optimizer considers all possible join orderings
+      and chooses the most efficient.  Outer joins, however, must
+      still follow the declared ordering.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Faster and more powerful regular expression code
+    </term>
+
+    <listitem>
+     <para>
+      The entire regular expression module has been replaced with a
+      new version by Henry Spencer, originally written for Tcl.  The
+      code greatly improves performance and supports several flavors
+      of regular expressions.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Function-inlining for simple SQL functions
+    </term>
+
+    <listitem>
+     <para>
+      Simple SQL functions can now be inlined by including their SQL
+      in the main query.  This improves performance by eliminating
+      per-call overhead.  That means simple SQL functions now
+      behave like macros.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Full support for IPv6 connections and IPv6 address data types
+    </term>
+
+    <listitem>
+     <para>
+      Previous releases allowed only IPv4 connections, and the IP
+      data types only supported IPv4 addresses. This release adds
+      full IPv6 support in both of these areas.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Major improvements in SSL performance and reliability
+    </term>
+
+    <listitem>
+     <para>
+      Several people very familiar with the SSL API have overhauled
+      our SSL code to improve SSL key negotiation and error
+      recovery.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Make free space map efficiently reuse empty index pages,
+     and other free space management improvements
+    </term>
+
+    <listitem>
+     <para>
+      In previous releases, B-tree index pages that were left empty
+      because of deleted rows could only be reused by rows with
+      index values similar to the rows originally indexed on that
+      page. In 7.4, <command>VACUUM</command> records empty index
+      pages and allows them to be reused for any future index rows.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     SQL-standard information schema
+    </term>
+
+    <listitem>
+     <para>
+      The information schema provides a standardized and stable way
+      to access information about the schema objects defined in a
+      database.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Cursors conform more closely to the SQL standard
+    </term>
+
+    <listitem>
+     <para>
+      The commands <command>FETCH</command> and
+      <command>MOVE</command> have been overhauled to conform more
+      closely to the SQL standard.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Cursors can exist outside transactions
+    </term>
+
+    <listitem>
+     <para>
+      These cursors are also called holdable cursors.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     New client-to-server protocol
+    </term>
+
+    <listitem>
+     <para>
+      The new protocol adds error codes, more status information,
+      faster startup, better support for binary data transmission,
+      parameter values separated from SQL commands, prepared
+      statements available at the protocol level, and cleaner
+      recovery from <command>COPY</command> failures.  The older
+      protocol is still supported by both server and clients.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     <application>libpq</application> and
+     <application>ECPG</application> applications are now fully
+     thread-safe
+    </term>
+
+    <listitem>
+     <para>
+      While previous <application>libpq</application> releases
+      already supported threads, this release improves thread safety
+      by fixing some non-thread-safe code that was used during
+      database connection startup.  The <command>configure</command>
+      option <option>--enable-thread-safety</option> must be used to
+      enable this feature.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     New version of full-text indexing
+    </term>
+
+    <listitem>
+     <para>
+      A new full-text indexing suite is available in
+      <filename>contrib/tsearch2</filename>.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     New autovacuum tool
+    </term>
+
+    <listitem>
+     <para>
+      The new autovacuum tool in
+      <filename>contrib/autovacuum</filename> monitors the database
+      statistics tables for
+      <command>INSERT</command>/<command>UPDATE</command>/<command>DELETE</command>
+      activity and automatically vacuums tables when needed.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Array handling has been improved and moved into the server core
+    </term>
+
+    <listitem>
+     <para>
+      Many array limitations have been removed, and arrays behave
+      more like fully-supported data types.
+     </para>
+    </listitem>
+   </varlistentry>
+
+  </variablelist>
+ </sect2>
+
+ <sect2>
+  <title>Migration to Version 7.4</title>
+
+  <para>
+   A dump/restore using <application>pg_dump</application> is
+   required for those wishing to migrate data from any previous
+   release.
+  </para>
+
+  <para>
+   Observe the following incompatibilities:
+  </para>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     The server-side autocommit setting was removed and
+     reimplemented in client applications and languages.
+     Server-side autocommit was causing too many problems with
+     languages and applications that wanted to control their own
+     autocommit behavior, so autocommit was removed from the server
+     and added to individual client APIs as appropriate.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Error message wording has changed substantially in this
+     release.  Significant effort was invested to make the messages
+     more consistent and user-oriented.  If your applications try to
+     detect different error conditions by parsing the error message,
+     you are strongly encouraged to use the new error code facility instead.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Inner joins using the explicit <literal>JOIN</literal> syntax
+     might behave differently because they are now better
+     optimized.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     A number of server configuration parameters have been renamed
+     for clarity, primarily those related to
+     logging.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <literal>FETCH 0</literal> or <literal>MOVE 0</literal> now
+     does nothing.  In prior releases, <literal>FETCH 0</literal>
+     would fetch all remaining rows, and <literal>MOVE 0</literal>
+     would move to the end of the cursor.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <command>FETCH</command> and <command>MOVE</command> now return
+     the actual number of rows fetched/moved, or zero if at the
+     beginning/end of the cursor.  Prior releases would return the
+     row count passed to the command, not the number of rows
+     actually fetched or moved.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <command>COPY</command> now can process files that use
+     carriage-return or carriage-return/line-feed end-of-line
+     sequences. Literal carriage-returns and line-feeds are no
+     longer accepted in data values; use <literal>\r</literal> and
+     <literal>\n</literal> instead.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Trailing spaces are now trimmed when converting from type
+     <type>char(<replaceable>n</>)</type> to
+     <type>varchar(<replaceable>n</>)</type> or <type>text</type>.
+     This is what most people always expected to happen anyway.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The data type <type>float(<replaceable>p</>)</type> now
+     measures <replaceable>p</> in binary digits, not decimal
+     digits.  The new behavior follows the SQL standard.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Ambiguous date values now must match the ordering specified by
+     the <varname>datestyle</varname> setting.  In prior releases, a
+     date specification of <literal>10/20/03</> was interpreted as a
+     date in October even if <varname>datestyle</> specified that
+     the day should be first.  7.4 will throw an error if a date
+     specification is invalid for the current setting of
+     <varname>datestyle</>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The functions <function>oidrand</function>,
+     <function>oidsrand</function>, and
+     <function>userfntest</function> have been removed.  These
+     functions were determined to be no longer useful.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     String literals specifying time-varying date/time values, such
+     as <literal>'now'</literal> or <literal>'today'</literal> will
+     no longer work as expected in column default expressions; they
+     now cause the time of the table creation to be the default, not
+     the time of the insertion.  Functions such as
+     <function>now()</>, <function>current_timestamp</>, or
+     <function>current_date</function> should be used instead.
+    </para>
+
+    <para>
+     In previous releases, there was special code so that strings
+     such as <literal>'now'</literal> were interpreted at
+     <command>INSERT</> time and not at table creation time, but
+     this work around didn't cover all cases.  Release 7.4 now
+     requires that defaults be defined properly using functions such
+     as <function>now()</> or <function>current_timestamp</>. These
+     will work in all situations.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The dollar sign (<literal>$</>) is no longer allowed in
+     operator names.  It can instead be a non-first character in
+     identifiers.  This was done to improve compatibility with other
+     database systems, and to avoid syntax problems when parameter
+     placeholders (<literal>$<replaceable>n</></>) are written
+     adjacent to operators.
+    </para>
+   </listitem>
+
+  </itemizedlist>
+ </sect2>
+
+ <sect2>
+  <title>Changes</title>
+
+  <para>
+   Below you will find a detailed account of the changes between
+   release 7.4 and the previous major release.
+  </para>
+
+ <sect3>
+  <title>Server Operation Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     Allow IPv6 server connections (Nigel Kukard, Johan Jordaan,
+     Bruce, Tom, Kurt Roeckx, Andrew Dunstan)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Fix SSL to handle errors cleanly (Nathan Mueller)
+    </para>
+    <para>
+     In prior releases, certain SSL API error reports were not
+     handled correctly.  This release fixes those problems.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     SSL protocol security and performance improvements (Sean Chittenden)
+    </para>
+    <para>
+     SSL key renegotiation was happening too frequently, causing poor
+     SSL performance.  Also, initial key handling was improved.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Print lock information when a deadlock is detected (Tom)
+    </para>
+    <para>
+     This allows easier debugging of deadlock situations.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Update <filename>/tmp</filename> socket modification times
+     regularly to avoid their removal (Tom)
+    </para>
+    <para>
+     This should help prevent <filename>/tmp</filename> directory
+     cleaner administration scripts from removing server socket
+     files.
+    </para>
+   </listitem>
+
+   <listitem><para>Enable PAM for Mac OS X (Aaron Hillegass)</para></listitem>
+
+   <listitem>
+    <para>Make B-tree indexes fully WAL-safe (Tom)</para>
+    <para>
+     In prior releases, under certain rare cases, a server crash
+     could cause B-tree indexes to become corrupt. This release
+     removes those last few rare cases.
+    </para>
+   </listitem>
+
+   <listitem><para>Allow B-tree index compaction and empty page reuse (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Fix inconsistent index lookups during split of first root page (Tom)
+    </para>
+    <para>
+     In prior releases, when a single-page index split into two
+     pages, there was a brief period when another database session
+     could miss seeing an index entry.  This release fixes that rare
+     failure case.
+    </para>
+   </listitem>
+
+   <listitem><para>Improve free space map allocation logic (Tom)</para></listitem>
+
+   <listitem>
+    <para>Preserve free space information between server restarts (Tom)</para>
+    <para>
+     In prior releases, the free space map was not saved when the
+     postmaster was stopped, so newly started servers had no free
+     space information. This release saves the free space map, and
+     reloads it when the server is restarted.
+    </para>
+   </listitem>
+
+   <listitem><para>Add start time to <literal>pg_stat_activity</literal> (Neil)</para></listitem>
+   <listitem><para>New code to detect corrupt disk pages; erase with <varname>zero_damaged_pages</varname> (Tom)</para></listitem>
+   <listitem><para>New client/server protocol: faster, no username length limit, allow clean exit from <command>COPY</command> (Tom)</para></listitem>
+   <listitem><para>Add transaction status, table ID, column ID to client/server protocol (Tom)</para></listitem>
+   <listitem><para>Add binary I/O to client/server protocol (Tom)</para></listitem>
+   <listitem><para>Remove autocommit server setting; move to client applications (Tom)</para></listitem>
+   <listitem><para>New error message wording, error codes, and three levels of error detail (Tom, Joe, Peter)</para></listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Performance Improvements</title>
+
+  <itemizedlist>
+   <listitem><para>Add hashing for <literal>GROUP BY</literal> aggregates (Tom)</para></listitem>
+   <listitem><para>Make nested-loop joins be smarter about multicolumn indexes (Tom)</para></listitem>
+   <listitem><para>Allow multikey hash joins (Tom)</para></listitem>
+   <listitem><para>Improve constant folding (Tom)</para></listitem>
+   <listitem><para>Add ability to inline simple SQL functions (Tom)</para></listitem>
+
+   <listitem>
+    <para>Reduce memory usage for queries using complex functions (Tom)</para>
+    <para>
+     In prior releases, functions returning allocated memory would
+     not free it until the query completed. This release allows the
+     freeing of function-allocated memory when the function call
+     completes, reducing the total memory used by functions.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Improve GEQO optimizer performance (Tom)</para>
+    <para>
+     This release fixes several inefficiencies in the way the GEQO optimizer
+     manages potential query paths.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow <literal>IN</>/<literal>NOT IN</> to be handled via hash
+     tables (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improve <literal>NOT IN (<replaceable>subquery</>)</literal>
+     performance (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow most <literal>IN</literal> subqueries to be processed as
+     joins (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Pattern matching operations can use indexes regardless of
+     locale (Peter)
+    </para>
+    <para>
+     There is no way for non-ASCII locales to use the standard
+     indexes for <literal>LIKE</literal> comparisons. This release
+     adds a way to create a special index for
+     <literal>LIKE</literal>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow the postmaster to preload libraries using <varname>preload_libraries</varname> (Joe)</para>
+    <para>
+     For shared libraries that require a long time to load, this
+     option is available so the library can be preloaded in the
+     postmaster and inherited by all database sessions.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improve optimizer cost computations, particularly for subqueries (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Avoid sort when subquery <literal>ORDER BY</literal> matches upper query (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Deduce that <literal>WHERE a.x = b.y AND b.y = 42</literal> also
+     means <literal>a.x = 42</literal> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow hash/merge joins on complex joins (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow hash joins for more data types (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow join optimization of explicit inner joins, disable with
+     <varname>join_collapse_limit</varname> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add parameter <varname>from_collapse_limit</varname> to control
+     conversion of subqueries to joins (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Use faster and more powerful regular expression code from Tcl
+     (Henry Spencer, Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Use bit-mapped relation sets in the optimizer (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Improve connection startup time (Tom)</para>
+    <para>
+     The new client/server protocol requires fewer network packets to
+     start a database session.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improve trigger/constraint performance (Stephan)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improve speed of <literal>col IN (const, const, const, ...)</literal> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Fix hash indexes which were broken in rare cases (Tom)
+    </para>
+   </listitem>
+
+   <listitem><para>Improve hash index concurrency and speed (Tom)</para>
+    <para>
+     Prior releases suffered from poor hash index performance,
+     particularly for high concurrency situations. This release fixes
+     that, and the development group is interested in reports
+     comparing B-tree and hash index performance.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Align shared buffers on 32-byte boundary for copy speed improvement (Manfred Spraul)</para>
+    <para>
+     Certain CPU's perform faster data copies when addresses are
+     32-byte aligned.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Data type <type>numeric</type> reimplemented for better performance (Tom)</para>
+    <para>
+     <type>numeric</type> used to be stored in base 100. The new code
+     uses base 10000, for significantly better performance.
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Server Configuration Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>Rename server parameter <varname>server_min_messages</> to <varname>log_min_messages</> (Bruce)</para>
+    <para>
+     This was done so most parameters that control the server logs
+     begin with <literal>log_</>.
+    </para>
+   </listitem>
+
+   <listitem><para>Rename <varname>show_*_stats</> to <varname>log_*_stats</> (Bruce)</para></listitem>
+   <listitem><para>Rename <varname>show_source_port</> to <varname>log_source_port</> (Bruce)</para></listitem>
+   <listitem><para>Rename <varname>hostname_lookup</> to <varname>log_hostname</> (Bruce)</para></listitem>
+
+   <listitem>
+    <para>Add <varname>checkpoint_warning</> to warn of excessive checkpointing (Bruce)</para>
+    <para>
+     In prior releases, it was difficult to determine if checkpoint
+     was happening too frequently. This feature adds a warning to the
+     server logs when excessive checkpointing happens.
+    </para>
+   </listitem>
+
+   <listitem><para>New read-only server parameters for localization (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Change debug server log messages to output as <literal>DEBUG</>
+     rather than <literal>LOG</> (Bruce)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Prevent server log variables from being turned off by non-superusers (Bruce)</para>
+    <para>
+     This is a security feature so non-superusers cannot disable
+     logging that was enabled by the administrator.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <varname>log_min_messages</>/<varname>client_min_messages</> now
+     controls <varname>debug_*</> output (Bruce)
+    </para>
+    <para>
+     This centralizes client debug information so all debug output
+     can be sent to either the client or server logs.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add Mac OS X Rendezvous server support (Chris Campbell)</para>
+    <para>
+     This allows Mac OS X hosts to query the network for available
+     <productname>PostgreSQL</productname> servers.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add ability to print only slow statements using
+     <varname>log_min_duration_statement</varname>
+     (Christopher)
+    </para>
+    <para>
+     This is an often requested debugging feature that allows
+     administrators to see only slow queries in their server logs.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <filename>pg_hba.conf</filename> to accept netmasks in CIDR format (Andrew Dunstan)</para>
+    <para>
+     This allows administrators to merge the host IP address and
+     netmask fields into a single CIDR field in <filename>pg_hba.conf</filename>.
+    </para>
+   </listitem>
+
+   <listitem><para>New read-only parameter <varname>is_superuser</varname> (Tom)</para></listitem>
+
+   <listitem>
+    <para>New parameter <varname>log_error_verbosity</varname> to control error detail (Tom)</para>
+    <para>
+     This works with the new error reporting feature to supply
+     additional error information like hints, file names and line
+     numbers.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para><literal>postgres --describe-config</literal> now dumps server config variables (Aizaz Ahmed, Peter)</para>
+    <para>
+     This option is useful for administration tools that need to know
+     the configuration variable names and their minimums, maximums,
+     defaults, and descriptions.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add new columns in <literal>pg_settings</literal>:
+     <literal>context</>, <literal>type</>, <literal>source</>,
+     <literal>min_val</>, <literal>max_val</> (Joe)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make default <varname>shared_buffers</> 1000 and
+     <varname>max_connections</> 100, if possible (Tom)
+    </para>
+    <para>
+     Prior versions defaulted to 64 shared buffers so <productname>PostgreSQL</productname>
+     would start on even very old systems. This release tests the
+     amount of shared memory allowed by the platform and selects more
+     reasonable default values if possible.  Of course, users are
+     still encouraged to evaluate their resource load and size
+     <varname>shared_buffers</varname> accordingly.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     New <filename>pg_hba.conf</filename> record type
+     <literal>hostnossl</> to prevent SSL connections (Jon
+     Jensen)
+    </para>
+    <para>
+     In prior releases, there was no way to prevent SSL connections
+     if both the client and server supported SSL. This option allows
+     that capability.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Remove parameter <varname>geqo_random_seed</varname>
+     (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add server parameter <varname>regex_flavor</varname> to control regular expression processing (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make <command>pg_ctl</command> better handle nonstandard ports (Greg)
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Query Changes</title>
+
+  <itemizedlist>
+   <listitem><para>New SQL-standard information schema (Peter)</para></listitem>
+   <listitem><para>Add read-only transactions (Peter)</para></listitem>
+   <listitem><para>Print key name and value in foreign-key violation messages (Dmitry Tkach)</para></listitem>
+
+   <listitem>
+    <para>Allow users to see their own queries in <literal>pg_stat_activity</literal> (Kevin Brown)</para>
+    <para>
+     In prior releases, only the superuser could see query strings
+     using <literal>pg_stat_activity</literal>. Now ordinary users
+     can see their own query strings.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Fix aggregates in subqueries to match SQL standard (Tom)</para>
+    <para>
+     The SQL standard says that an aggregate function appearing
+     within a nested subquery belongs to the outer query if its
+     argument contains only outer-query variables.  Prior
+     <productname>PostgreSQL</productname> releases did not handle
+     this fine point correctly.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add option to prevent auto-addition of tables referenced in query (Nigel J. Andrews)</para>
+    <para>
+     By default, tables mentioned in the query are automatically
+     added to the <literal>FROM</> clause if they are not already
+     there.  This is compatible with historic
+     <productname>POSTGRES</productname> behavior but is contrary to
+     the SQL standard.  This option allows selecting
+     standard-compatible behavior.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <literal>UPDATE ... SET col = DEFAULT</literal> (Rod)</para>
+    <para>
+     This allows <command>UPDATE</command> to set a column to its
+     declared default value.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow expressions to be used in <literal>LIMIT</>/<literal>OFFSET</> (Tom)</para>
+    <para>
+     In prior releases, <literal>LIMIT</>/<literal>OFFSET</> could
+     only use constants, not expressions.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Implement <literal>CREATE TABLE AS EXECUTE</literal> (Neil, Peter)</para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Object Manipulation Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>Make <command>CREATE SEQUENCE</command> grammar more conforming to SQL:2003 (Neil)</para>
+   </listitem>
+
+   <listitem>
+    <para>Add statement-level triggers (Neil)</para>
+    <para>
+     While this allows a trigger to fire at the end of a statement,
+     it does not allow the trigger to access all rows modified by the
+     statement.  This capability is planned for a future release.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add check constraints for domains (Rod)</para>
+    <para>
+     This greatly increases the usefulness of domains by allowing
+     them to use check constraints.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add <command>ALTER DOMAIN</command> (Rod)</para>
+    <para>
+     This allows manipulation of existing domains.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Fix several zero-column table bugs (Tom)</para>
+    <para>
+     <productname>PostgreSQL</productname> supports zero-column tables. This fixes various bugs
+     that occur when using such tables.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Have <literal>ALTER TABLE ... ADD PRIMARY KEY</literal> add not-null constraint (Rod)</para>
+    <para>
+     In prior releases, <literal>ALTER TABLE ... ADD
+     PRIMARY</literal> would add a unique index, but not a not-null
+     constraint.  That is fixed in this release.
+    </para>
+   </listitem>
+
+   <listitem><para>Add <literal>ALTER TABLE ... WITHOUT OIDS</literal> (Rod)</para>
+    <para>
+     This allows control over whether new and updated rows will have
+     an OID column.  This is most useful for saving storage space.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add <literal>ALTER SEQUENCE</literal> to modify minimum, maximum,
+     increment, cache, cycle values (Rod)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add <literal>ALTER TABLE ... CLUSTER ON</literal> (Alvaro Herrera)</para>
+    <para>
+     This command is used by <command>pg_dump</command> to record the
+     cluster column for each table previously clustered. This
+     information is used by database-wide cluster to cluster all
+     previously clustered tables.
+    </para>
+   </listitem>
+
+   <listitem><para>Improve automatic type casting for domains (Rod, Tom)</para></listitem>
+   <listitem><para>Allow dollar signs in identifiers, except as first character (Tom)</para></listitem>
+   <listitem><para>Disallow dollar signs in operator names, so <literal>x=$1</> works (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Allow copying table schema using <literal>LIKE
+     <replaceable>subtable</replaceable></literal>, also SQL:2003
+     feature <literal>INCLUDING DEFAULTS</literal> (Rod)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add <literal>WITH GRANT OPTION</literal> clause to
+     <command>GRANT</command> (Peter)
+    </para>
+    <para>
+     This enabled <command>GRANT</command> to give other users the
+     ability to grant privileges on a object.
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Utility Command Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>Add <literal>ON COMMIT</literal> clause to <command>CREATE TABLE</command> for temporary tables (Gavin)</para>
+    <para>
+     This adds the ability for a table to be dropped or all rows
+     deleted on transaction commit.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow cursors outside transactions using <literal>WITH HOLD</literal> (Neil)</para>
+    <para>
+     In previous releases, cursors were removed at the end of the
+     transaction that created them. Cursors can now be created with
+     the <literal>WITH HOLD</literal> option, which allows them to
+     continue to be accessed after the creating transaction has
+     committed.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para><literal>FETCH 0</literal> and <literal>MOVE 0 </literal> now do nothing (Bruce)</para>
+    <para>
+     In previous releases, <literal>FETCH 0</literal> fetched all
+     remaining rows, and <literal>MOVE 0</literal> moved to the end
+     of the cursor.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Cause <command>FETCH</command> and <command>MOVE</command> to
+     return the number of rows fetched/moved, or zero if at the
+     beginning/end of cursor, per SQL standard (Bruce)
+    </para>
+    <para>
+     In prior releases, the row count returned by
+     <command>FETCH</command> and <command>MOVE</command> did not
+     accurately reflect the number of rows processed.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Properly handle <literal>SCROLL</literal> with cursors, or
+    report an error (Neil)</para>
+    <para>
+     Allowing random access (both forward and backward scrolling) to
+     some kinds of queries cannot be done without some additional
+     work. If <literal>SCROLL</literal> is specified when the cursor
+     is created, this additional work will be performed. Furthermore,
+     if the cursor has been created with <literal>NO SCROLL</literal>,
+     no random access is allowed.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Implement SQL-compatible options <literal>FIRST</>,
+     <literal>LAST</>, <literal>ABSOLUTE <replaceable>n</></>,
+     <literal>RELATIVE <replaceable>n</></> for
+     <command>FETCH</command> and <command>MOVE</command> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <command>EXPLAIN</command> on <command>DECLARE CURSOR</command> (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <command>CLUSTER</command> to use index marked as pre-clustered by default (Alvaro Herrera)</para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <command>CLUSTER</command> to cluster all tables (Alvaro Herrera)</para>
+    <para>
+     This allows all previously clustered tables in a database to be
+     reclustered with a single command.
+    </para>
+   </listitem>
+
+   <listitem><para>Prevent <command>CLUSTER</command> on partial indexes (Tom)</para></listitem>
+
+   <listitem><para>Allow DOS and Mac line-endings in <command>COPY</> files (Bruce)</para></listitem>
+
+   <listitem>
+    <para>
+     Disallow literal carriage return as a data value,
+     backslash-carriage-return and <literal>\r</> are still allowed
+     (Bruce)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para><command>COPY</> changes (binary, <literal>\.</>) (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Recover from <command>COPY</command> failure cleanly (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Prevent possible memory leaks in <command>COPY</command> (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Make <command>TRUNCATE</command> transaction-safe (Rod)</para>
+    <para>
+     <command>TRUNCATE</command> can now be used inside a
+     transaction. If the transaction aborts, the changes made by the
+     <command>TRUNCATE</command> are automatically rolled back.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow prepare/bind of utility commands like
+     <command>FETCH</command> and <command>EXPLAIN</command> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add <command>EXPLAIN EXECUTE</command> (Neil)</para>
+   </listitem>
+
+   <listitem>
+    <para>Improve <command>VACUUM</command> performance on indexes by reducing WAL traffic (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Functional indexes have been generalized into indexes on expressions (Tom)</para>
+    <para>
+     In prior releases, functional indexes only supported a simple
+     function applied to one or more column names.  This release
+     allows any type of scalar expression.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Have <command>SHOW TRANSACTION ISOLATION</command> match input
+     to <command>SET TRANSACTION ISOLATION</command>
+     (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+      Have <command>COMMENT ON DATABASE</command> on nonlocal
+      database generate a warning, rather than an error (Rod)
+     </para>
+
+    <para>
+     Database comments are stored in database-local tables so
+     comments on a database have to be stored in each database.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improve reliability of <command>LISTEN</>/<command>NOTIFY</> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow <command>REINDEX</command> to reliably reindex nonshared system catalog indexes (Tom)</para>
+    <para>
+     This allows system tables to be reindexed without the
+     requirement of a standalone session, which was necessary in
+     previous releases. The only tables that now require a standalone
+     session for reindexing are the global system tables
+     <literal>pg_database</>, <literal>pg_shadow</>, and
+     <literal>pg_group</>.
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Data Type and Function Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     New server parameter <varname>extra_float_digits</varname> to
+     control precision display of floating-point numbers (Pedro
+     Ferreira, Tom)
+    </para>
+    <para>
+     This controls output precision which was causing regression
+     testing problems.
+    </para>
+   </listitem>
+
+   <listitem><para>Allow <literal>+1300</literal> as a numeric time-zone specifier, for FJST (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Remove rarely used functions <function>oidrand</>,
+     <function>oidsrand</>, and <function>userfntest</> functions
+     (Neil)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add <function>md5()</> function to main server, already in <filename>contrib/pgcrypto</filename> (Joe)</para>
+    <para>
+     An MD5 function was frequently requested. For more complex
+     encryption capabilities, use
+     <filename>contrib/pgcrypto</filename>.
+    </para>
+   </listitem>
+
+   <listitem><para>Increase date range of <type>timestamp</type> (John Cochran)</para></listitem>
+
+   <listitem>
+    <para>
+     Change <literal>EXTRACT(EPOCH FROM timestamp)</literal> so
+     <type>timestamp without time zone</type> is assumed to be in
+     local time, not GMT (Tom)
+    </para>
+   </listitem>
+
+   <listitem><para>Trap division by zero in case the operating system doesn't prevent it (Tom)</para></listitem>
+   <listitem><para>Change the <type>numeric</type> data type internally to base 10000 (Tom)</para></listitem>
+   <listitem><para>New <function>hostmask()</function> function (Greg Wickham)</para></listitem>
+   <listitem><para>Fixes for <function>to_char()</function> and <function>to_timestamp()</function> (Karel)</para></listitem>
+
+   <listitem>
+    <para>
+     Allow functions that can take any argument data type and return
+     any data type, using <type>anyelement</type> and
+     <type>anyarray</type> (Joe)
+    </para>
+    <para>
+     This allows the creation of functions that can work with any
+     data type.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Arrays can now be specified as <literal>ARRAY[1,2,3]</literal>,
+     <literal>ARRAY[['a','b'],['c','d']]</literal>, or
+     <literal>ARRAY[ARRAY[ARRAY[2]]]</literal> (Joe)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow proper comparisons for arrays, including <literal>ORDER
+     BY</literal> and <literal>DISTINCT</literal> support
+     (Joe)
+    </para>
+   </listitem>
+
+   <listitem><para>Allow indexes on array columns (Joe)</para></listitem>
+   <listitem><para>Allow array concatenation with <literal>||</literal> (Joe)</para></listitem>
+
+   <listitem>
+    <para>
+     Allow <literal>WHERE</literal> qualification
+     <literal><replaceable>expr</> <replaceable>op</> ANY/SOME/ALL
+     (<replaceable>array_expr</>)</literal> (Joe)
+    </para>
+    <para>
+     This allows arrays to behave like a list of values, for purposes
+     like <literal>SELECT * FROM tab WHERE col IN
+     (array_val)</literal>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     New array functions <function>array_append</>,
+     <function>array_cat</>, <function>array_lower</>,
+     <function>array_prepend</>, <function>array_to_string</>,
+     <function>array_upper</>, <function>string_to_array</> (Joe)
+    </para>
+   </listitem>
+
+   <listitem><para>Allow user defined aggregates to use polymorphic functions (Joe)</para></listitem>
+   <listitem><para>Allow assignments to empty arrays (Joe)</para></listitem>
+
+   <listitem>
+    <para>
+     Allow 60 in seconds fields of <type>time</type>,
+     <type>timestamp</type>, and <type>interval</type> input values
+     (Tom)
+    </para>
+    <para>
+     Sixty-second values are needed for leap seconds.
+    </para>
+   </listitem>
+
+   <listitem><para>Allow <type>cidr</type> data type to be cast to <type>text</type> (Tom)</para></listitem>
+
+   <listitem><para>Disallow invalid time zone names in SET TIMEZONE</para></listitem>
+
+   <listitem>
+    <para>
+     Trim trailing spaces when <type>char</type> is cast to
+     <type>varchar</> or <type>text</> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make <type>float(<replaceable>p</>)</> measure the precision
+     <replaceable>p</> in binary digits, not decimal digits
+     (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add IPv6 support to the <type>inet</type> and <type>cidr</type> data types (Michael Graff)</para>
+   </listitem>
+
+   <listitem>
+    <para>Add <function>family()</function> function to report whether address is IPv4 or IPv6 (Michael Graff)</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Have <literal>SHOW datestyle</literal> generate output similar
+     to that used by <literal>SET datestyle</literal> (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make <literal>EXTRACT(TIMEZONE)</literal> and <literal>SET/SHOW
+     TIME ZONE</literal> follow the SQL convention for the sign of
+     time zone offsets, i.e., positive is east from UTC (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Fix <literal>date_trunc('quarter', ...)</literal> (Böjthe Zoltán)</para>
+    <para>
+     Prior releases returned an incorrect value for this function call.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Make <function>initcap()</function> more compatible with Oracle (Mike Nolan)</para>
+    <para>
+     <function>initcap()</function> now uppercases a letter appearing
+     after any non-alphanumeric character, rather than only after
+     whitespace.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow only <varname>datestyle</varname> field order for date values not in ISO-8601 format (Greg)</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add new <varname>datestyle</varname> values <literal>MDY</>,
+     <literal>DMY</>, and <literal>YMD</> to set input field order;
+     honor <literal>US</> and <literal>European</> for backward
+     compatibility (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     String literals like <literal>'now'</literal> or
+     <literal>'today'</literal> will no longer work as a column
+     default. Use functions such as <function>now()</function>,
+     <function>current_timestamp</function> instead.  (change
+     required for prepared statements) (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Treat NaN as larger than any other value in <function>min()</>/<function>max()</> (Tom)</para>
+    <para>
+     NaN was already sorted after ordinary numeric values for most
+     purposes, but <function>min()</> and <function>max()</> didn't
+     get this right.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Prevent interval from suppressing <literal>:00</literal>
+    seconds display</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     New functions <function>pg_get_triggerdef(prettyprint)</function>
+     and <function>pg_conversion_is_visible()</function> (Christopher)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow time to be specified as <literal>040506</> or <literal>0405</> (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Input date order must now be <literal>YYYY-MM-DD</literal> (with 4-digit year) or
+     match <varname>datestyle</varname>
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make <function>pg_get_constraintdef</function> support
+     unique, primary-key, and check constraints (Christopher)
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Server-Side Language Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     Prevent PL/pgSQL crash when <literal>RETURN NEXT</literal> is
+     used on a zero-row record variable (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make PL/Python's <function>spi_execute</function> interface
+     handle null values properly (Andrew Bosma)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow PL/pgSQL to declare variables of composite types without <literal>%ROWTYPE</literal> (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Fix PL/Python's <function>_quote()</function> function to handle big integers</para>
+   </listitem>
+
+   <listitem>
+    <para>Make PL/Python an untrusted language, now called <literal>plpythonu</literal> (Kevin Jacobs, Tom)</para>
+    <para>
+     The Python language no longer supports a restricted execution
+     environment, so the trusted version of PL/Python was removed. If
+     this situation changes, a version of PL/Python that can be used
+     by non-superusers will be readded.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow polymorphic PL/pgSQL functions (Joe, Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Allow polymorphic SQL functions (Joe)</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Improved compiled function caching mechanism in PL/pgSQL with
+     full support for polymorphism (Joe)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Add new parameter <literal>$0</> in PL/pgSQL representing the
+     function's actual return type (Joe)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow PL/Tcl and PL/Python to use the same trigger on multiple tables (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Fixed PL/Tcl's <function>spi_prepare</function> to accept fully
+     qualified type names in the parameter type list
+     (Jan)
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>psql Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>Add <literal>\pset pager always</literal> to always use pager (Greg)</para>
+    <para>
+     This forces the pager to be used even if the number of rows is
+     less than the screen height.  This is valuable for rows that
+     wrap across several screen rows.
+    </para>
+   </listitem>
+
+   <listitem><para>Improve tab completion (Rod, Ross Reedstrom, Ian Barwick)</para></listitem>
+   <listitem><para>Reorder <literal>\?</> help into groupings (Harald Armin Massa, Bruce)</para></listitem>
+   <listitem><para>Add backslash commands for listing schemas, casts, and conversions (Christopher)</para></listitem>
+
+   <listitem>
+    <para>
+     <command>\encoding</> now changes based on the server parameter
+     <varname>client_encoding</varname> (Tom)
+    </para>
+    <para>
+     In previous versions, <command>\encoding</command> was not aware
+     of encoding changes made using <literal>SET
+     client_encoding</literal>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Save editor buffer into readline history (Ross)</para>
+    <para>
+     When <command>\e</> is used to edit a query, the result is saved
+     in the readline history for retrieval using the up arrow.
+    </para>
+   </listitem>
+
+   <listitem><para>Improve <command>\d</command> display (Christopher)</para></listitem>
+   <listitem><para>Enhance HTML mode to be more standards-conforming (Greg)</para></listitem>
+
+   <listitem>
+    <para>New <command>\set AUTOCOMMIT off</command> capability (Tom)</para>
+    <para>
+     This takes the place of the removed server parameter <varname>autocommit</varname>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>New <command>\set VERBOSITY</command> to control error detail (Tom)</para>
+    <para>
+     This controls the new error reporting details.
+    </para>
+   </listitem>
+
+   <listitem><para>New prompt escape sequence <literal>%x</literal> to show transaction status (Tom)</para></listitem>
+   <listitem><para>Long options for <application>psql</application> are now available on all platforms</para></listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>pg_dump Changes</title>
+
+  <itemizedlist>
+   <listitem><para>Multiple pg_dump fixes, including tar format and large objects</para></listitem>
+   <listitem><para>Allow pg_dump to dump specific schemas (Neil)</para></listitem>
+
+   <listitem>
+    <para>Make pg_dump preserve column storage characteristics (Christopher)</para>
+    <para>
+     This preserves <literal>ALTER TABLE ... SET STORAGE</literal> information.
+    </para>
+   </listitem>
+
+   <listitem><para>Make pg_dump preserve <command>CLUSTER</command> characteristics (Christopher)</para></listitem>
+
+   <listitem>
+    <para>
+     Have pg_dumpall use <command>GRANT</>/<command>REVOKE</> to dump database-level privileges (Tom)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow pg_dumpall to support the options <option>-a</>,
+     <option>-s</>, <option>-x</> of pg_dump (Tom)
+    </para>
+   </listitem>
+
+   <listitem><para>Prevent pg_dump from lowercasing identifiers specified on the command line (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     pg_dump options <option>--use-set-session-authorization</option>
+     and <option>--no-reconnect</option> now do nothing, all dumps
+     use <command>SET SESSION AUTHORIZATION</command>
+    </para>
+    <para>
+     pg_dump no longer reconnects to switch users, but instead always
+     uses <command>SET SESSION AUTHORIZATION</command>. This will
+     reduce password prompting during restores.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Long options for <application>pg_dump</application> are now available on all platforms</para>
+    <para>
+     <productname>PostgreSQL</productname> now includes its own
+     long-option processing routines.
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>libpq Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     Add function <function>PQfreemem</function> for freeing memory on
+     Windows, suggested for <command>NOTIFY</command> (Bruce)
+    </para>
+    <para>
+     Windows requires that memory allocated in a library be freed by
+     a function in the same library, hence
+     <function>free()</function> doesn't work for freeing memory
+     allocated by libpq. <function>PQfreemem</function> is the proper
+     way to free libpq memory, especially on Windows, and is
+     recommended for other platforms as well.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Document service capability, and add sample file (Bruce)</para>
+    <para>
+     This allows clients to look up connection information in a
+     central file on the client machine.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Make <function>PQsetdbLogin</function> have the same defaults as
+     <function>PQconnectdb</function> (Tom)
+    </para>
+   </listitem>
+
+   <listitem><para>Allow libpq to cleanly fail when result sets are too large (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Improve performance of function <function>PQunescapeBytea</function> (Ben Lamb)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow thread-safe libpq with <filename>configure</filename>
+     option <option>--enable-thread-safety</option> (Lee Kindness,
+     Philip Yarra)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow function <function>pqInternalNotice</function> to accept a
+     format string and arguments instead of just a preformatted
+     message (Tom, Sean Chittenden)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Control SSL negotiation with <literal>sslmode</literal> values
+     <literal>disable</literal>, <literal>allow</literal>,
+     <literal>prefer</literal>, and <literal>require</literal> (Jon
+     Jensen)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Allow new error codes and levels of text (Tom)</para>
+   </listitem>
+
+   <listitem>
+    <para>Allow access to the underlying table and column of a query result (Tom)</para>
+    <para>
+     This is helpful for query-builder applications that want to know
+     the underlying table and column names associated with a specific
+     result set.
+    </para>
+   </listitem>
+
+   <listitem><para>Allow access to the current transaction status (Tom)</para></listitem>
+   <listitem><para>Add ability to pass binary data directly to the server (Tom)</para></listitem>
+
+   <listitem>
+    <para>
+     Add function <function>PQexecPrepared</function> and
+     <function>PQsendQueryPrepared</function> functions which perform
+     bind/execute of previously prepared statements (Tom)
+     </para>
+    </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>JDBC Changes</title>
+
+  <itemizedlist>
+   <listitem><para>Allow <function>setNull</function> on updateable result sets</para></listitem>
+   <listitem><para>Allow <function>executeBatch</function> on a prepared statement (Barry)</para></listitem>
+   <listitem><para>Support SSL connections (Barry)</para></listitem>
+   <listitem><para>Handle schema names in result sets (Paul Sorenson)</para></listitem>
+   <listitem><para>Add refcursor support (Nic Ferrier)</para></listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Miscellaneous Interface Changes</title>
+
+  <itemizedlist>
+   <listitem>
+    <para>Prevent possible memory leak or core dump during libpgtcl shutdown (Tom)</para>
+   </listitem>
+   <listitem>
+    <para>Add Informix compatibility to ECPG (Michael)</para>
+    <para>
+     This allows ECPG to process embedded C programs that were
+     written using certain Informix extensions.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Add type <type>decimal</type> to ECPG that is fixed length, for Informix (Michael)</para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Allow thread-safe embedded SQL programs with
+     <filename>configure</filename> option
+     <option>--enable-thread-safety</option> (Lee Kindness, Bruce)
+    </para>
+    <para>
+     This allows multiple threads to access the database at the same
+     time.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>Moved Python client PyGreSQL to <ulink url="http://www.pygresql.org"></ulink> (Marc)</para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Source Code Changes</title>
+
+  <itemizedlist>
+   <listitem><para>Prevent need for separate platform geometry regression result files (Tom)</para></listitem>
+   <listitem><para>Improved PPC locking primitive (Reinhard Max)</para></listitem>
+   <listitem><para>New function <function>palloc0</function> to allocate and clear memory (Bruce)</para></listitem>
+   <listitem><para>Fix locking code for s390x CPU (64-bit) (Tom)</para></listitem>
+   <listitem><para>Allow OpenBSD to use local ident credentials (William Ahern)</para></listitem>
+   <listitem><para>Make query plan trees read-only to executor (Tom)</para></listitem>
+   <listitem><para>Add Darwin startup scripts (David Wheeler)</para></listitem>
+   <listitem><para>Allow libpq to compile with Borland C++ compiler (Lester Godwin, Karl Waclawek)</para></listitem>
+   <listitem><para>Use our own version of <function>getopt_long()</function> if needed (Peter)</para></listitem>
+   <listitem><para>Convert administration scripts to C (Peter)</para></listitem>
+   <listitem><para> Bison &gt;= 1.85 is now required to build the <productname>PostgreSQL</> grammar, if building from CVS</para></listitem>
+   <listitem><para>Merge documentation into one book (Peter)</para></listitem>
+   <listitem><para>Add Windows compatibility functions (Bruce)</para></listitem>
+   <listitem><para>Allow client interfaces to compile under MinGW (Bruce)</para></listitem>
+   <listitem><para>New <function>ereport()</function> function for error reporting (Tom)</para></listitem>
+   <listitem><para>Support Intel compiler on Linux (Peter)</para></listitem>
+   <listitem><para>Improve Linux startup scripts (Slawomir Sudnik, Darko Prenosil)</para></listitem>
+   <listitem><para>Add support for AMD Opteron and Itanium (Jeffrey W. Baker, Bruce)</para></listitem>
+   <listitem>
+    <para>Remove <option>--enable-recode</option> option from <command>configure</command></para>
+    <para>
+     This was no longer needed now that we have <command>CREATE CONVERSION</command>.
+    </para>
+   </listitem>
+   <listitem>
+    <para>Generate a compile error if spinlock code is not found (Bruce)</para>
+    <para>
+     Platforms without spinlock code will now fail to compile, rather
+     than silently using semaphores. This failure can be disabled
+     with a new <command>configure</command> option.
+    </para>
+   </listitem>
+  </itemizedlist>
+ </sect3>
+
+ <sect3>
+  <title>Contrib Changes</title>
+
+  <itemizedlist>
+   <listitem><para>Change dbmirror license to BSD</para></listitem>
+   <listitem><para>Improve earthdistance (Bruno Wolff III)</para></listitem>
+   <listitem><para>Portability improvements to pgcrypto (Marko Kreen)</para></listitem>
+   <listitem><para>Prevent crash in xml (John Gray, Michael Richards)</para></listitem>
+   <listitem><para>Update oracle</para></listitem>
+   <listitem><para>Update mysql</para></listitem>
+   <listitem><para>Update cube (Bruno Wolff III)</para></listitem>
+   <listitem><para>Update earthdistance to use cube (Bruno Wolff III)</para></listitem>
+   <listitem><para>Update btree_gist (Oleg)</para></listitem>
+   <listitem><para>New tsearch2 full-text search module (Oleg, Teodor)</para></listitem>
+   <listitem><para>Add hash-based crosstab function to tablefuncs (Joe)</para></listitem>
+   <listitem><para>Add serial column to order <function>connectby()</> siblings in tablefuncs (Nabil Sayegh,Joe)</para></listitem>
+   <listitem><para>Add named persistent connections to dblink (Shridhar Daithanka)</para></listitem>
+   <listitem><para>New pg_autovacuum allows automatic <command>VACUUM</command> (Matthew T. O'Connor)</para></listitem>
+   <listitem><para>Make pgbench honor environment variables <envar>PGHOST</>, <envar>PGPORT</>, <envar>PGUSER</> (Tatsuo)</para></listitem>
+   <listitem><para>Improve intarray (Teodor Sigaev)</para></listitem>
+   <listitem><para>Improve pgstattuple (Rod)</para></listitem>
+   <listitem><para>Fix bug in <function>metaphone()</function> in fuzzystrmatch</para></listitem>
+   <listitem><para>Improve adddepend (Rod)</para></listitem>
+   <listitem><para>Update spi/timetravel (Böjthe Zoltán)</para></listitem>
+   <listitem><para>Fix dbase <option>-s</> option and improve non-ASCII handling (Thomas Behr, Márcio Smiderle)</para></listitem>
+   <listitem><para>Remove array module because features now included by default (Joe)</para></listitem>
+  </itemizedlist>
+ </sect3>
+ </sect2>
+</sect1>
+
+ <sect1 id="release-7-3-21">
+  <title>Release 7.3.21</title>
 
   <note>
-   <title>Release date</title>
-   <simpara>2003-11-17</simpara>
+  <title>Release date</title>
+  <simpara>2008-01-07</simpara>
   </note>
 
-  <sect2>
-   <title>Overview</title>
+  <para>
+   This release contains a variety of fixes from 7.3.20,
+   including fixes for significant security issues.
+  </para>
 
-   <para>
-    Major changes in this release:
-   </para>
-
-   <variablelist>
-    <varlistentry>
-     <term>
-      <literal>IN</literal> / <literal>NOT IN</literal> subqueries are
-      now much more efficient
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, <literal>IN</literal>/<literal>NOT
-       IN</literal> subqueries were joined to the upper query by
-       sequentially scanning the subquery looking for a match.  The
-       7.4 code uses the same sophisticated techniques used by
-       ordinary joins and so is much faster.  An
-       <literal>IN</literal> will now usually be as fast as or faster
-       than an equivalent <literal>EXISTS</literal> subquery; this
-       reverses the conventional wisdom that applied to previous
-       releases.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Improved <literal>GROUP BY</literal> processing by using hash buckets
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, rows to be grouped had to be sorted
-       first.  The 7.4 code can do <literal>GROUP BY</literal>
-       without sorting, by accumulating results into a hash table
-       with one entry per group.  It will still use the sort
-       technique, however, if the hash table is estimated to be too
-       large to fit in <varname>sort_mem</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New multikey hash join capability
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, hash joins could only occur on single
-       keys.  This release allows multicolumn hash joins.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Queries using the explicit <literal>JOIN</literal> syntax are
-      now better optimized
-     </term>
-
-     <listitem>
-      <para>
-       Prior releases evaluated queries using the explicit
-       <literal>JOIN</literal> syntax only in the order implied by
-       the syntax. 7.4 allows full optimization of these queries,
-       meaning the optimizer considers all possible join orderings
-       and chooses the most efficient.  Outer joins, however, must
-       still follow the declared ordering.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Faster and more powerful regular expression code
-     </term>
-
-     <listitem>
-      <para>
-       The entire regular expression module has been replaced with a
-       new version by Henry Spencer, originally written for Tcl.  The
-       code greatly improves performance and supports several flavors
-       of regular expressions.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Function-inlining for simple SQL functions
-     </term>
-
-     <listitem>
-      <para>
-       Simple SQL functions can now be inlined by including their SQL
-       in the main query.  This improves performance by eliminating
-       per-call overhead.  That means simple SQL functions now
-       behave like macros.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Full support for IPv6 connections and IPv6 address data types
-     </term>
-
-     <listitem>
-      <para>
-       Previous releases allowed only IPv4 connections, and the IP
-       data types only supported IPv4 addresses. This release adds
-       full IPv6 support in both of these areas.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Major improvements in SSL performance and reliability
-     </term>
-
-     <listitem>
-      <para>
-       Several people very familiar with the SSL API have overhauled
-       our SSL code to improve SSL key negotiation and error
-       recovery.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Make free space map efficiently reuse empty index pages,
-      and other free space management improvements
-     </term>
-
-     <listitem>
-      <para>
-       In previous releases, B-tree index pages that were left empty
-       because of deleted rows could only be reused by rows with
-       index values similar to the rows originally indexed on that
-       page. In 7.4, <command>VACUUM</command> records empty index
-       pages and allows them to be reused for any future index rows.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      SQL-standard information schema
-     </term>
-
-     <listitem>
-      <para>
-       The information schema provides a standardized and stable way
-       to access information about the schema objects defined in a
-       database.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Cursors conform more closely to the SQL standard
-     </term>
-
-     <listitem>
-      <para>
-       The commands <command>FETCH</command> and
-       <command>MOVE</command> have been overhauled to conform more
-       closely to the SQL standard.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Cursors can exist outside transactions
-     </term>
-
-     <listitem>
-      <para>
-       These cursors are also called holdable cursors.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New client-to-server protocol
-     </term>
-
-     <listitem>
-      <para>
-       The new protocol adds error codes, more status information,
-       faster startup, better support for binary data transmission,
-       parameter values separated from SQL commands, prepared
-       statements available at the protocol level, and cleaner
-       recovery from <command>COPY</command> failures.  The older
-       protocol is still supported by both server and clients.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      <application>libpq</application> and
-      <application>ECPG</application> applications are now fully
-      thread-safe
-     </term>
-
-     <listitem>
-      <para>
-       While previous <application>libpq</application> releases
-       already supported threads, this release improves thread safety
-       by fixing some non-thread-safe code that was used during
-       database connection startup.  The <command>configure</command>
-       option <option>--enable-thread-safety</option> must be used to
-       enable this feature.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New version of full-text indexing
-     </term>
-
-     <listitem>
-      <para>
-       A new full-text indexing suite is available in
-       <filename>contrib/tsearch2</filename>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      New autovacuum tool
-     </term>
-
-     <listitem>
-      <para>
-       The new autovacuum tool in
-       <filename>contrib/autovacuum</filename> monitors the database
-       statistics tables for
-       <command>INSERT</command>/<command>UPDATE</command>/<command>DELETE</command>
-       activity and automatically vacuums tables when needed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>
-      Array handling has been improved and moved into the server core
-     </term>
-
-     <listitem>
-      <para>
-       Many array limitations have been removed, and arrays behave
-       more like fully-supported data types.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
+  <para>
+   This is expected to be the last <productname>PostgreSQL</> release
+   in the 7.3.X series.  Users are encouraged to update to a newer
+   release branch soon.
+  </para>
 
   <sect2>
-   <title>Migration to version 7.4</title>
+   <title>Migration to Version 7.3.21</title>
 
    <para>
-    A dump/restore using <application>pg_dump</application> is
-    required for those wishing to migrate data from any previous
-    release.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The server-side autocommit setting was removed and
-      reimplemented in client applications and languages.
-      Server-side autocommit was causing too many problems with
-      languages and applications that wanted to control their own
-      autocommit behavior, so autocommit was removed from the server
-      and added to individual client APIs as appropriate.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Error message wording has changed substantially in this
-      release.  Significant effort was invested to make the messages
-      more consistent and user-oriented.  If your applications try to
-      detect different error conditions by parsing the error message,
-      you are strongly encouraged to use the new error code facility instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Inner joins using the explicit <literal>JOIN</literal> syntax
-      might behave differently because they are now better
-      optimized.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A number of server configuration parameters have been renamed
-      for clarity, primarily those related to
-      logging.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <literal>FETCH 0</literal> or <literal>MOVE 0</literal> now
-      does nothing.  In prior releases, <literal>FETCH 0</literal>
-      would fetch all remaining rows, and <literal>MOVE 0</literal>
-      would move to the end of the cursor.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <command>FETCH</command> and <command>MOVE</command> now return
-      the actual number of rows fetched/moved, or zero if at the
-      beginning/end of the cursor.  Prior releases would return the
-      row count passed to the command, not the number of rows
-      actually fetched or moved.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <command>COPY</command> now can process files that use
-      carriage-return or carriage-return/line-feed end-of-line
-      sequences. Literal carriage-returns and line-feeds are no
-      longer accepted in data values; use <literal>\r</literal> and
-      <literal>\n</literal> instead.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Trailing spaces are now trimmed when converting from type
-      <type>char(<replaceable>n</>)</type> to
-      <type>varchar(<replaceable>n</>)</type> or <type>text</type>.
-      This is what most people always expected to happen anyway.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The data type <type>float(<replaceable>p</>)</type> now
-      measures <replaceable>p</> in binary digits, not decimal
-      digits.  The new behavior follows the SQL standard.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Ambiguous date values now must match the ordering specified by
-      the <varname>datestyle</varname> setting.  In prior releases, a
-      date specification of <literal>10/20/03</> was interpreted as a
-      date in October even if <varname>datestyle</> specified that
-      the day should be first.  7.4 will throw an error if a date
-      specification is invalid for the current setting of
-      <varname>datestyle</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The functions <function>oidrand</function>,
-      <function>oidsrand</function>, and
-      <function>userfntest</function> have been removed.  These
-      functions were determined to be no longer useful.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      String literals specifying time-varying date/time values, such
-      as <literal>'now'</literal> or <literal>'today'</literal> will
-      no longer work as expected in column default expressions; they
-      now cause the time of the table creation to be the default, not
-      the time of the insertion.  Functions such as
-      <function>now()</>, <function>current_timestamp</>, or
-      <function>current_date</function> should be used instead.
-     </para>
-
-     <para>
-      In previous releases, there was special code so that strings
-      such as <literal>'now'</literal> were interpreted at
-      <command>INSERT</> time and not at table creation time, but
-      this work around didn't cover all cases.  Release 7.4 now
-      requires that defaults be defined properly using functions such
-      as <function>now()</> or <function>current_timestamp</>. These
-      will work in all situations.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The dollar sign (<literal>$</>) is no longer allowed in
-      operator names.  It can instead be a non-first character in
-      identifiers.  This was done to improve compatibility with other
-      database systems, and to avoid syntax problems when parameter
-      placeholders (<literal>$<replaceable>n</></>) are written
-      adjacent to operators.
-     </para>
-    </listitem>
-
-   </itemizedlist>
   </sect2>
 
   <sect2>
    <title>Changes</title>
 
-   <para>
-    Below you will find a detailed account of the changes between
-    release 7.4 and the previous major release.
-   </para>
-
-  <sect3>
-   <title>Server Operation Changes</title>
-
    <itemizedlist>
+
     <listitem>
      <para>
-      Allow IPv6 server connections (Nigel Kukard, Johan Jordaan,
-      Bruce, Tom, Kurt Roeckx, Andrew Dunstan)
+      Prevent functions in indexes from executing with the privileges of
+      the user running <command>VACUUM</>, <command>ANALYZE</>, etc (Tom)
+     </para>
+
+     <para>
+      Functions used in index expressions and partial-index
+      predicates are evaluated whenever a new table entry is made.  It has
+      long been understood that this poses a risk of trojan-horse code
+      execution if one modifies a table owned by an untrustworthy user.
+      (Note that triggers, defaults, check constraints, etc. pose the
+      same type of risk.)  But functions in indexes pose extra danger
+      because they will be executed by routine maintenance operations
+      such as <command>VACUUM FULL</>, which are commonly performed
+      automatically under a superuser account.  For example, a nefarious user
+      can execute code with superuser privileges by setting up a
+      trojan-horse index definition and waiting for the next routine vacuum.
+      The fix arranges for standard maintenance operations
+      (including <command>VACUUM</>, <command>ANALYZE</>, <command>REINDEX</>,
+      and <command>CLUSTER</>) to execute as the table owner rather than
+      the calling user, using the same privilege-switching mechanism already
+      used for <literal>SECURITY DEFINER</> functions.  To prevent bypassing
+      this security measure, execution of <command>SET SESSION
+      AUTHORIZATION</> and <command>SET ROLE</> is now forbidden within a
+      <literal>SECURITY DEFINER</> context.  (CVE-2007-6600)
      </para>
     </listitem>
 
     <listitem>
      <para>
-      Fix SSL to handle errors cleanly (Nathan Mueller)
+      Require non-superusers who use <filename>/contrib/dblink</> to use only
+      password authentication, as a security measure (Joe)
      </para>
+
      <para>
-      In prior releases, certain SSL API error reports were not
-      handled correctly.  This release fixes those problems.
+      The fix that appeared for this in 7.3.20 was incomplete, as it plugged
+      the hole for only some <filename>dblink</> functions.  (CVE-2007-6601,
+      CVE-2007-3278)
      </para>
     </listitem>
 
     <listitem>
      <para>
-      SSL protocol security and performance improvements (Sean Chittenden)
-     </para>
-     <para>
-      SSL key renegotiation was happening too frequently, causing poor
-      SSL performance.  Also, initial key handling was improved.
+      Fix potential crash in <function>translate()</> when using a multibyte
+      database encoding (Tom)
      </para>
     </listitem>
 
     <listitem>
      <para>
-      Print lock information when a deadlock is detected (Tom)
-     </para>
-     <para>
-      This allows easier debugging of deadlock situations.
+      Make <filename>contrib/tablefunc</>'s <function>crosstab()</> handle
+      NULL rowid as a category in its own right, rather than crashing (Joe)
      </para>
     </listitem>
 
     <listitem>
      <para>
-      Update <filename>/tmp</filename> socket modification times
-      regularly to avoid their removal (Tom)
+      Require a specific version of <productname>Autoconf</> to be used
+      when re-generating the <command>configure</> script (Peter)
      </para>
+
      <para>
-      This should help prevent <filename>/tmp</filename> directory
-      cleaner administration scripts from removing server socket
-      files.
+      This affects developers and packagers only.  The change was made
+      to prevent accidental use of untested combinations of
+      <productname>Autoconf</> and <productname>PostgreSQL</> versions.
+      You can remove the version check if you really want to use a
+      different <productname>Autoconf</> version, but it's
+      your responsibility whether the result works or not.
      </para>
     </listitem>
 
-    <listitem><para>Enable PAM for Mac OS X (Aaron Hillegass)</para></listitem>
-
-    <listitem>
-     <para>Make B-tree indexes fully WAL-safe (Tom)</para>
-     <para>
-      In prior releases, under certain rare cases, a server crash
-      could cause B-tree indexes to become corrupt. This release
-      removes those last few rare cases.
-     </para>
-    </listitem>
-
-    <listitem><para>Allow B-tree index compaction and empty page reuse (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Fix inconsistent index lookups during split of first root page (Tom)
-     </para>
-     <para>
-      In prior releases, when a single-page index split into two
-      pages, there was a brief period when another database session
-      could miss seeing an index entry.  This release fixes that rare
-      failure case.
-     </para>
-    </listitem>
-
-    <listitem><para>Improve free space map allocation logic (Tom)</para></listitem>
-
-    <listitem>
-     <para>Preserve free space information between server restarts (Tom)</para>
-     <para>
-      In prior releases, the free space map was not saved when the
-      postmaster was stopped, so newly started servers had no free
-      space information. This release saves the free space map, and
-      reloads it when the server is restarted.
-     </para>
-    </listitem>
-
-    <listitem><para>Add start time to <literal>pg_stat_activity</literal> (Neil)</para></listitem>
-    <listitem><para>New code to detect corrupt disk pages; erase with <varname>zero_damaged_pages</varname> (Tom)</para></listitem>
-    <listitem><para>New client/server protocol: faster, no username length limit, allow clean exit from <command>COPY</command> (Tom)</para></listitem>
-    <listitem><para>Add transaction status, table ID, column ID to client/server protocol (Tom)</para></listitem>
-    <listitem><para>Add binary I/O to client/server protocol (Tom)</para></listitem>
-    <listitem><para>Remove autocommit server setting; move to client applications (Tom)</para></listitem>
-    <listitem><para>New error message wording, error codes, and three levels of error detail (Tom, Joe, Peter)</para></listitem>
    </itemizedlist>
-  </sect3>
 
-  <sect3>
-   <title>Performance Improvements</title>
-
-   <itemizedlist>
-    <listitem><para>Add hashing for <literal>GROUP BY</literal> aggregates (Tom)</para></listitem>
-    <listitem><para>Make nested-loop joins be smarter about multicolumn indexes (Tom)</para></listitem>
-    <listitem><para>Allow multikey hash joins (Tom)</para></listitem>
-    <listitem><para>Improve constant folding (Tom)</para></listitem>
-    <listitem><para>Add ability to inline simple SQL functions (Tom)</para></listitem>
-
-    <listitem>
-     <para>Reduce memory usage for queries using complex functions (Tom)</para>
-     <para>
-      In prior releases, functions returning allocated memory would
-      not free it until the query completed. This release allows the
-      freeing of function-allocated memory when the function call
-      completes, reducing the total memory used by functions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Improve GEQO optimizer performance (Tom)</para>
-     <para>
-      This release fixes several inefficiencies in the way the GEQO optimizer
-      manages potential query paths.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow <literal>IN</>/<literal>NOT IN</> to be handled via hash
-      tables (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve <literal>NOT IN (<replaceable>subquery</>)</literal>
-      performance (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow most <literal>IN</literal> subqueries to be processed as
-      joins (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Pattern matching operations can use indexes regardless of
-      locale (Peter)
-     </para>
-     <para>
-      There is no way for non-ASCII locales to use the standard
-      indexes for <literal>LIKE</literal> comparisons. This release
-      adds a way to create a special index for
-      <literal>LIKE</literal>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow the postmaster to preload libraries using <varname>preload_libraries</varname> (Joe)</para>
-     <para>
-      For shared libraries that require a long time to load, this
-      option is available so the library can be preloaded in the
-      postmaster and inherited by all database sessions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve optimizer cost computations, particularly for subqueries (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Avoid sort when subquery <literal>ORDER BY</literal> matches upper query (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Deduce that <literal>WHERE a.x = b.y AND b.y = 42</literal> also
-      means <literal>a.x = 42</literal> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow hash/merge joins on complex joins (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow hash joins for more data types (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow join optimization of explicit inner joins, disable with
-      <varname>join_collapse_limit</varname> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add parameter <varname>from_collapse_limit</varname> to control
-      conversion of subqueries to joins (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use faster and more powerful regular expression code from Tcl
-      (Henry Spencer, Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use bit-mapped relation sets in the optimizer (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Improve connection startup time (Tom)</para>
-     <para>
-      The new client/server protocol requires fewer network packets to
-      start a database session.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve trigger/constraint performance (Stephan)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve speed of <literal>col IN (const, const, const, ...)</literal> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fix hash indexes which were broken in rare cases (Tom)
-     </para>
-    </listitem>
-
-    <listitem><para>Improve hash index concurrency and speed (Tom)</para>
-     <para>
-      Prior releases suffered from poor hash index performance,
-      particularly for high concurrency situations. This release fixes
-      that, and the development group is interested in reports
-      comparing B-tree and hash index performance.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Align shared buffers on 32-byte boundary for copy speed improvement (Manfred Spraul)</para>
-     <para>
-      Certain CPU's perform faster data copies when addresses are
-      32-byte aligned.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Data type <type>numeric</type> reimplemented for better performance (Tom)</para>
-     <para>
-      <type>numeric</type> used to be stored in base 100. The new code
-      uses base 10000, for significantly better performance.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Server Configuration Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>Rename server parameter <varname>server_min_messages</> to <varname>log_min_messages</> (Bruce)</para>
-     <para>
-      This was done so most parameters that control the server logs
-      begin with <literal>log_</>.
-     </para>
-    </listitem>
-
-    <listitem><para>Rename <varname>show_*_stats</> to <varname>log_*_stats</> (Bruce)</para></listitem>
-    <listitem><para>Rename <varname>show_source_port</> to <varname>log_source_port</> (Bruce)</para></listitem>
-    <listitem><para>Rename <varname>hostname_lookup</> to <varname>log_hostname</> (Bruce)</para></listitem>
-
-    <listitem>
-     <para>Add <varname>checkpoint_warning</> to warn of excessive checkpointing (Bruce)</para>
-     <para>
-      In prior releases, it was difficult to determine if checkpoint
-      was happening too frequently. This feature adds a warning to the
-      server logs when excessive checkpointing happens.
-     </para>
-    </listitem>
-
-    <listitem><para>New read-only server parameters for localization (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Change debug server log messages to output as <literal>DEBUG</>
-      rather than <literal>LOG</> (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Prevent server log variables from being turned off by non-superusers (Bruce)</para>
-     <para>
-      This is a security feature so non-superusers cannot disable
-      logging that was enabled by the administrator.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <varname>log_min_messages</>/<varname>client_min_messages</> now
-      controls <varname>debug_*</> output (Bruce)
-     </para>
-     <para>
-      This centralizes client debug information so all debug output
-      can be sent to either the client or server logs.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add Mac OS X Rendezvous server support (Chris Campbell)</para>
-     <para>
-      This allows Mac OS X hosts to query the network for available
-      <productname>PostgreSQL</productname> servers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add ability to print only slow statements using
-      <varname>log_min_duration_statement</varname>
-      (Christopher)
-     </para>
-     <para>
-      This is an often requested debugging feature that allows
-      administrators to see only slow queries in their server logs.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <filename>pg_hba.conf</filename> to accept netmasks in CIDR format (Andrew Dunstan)</para>
-     <para>
-      This allows administrators to merge the host IP address and
-      netmask fields into a single CIDR field in <filename>pg_hba.conf</filename>.
-     </para>
-    </listitem>
-
-    <listitem><para>New read-only parameter <varname>is_superuser</varname> (Tom)</para></listitem>
-
-    <listitem>
-     <para>New parameter <varname>log_error_verbosity</varname> to control error detail (Tom)</para>
-     <para>
-      This works with the new error reporting feature to supply
-      additional error information like hints, file names and line
-      numbers.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para><literal>postgres --describe-config</literal> now dumps server config variables (Aizaz Ahmed, Peter)</para>
-     <para>
-      This option is useful for administration tools that need to know
-      the configuration variable names and their minimums, maximums,
-      defaults, and descriptions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add new columns in <literal>pg_settings</literal>:
-      <literal>context</>, <literal>type</>, <literal>source</>,
-      <literal>min_val</>, <literal>max_val</> (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make default <varname>shared_buffers</> 1000 and
-      <varname>max_connections</> 100, if possible (Tom)
-     </para>
-     <para>
-      Prior versions defaulted to 64 shared buffers so <productname>PostgreSQL</productname>
-      would start on even very old systems. This release tests the
-      amount of shared memory allowed by the platform and selects more
-      reasonable default values if possible.  Of course, users are
-      still encouraged to evaluate their resource load and size
-      <varname>shared_buffers</varname> accordingly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New <filename>pg_hba.conf</filename> record type
-      <literal>hostnossl</> to prevent SSL connections (Jon
-      Jensen)
-     </para>
-     <para>
-      In prior releases, there was no way to prevent SSL connections
-      if both the client and server supported SSL. This option allows
-      that capability.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Remove parameter <varname>geqo_random_seed</varname>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add server parameter <varname>regex_flavor</varname> to control regular expression processing (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <command>pg_ctl</command> better handle nonstandard ports (Greg)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Query Changes</title>
-
-   <itemizedlist>
-    <listitem><para>New SQL-standard information schema (Peter)</para></listitem>
-    <listitem><para>Add read-only transactions (Peter)</para></listitem>
-    <listitem><para>Print key name and value in foreign-key violation messages (Dmitry Tkach)</para></listitem>
-
-    <listitem>
-     <para>Allow users to see their own queries in <literal>pg_stat_activity</literal> (Kevin Brown)</para>
-     <para>
-      In prior releases, only the superuser could see query strings
-      using <literal>pg_stat_activity</literal>. Now ordinary users
-      can see their own query strings.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Fix aggregates in subqueries to match SQL standard (Tom)</para>
-     <para>
-      The SQL standard says that an aggregate function appearing
-      within a nested subquery belongs to the outer query if its
-      argument contains only outer-query variables.  Prior
-      <productname>PostgreSQL</productname> releases did not handle
-      this fine point correctly.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add option to prevent auto-addition of tables referenced in query (Nigel J. Andrews)</para>
-     <para>
-      By default, tables mentioned in the query are automatically
-      added to the <literal>FROM</> clause if they are not already
-      there.  This is compatible with historic
-      <productname>POSTGRES</productname> behavior but is contrary to
-      the SQL standard.  This option allows selecting
-      standard-compatible behavior.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <literal>UPDATE ... SET col = DEFAULT</literal> (Rod)</para>
-     <para>
-      This allows <command>UPDATE</command> to set a column to its
-      declared default value.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow expressions to be used in <literal>LIMIT</>/<literal>OFFSET</> (Tom)</para>
-     <para>
-      In prior releases, <literal>LIMIT</>/<literal>OFFSET</> could
-      only use constants, not expressions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Implement <literal>CREATE TABLE AS EXECUTE</literal> (Neil, Peter)</para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Object Manipulation Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>Make <command>CREATE SEQUENCE</command> grammar more conforming to SQL:2003 (Neil)</para>
-    </listitem>
-
-    <listitem>
-     <para>Add statement-level triggers (Neil)</para>
-     <para>
-      While this allows a trigger to fire at the end of a statement,
-      it does not allow the trigger to access all rows modified by the
-      statement.  This capability is planned for a future release.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add check constraints for domains (Rod)</para>
-     <para>
-      This greatly increases the usefulness of domains by allowing
-      them to use check constraints.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add <command>ALTER DOMAIN</command> (Rod)</para>
-     <para>
-      This allows manipulation of existing domains.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Fix several zero-column table bugs (Tom)</para>
-     <para>
-      <productname>PostgreSQL</productname> supports zero-column tables. This fixes various bugs
-      that occur when using such tables.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Have <literal>ALTER TABLE ... ADD PRIMARY KEY</literal> add not-null constraint (Rod)</para>
-     <para>
-      In prior releases, <literal>ALTER TABLE ... ADD
-      PRIMARY</literal> would add a unique index, but not a not-null
-      constraint.  That is fixed in this release.
-     </para>
-    </listitem>
-
-    <listitem><para>Add <literal>ALTER TABLE ... WITHOUT OIDS</literal> (Rod)</para>
-     <para>
-      This allows control over whether new and updated rows will have
-      an OID column.  This is most useful for saving storage space.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>ALTER SEQUENCE</literal> to modify minimum, maximum,
-      increment, cache, cycle values (Rod)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add <literal>ALTER TABLE ... CLUSTER ON</literal> (Alvaro Herrera)</para>
-     <para>
-      This command is used by <command>pg_dump</command> to record the
-      cluster column for each table previously clustered. This
-      information is used by database-wide cluster to cluster all
-      previously clustered tables.
-     </para>
-    </listitem>
-
-    <listitem><para>Improve automatic type casting for domains (Rod, Tom)</para></listitem>
-    <listitem><para>Allow dollar signs in identifiers, except as first character (Tom)</para></listitem>
-    <listitem><para>Disallow dollar signs in operator names, so <literal>x=$1</> works (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Allow copying table schema using <literal>LIKE
-      <replaceable>subtable</replaceable></literal>, also SQL:2003
-      feature <literal>INCLUDING DEFAULTS</literal> (Rod)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add <literal>WITH GRANT OPTION</literal> clause to
-      <command>GRANT</command> (Peter)
-     </para>
-     <para>
-      This enabled <command>GRANT</command> to give other users the
-      ability to grant privileges on a object.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Utility Command Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>Add <literal>ON COMMIT</literal> clause to <command>CREATE TABLE</command> for temporary tables (Gavin)</para>
-     <para>
-      This adds the ability for a table to be dropped or all rows
-      deleted on transaction commit.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow cursors outside transactions using <literal>WITH HOLD</literal> (Neil)</para>
-     <para>
-      In previous releases, cursors were removed at the end of the
-      transaction that created them. Cursors can now be created with
-      the <literal>WITH HOLD</literal> option, which allows them to
-      continue to be accessed after the creating transaction has
-      committed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para><literal>FETCH 0</literal> and <literal>MOVE 0 </literal> now do nothing (Bruce)</para>
-     <para>
-      In previous releases, <literal>FETCH 0</literal> fetched all
-      remaining rows, and <literal>MOVE 0</literal> moved to the end
-      of the cursor.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Cause <command>FETCH</command> and <command>MOVE</command> to
-      return the number of rows fetched/moved, or zero if at the
-      beginning/end of cursor, per SQL standard (Bruce)
-     </para>
-     <para>
-      In prior releases, the row count returned by
-      <command>FETCH</command> and <command>MOVE</command> did not
-      accurately reflect the number of rows processed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Properly handle <literal>SCROLL</literal> with cursors, or
-     report an error (Neil)</para>
-     <para>
-      Allowing random access (both forward and backward scrolling) to
-      some kinds of queries cannot be done without some additional
-      work. If <literal>SCROLL</literal> is specified when the cursor
-      is created, this additional work will be performed. Furthermore,
-      if the cursor has been created with <literal>NO SCROLL</literal>,
-      no random access is allowed.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Implement SQL-compatible options <literal>FIRST</>,
-      <literal>LAST</>, <literal>ABSOLUTE <replaceable>n</></>,
-      <literal>RELATIVE <replaceable>n</></> for
-      <command>FETCH</command> and <command>MOVE</command> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <command>EXPLAIN</command> on <command>DECLARE CURSOR</command> (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <command>CLUSTER</command> to use index marked as pre-clustered by default (Alvaro Herrera)</para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <command>CLUSTER</command> to cluster all tables (Alvaro Herrera)</para>
-     <para>
-      This allows all previously clustered tables in a database to be
-      reclustered with a single command.
-     </para>
-    </listitem>
-
-    <listitem><para>Prevent <command>CLUSTER</command> on partial indexes (Tom)</para></listitem>
-
-    <listitem><para>Allow DOS and Mac line-endings in <command>COPY</> files (Bruce)</para></listitem>
-
-    <listitem>
-     <para>
-      Disallow literal carriage return as a data value,
-      backslash-carriage-return and <literal>\r</> are still allowed
-      (Bruce)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para><command>COPY</> changes (binary, <literal>\.</>) (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Recover from <command>COPY</command> failure cleanly (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Prevent possible memory leaks in <command>COPY</command> (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Make <command>TRUNCATE</command> transaction-safe (Rod)</para>
-     <para>
-      <command>TRUNCATE</command> can now be used inside a
-      transaction. If the transaction aborts, the changes made by the
-      <command>TRUNCATE</command> are automatically rolled back.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow prepare/bind of utility commands like
-      <command>FETCH</command> and <command>EXPLAIN</command> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add <command>EXPLAIN EXECUTE</command> (Neil)</para>
-    </listitem>
-
-    <listitem>
-     <para>Improve <command>VACUUM</command> performance on indexes by reducing WAL traffic (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Functional indexes have been generalized into indexes on expressions (Tom)</para>
-     <para>
-      In prior releases, functional indexes only supported a simple
-      function applied to one or more column names.  This release
-      allows any type of scalar expression.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Have <command>SHOW TRANSACTION ISOLATION</command> match input
-      to <command>SET TRANSACTION ISOLATION</command>
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-       Have <command>COMMENT ON DATABASE</command> on nonlocal
-       database generate a warning, rather than an error (Rod)
-      </para>
-
-     <para>
-      Database comments are stored in database-local tables so
-      comments on a database have to be stored in each database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improve reliability of <command>LISTEN</>/<command>NOTIFY</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow <command>REINDEX</command> to reliably reindex nonshared system catalog indexes (Tom)</para>
-     <para>
-      This allows system tables to be reindexed without the
-      requirement of a standalone session, which was necessary in
-      previous releases. The only tables that now require a standalone
-      session for reindexing are the global system tables
-      <literal>pg_database</>, <literal>pg_shadow</>, and
-      <literal>pg_group</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Data Type and Function Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      New server parameter <varname>extra_float_digits</varname> to
-      control precision display of floating-point numbers (Pedro
-      Ferreira, Tom)
-     </para>
-     <para>
-      This controls output precision which was causing regression
-      testing problems.
-     </para>
-    </listitem>
-
-    <listitem><para>Allow <literal>+1300</literal> as a numeric time-zone specifier, for FJST (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Remove rarely used functions <function>oidrand</>,
-      <function>oidsrand</>, and <function>userfntest</> functions
-      (Neil)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add <function>md5()</> function to main server, already in <filename>contrib/pgcrypto</filename> (Joe)</para>
-     <para>
-      An MD5 function was frequently requested. For more complex
-      encryption capabilities, use
-      <filename>contrib/pgcrypto</filename>.
-     </para>
-    </listitem>
-
-    <listitem><para>Increase date range of <type>timestamp</type> (John Cochran)</para></listitem>
-
-    <listitem>
-     <para>
-      Change <literal>EXTRACT(EPOCH FROM timestamp)</literal> so
-      <type>timestamp without time zone</type> is assumed to be in
-      local time, not GMT (Tom)
-     </para>
-    </listitem>
-
-    <listitem><para>Trap division by zero in case the operating system doesn't prevent it (Tom)</para></listitem>
-    <listitem><para>Change the <type>numeric</type> data type internally to base 10000 (Tom)</para></listitem>
-    <listitem><para>New <function>hostmask()</function> function (Greg Wickham)</para></listitem>
-    <listitem><para>Fixes for <function>to_char()</function> and <function>to_timestamp()</function> (Karel)</para></listitem>
-
-    <listitem>
-     <para>
-      Allow functions that can take any argument data type and return
-      any data type, using <type>anyelement</type> and
-      <type>anyarray</type> (Joe)
-     </para>
-     <para>
-      This allows the creation of functions that can work with any
-      data type.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Arrays can now be specified as <literal>ARRAY[1,2,3]</literal>,
-      <literal>ARRAY[['a','b'],['c','d']]</literal>, or
-      <literal>ARRAY[ARRAY[ARRAY[2]]]</literal> (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow proper comparisons for arrays, including <literal>ORDER
-      BY</literal> and <literal>DISTINCT</literal> support
-      (Joe)
-     </para>
-    </listitem>
-
-    <listitem><para>Allow indexes on array columns (Joe)</para></listitem>
-    <listitem><para>Allow array concatenation with <literal>||</literal> (Joe)</para></listitem>
-
-    <listitem>
-     <para>
-      Allow <literal>WHERE</literal> qualification
-      <literal><replaceable>expr</> <replaceable>op</> ANY/SOME/ALL
-      (<replaceable>array_expr</>)</literal> (Joe)
-     </para>
-     <para>
-      This allows arrays to behave like a list of values, for purposes
-      like <literal>SELECT * FROM tab WHERE col IN
-      (array_val)</literal>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New array functions <function>array_append</>,
-      <function>array_cat</>, <function>array_lower</>,
-      <function>array_prepend</>, <function>array_to_string</>,
-      <function>array_upper</>, <function>string_to_array</> (Joe)
-     </para>
-    </listitem>
-
-    <listitem><para>Allow user defined aggregates to use polymorphic functions (Joe)</para></listitem>
-    <listitem><para>Allow assignments to empty arrays (Joe)</para></listitem>
-
-    <listitem>
-     <para>
-      Allow 60 in seconds fields of <type>time</type>,
-      <type>timestamp</type>, and <type>interval</type> input values
-      (Tom)
-     </para>
-     <para>
-      Sixty-second values are needed for leap seconds.
-     </para>
-    </listitem>
-
-    <listitem><para>Allow <type>cidr</type> data type to be cast to <type>text</type> (Tom)</para></listitem>
-
-    <listitem><para>Disallow invalid time zone names in SET TIMEZONE</para></listitem>
-
-    <listitem>
-     <para>
-      Trim trailing spaces when <type>char</type> is cast to
-      <type>varchar</> or <type>text</> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <type>float(<replaceable>p</>)</> measure the precision
-      <replaceable>p</> in binary digits, not decimal digits
-      (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add IPv6 support to the <type>inet</type> and <type>cidr</type> data types (Michael Graff)</para>
-    </listitem>
-
-    <listitem>
-     <para>Add <function>family()</function> function to report whether address is IPv4 or IPv6 (Michael Graff)</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Have <literal>SHOW datestyle</literal> generate output similar
-      to that used by <literal>SET datestyle</literal> (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <literal>EXTRACT(TIMEZONE)</literal> and <literal>SET/SHOW
-      TIME ZONE</literal> follow the SQL convention for the sign of
-      time zone offsets, i.e., positive is east from UTC (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Fix <literal>date_trunc('quarter', ...)</literal> (Böjthe Zoltán)</para>
-     <para>
-      Prior releases returned an incorrect value for this function call.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Make <function>initcap()</function> more compatible with Oracle (Mike Nolan)</para>
-     <para>
-      <function>initcap()</function> now uppercases a letter appearing
-      after any non-alphanumeric character, rather than only after
-      whitespace.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow only <varname>datestyle</varname> field order for date values not in ISO-8601 format (Greg)</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add new <varname>datestyle</varname> values <literal>MDY</>,
-      <literal>DMY</>, and <literal>YMD</> to set input field order;
-      honor <literal>US</> and <literal>European</> for backward
-      compatibility (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      String literals like <literal>'now'</literal> or
-      <literal>'today'</literal> will no longer work as a column
-      default. Use functions such as <function>now()</function>,
-      <function>current_timestamp</function> instead.  (change
-      required for prepared statements) (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Treat NaN as larger than any other value in <function>min()</>/<function>max()</> (Tom)</para>
-     <para>
-      NaN was already sorted after ordinary numeric values for most
-      purposes, but <function>min()</> and <function>max()</> didn't
-      get this right.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Prevent interval from suppressing <literal>:00</literal>
-     seconds display</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      New functions <function>pg_get_triggerdef(prettyprint)</function>
-      and <function>pg_conversion_is_visible()</function> (Christopher)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow time to be specified as <literal>040506</> or <literal>0405</> (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Input date order must now be <literal>YYYY-MM-DD</literal> (with 4-digit year) or
-      match <varname>datestyle</varname>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>pg_get_constraintdef</function> support
-      unique, primary-key, and check constraints (Christopher)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Server-Side Language Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Prevent PL/pgSQL crash when <literal>RETURN NEXT</literal> is
-      used on a zero-row record variable (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make PL/Python's <function>spi_execute</function> interface
-      handle null values properly (Andrew Bosma)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow PL/pgSQL to declare variables of composite types without <literal>%ROWTYPE</literal> (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Fix PL/Python's <function>_quote()</function> function to handle big integers</para>
-    </listitem>
-
-    <listitem>
-     <para>Make PL/Python an untrusted language, now called <literal>plpythonu</literal> (Kevin Jacobs, Tom)</para>
-     <para>
-      The Python language no longer supports a restricted execution
-      environment, so the trusted version of PL/Python was removed. If
-      this situation changes, a version of PL/Python that can be used
-      by non-superusers will be readded.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow polymorphic PL/pgSQL functions (Joe, Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Allow polymorphic SQL functions (Joe)</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Improved compiled function caching mechanism in PL/pgSQL with
-      full support for polymorphism (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add new parameter <literal>$0</> in PL/pgSQL representing the
-      function's actual return type (Joe)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow PL/Tcl and PL/Python to use the same trigger on multiple tables (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Fixed PL/Tcl's <function>spi_prepare</function> to accept fully
-      qualified type names in the parameter type list
-      (Jan)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>psql Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>Add <literal>\pset pager always</literal> to always use pager (Greg)</para>
-     <para>
-      This forces the pager to be used even if the number of rows is
-      less than the screen height.  This is valuable for rows that
-      wrap across several screen rows.
-     </para>
-    </listitem>
-
-    <listitem><para>Improve tab completion (Rod, Ross Reedstrom, Ian Barwick)</para></listitem>
-    <listitem><para>Reorder <literal>\?</> help into groupings (Harald Armin Massa, Bruce)</para></listitem>
-    <listitem><para>Add backslash commands for listing schemas, casts, and conversions (Christopher)</para></listitem>
-
-    <listitem>
-     <para>
-      <command>\encoding</> now changes based on the server parameter
-      <varname>client_encoding</varname> (Tom)
-     </para>
-     <para>
-      In previous versions, <command>\encoding</command> was not aware
-      of encoding changes made using <literal>SET
-      client_encoding</literal>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Save editor buffer into readline history (Ross)</para>
-     <para>
-      When <command>\e</> is used to edit a query, the result is saved
-      in the readline history for retrieval using the up arrow.
-     </para>
-    </listitem>
-
-    <listitem><para>Improve <command>\d</command> display (Christopher)</para></listitem>
-    <listitem><para>Enhance HTML mode to be more standards-conforming (Greg)</para></listitem>
-
-    <listitem>
-     <para>New <command>\set AUTOCOMMIT off</command> capability (Tom)</para>
-     <para>
-      This takes the place of the removed server parameter <varname>autocommit</varname>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>New <command>\set VERBOSITY</command> to control error detail (Tom)</para>
-     <para>
-      This controls the new error reporting details.
-     </para>
-    </listitem>
-
-    <listitem><para>New prompt escape sequence <literal>%x</literal> to show transaction status (Tom)</para></listitem>
-    <listitem><para>Long options for <application>psql</application> are now available on all platforms</para></listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>pg_dump Changes</title>
-
-   <itemizedlist>
-    <listitem><para>Multiple pg_dump fixes, including tar format and large objects</para></listitem>
-    <listitem><para>Allow pg_dump to dump specific schemas (Neil)</para></listitem>
-
-    <listitem>
-     <para>Make pg_dump preserve column storage characteristics (Christopher)</para>
-     <para>
-      This preserves <literal>ALTER TABLE ... SET STORAGE</literal> information.
-     </para>
-    </listitem>
-
-    <listitem><para>Make pg_dump preserve <command>CLUSTER</command> characteristics (Christopher)</para></listitem>
-
-    <listitem>
-     <para>
-      Have pg_dumpall use <command>GRANT</>/<command>REVOKE</> to dump database-level privileges (Tom)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow pg_dumpall to support the options <option>-a</>,
-      <option>-s</>, <option>-x</> of pg_dump (Tom)
-     </para>
-    </listitem>
-
-    <listitem><para>Prevent pg_dump from lowercasing identifiers specified on the command line (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      pg_dump options <option>--use-set-session-authorization</option>
-      and <option>--no-reconnect</option> now do nothing, all dumps
-      use <command>SET SESSION AUTHORIZATION</command>
-     </para>
-     <para>
-      pg_dump no longer reconnects to switch users, but instead always
-      uses <command>SET SESSION AUTHORIZATION</command>. This will
-      reduce password prompting during restores.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Long options for <application>pg_dump</application> are now available on all platforms</para>
-     <para>
-      <productname>PostgreSQL</productname> now includes its own
-      long-option processing routines.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>libpq Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Add function <function>PQfreemem</function> for freeing memory on
-      Windows, suggested for <command>NOTIFY</command> (Bruce)
-     </para>
-     <para>
-      Windows requires that memory allocated in a library be freed by
-      a function in the same library, hence
-      <function>free()</function> doesn't work for freeing memory
-      allocated by libpq. <function>PQfreemem</function> is the proper
-      way to free libpq memory, especially on Windows, and is
-      recommended for other platforms as well.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Document service capability, and add sample file (Bruce)</para>
-     <para>
-      This allows clients to look up connection information in a
-      central file on the client machine.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Make <function>PQsetdbLogin</function> have the same defaults as
-      <function>PQconnectdb</function> (Tom)
-     </para>
-    </listitem>
-
-    <listitem><para>Allow libpq to cleanly fail when result sets are too large (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Improve performance of function <function>PQunescapeBytea</function> (Ben Lamb)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow thread-safe libpq with <filename>configure</filename>
-      option <option>--enable-thread-safety</option> (Lee Kindness,
-      Philip Yarra)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow function <function>pqInternalNotice</function> to accept a
-      format string and arguments instead of just a preformatted
-      message (Tom, Sean Chittenden)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Control SSL negotiation with <literal>sslmode</literal> values
-      <literal>disable</literal>, <literal>allow</literal>,
-      <literal>prefer</literal>, and <literal>require</literal> (Jon
-      Jensen)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Allow new error codes and levels of text (Tom)</para>
-    </listitem>
-
-    <listitem>
-     <para>Allow access to the underlying table and column of a query result (Tom)</para>
-     <para>
-      This is helpful for query-builder applications that want to know
-      the underlying table and column names associated with a specific
-      result set.
-     </para>
-    </listitem>
-
-    <listitem><para>Allow access to the current transaction status (Tom)</para></listitem>
-    <listitem><para>Add ability to pass binary data directly to the server (Tom)</para></listitem>
-
-    <listitem>
-     <para>
-      Add function <function>PQexecPrepared</function> and
-      <function>PQsendQueryPrepared</function> functions which perform
-      bind/execute of previously prepared statements (Tom)
-      </para>
-     </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>JDBC Changes</title>
-
-   <itemizedlist>
-    <listitem><para>Allow <function>setNull</function> on updateable result sets</para></listitem>
-    <listitem><para>Allow <function>executeBatch</function> on a prepared statement (Barry)</para></listitem>
-    <listitem><para>Support SSL connections (Barry)</para></listitem>
-    <listitem><para>Handle schema names in result sets (Paul Sorenson)</para></listitem>
-    <listitem><para>Add refcursor support (Nic Ferrier)</para></listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Miscellaneous Interface Changes</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>Prevent possible memory leak or core dump during libpgtcl shutdown (Tom)</para>
-    </listitem>
-    <listitem>
-     <para>Add Informix compatibility to ECPG (Michael)</para>
-     <para>
-      This allows ECPG to process embedded C programs that were
-      written using certain Informix extensions.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Add type <type>decimal</type> to ECPG that is fixed length, for Informix (Michael)</para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Allow thread-safe embedded SQL programs with
-      <filename>configure</filename> option
-      <option>--enable-thread-safety</option> (Lee Kindness, Bruce)
-     </para>
-     <para>
-      This allows multiple threads to access the database at the same
-      time.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>Moved Python client PyGreSQL to <ulink url="http://www.pygresql.org"></ulink> (Marc)</para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Source Code Changes</title>
-
-   <itemizedlist>
-    <listitem><para>Prevent need for separate platform geometry regression result files (Tom)</para></listitem>
-    <listitem><para>Improved PPC locking primitive (Reinhard Max)</para></listitem>
-    <listitem><para>New function <function>palloc0</function> to allocate and clear memory (Bruce)</para></listitem>
-    <listitem><para>Fix locking code for s390x CPU (64-bit) (Tom)</para></listitem>
-    <listitem><para>Allow OpenBSD to use local ident credentials (William Ahern)</para></listitem>
-    <listitem><para>Make query plan trees read-only to executor (Tom)</para></listitem>
-    <listitem><para>Add Darwin startup scripts (David Wheeler)</para></listitem>
-    <listitem><para>Allow libpq to compile with Borland C++ compiler (Lester Godwin, Karl Waclawek)</para></listitem>
-    <listitem><para>Use our own version of <function>getopt_long()</function> if needed (Peter)</para></listitem>
-    <listitem><para>Convert administration scripts to C (Peter)</para></listitem>
-    <listitem><para> Bison &gt;= 1.85 is now required to build the <productname>PostgreSQL</> grammar, if building from CVS</para></listitem>
-    <listitem><para>Merge documentation into one book (Peter)</para></listitem>
-    <listitem><para>Add Windows compatibility functions (Bruce)</para></listitem>
-    <listitem><para>Allow client interfaces to compile under MinGW (Bruce)</para></listitem>
-    <listitem><para>New <function>ereport()</function> function for error reporting (Tom)</para></listitem>
-    <listitem><para>Support Intel compiler on Linux (Peter)</para></listitem>
-    <listitem><para>Improve Linux startup scripts (Slawomir Sudnik, Darko Prenosil)</para></listitem>
-    <listitem><para>Add support for AMD Opteron and Itanium (Jeffrey W. Baker, Bruce)</para></listitem>
-    <listitem>
-     <para>Remove <option>--enable-recode</option> option from <command>configure</command></para>
-     <para>
-      This was no longer needed now that we have <command>CREATE CONVERSION</command>.
-     </para>
-    </listitem>
-    <listitem>
-     <para>Generate a compile error if spinlock code is not found (Bruce)</para>
-     <para>
-      Platforms without spinlock code will now fail to compile, rather
-      than silently using semaphores. This failure can be disabled
-      with a new <command>configure</command> option.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect3>
-
-  <sect3>
-   <title>Contrib Changes</title>
-
-   <itemizedlist>
-    <listitem><para>Change dbmirror license to BSD</para></listitem>
-    <listitem><para>Improve earthdistance (Bruno Wolff III)</para></listitem>
-    <listitem><para>Portability improvements to pgcrypto (Marko Kreen)</para></listitem>
-    <listitem><para>Prevent crash in xml (John Gray, Michael Richards)</para></listitem>
-    <listitem><para>Update oracle</para></listitem>
-    <listitem><para>Update mysql</para></listitem>
-    <listitem><para>Update cube (Bruno Wolff III)</para></listitem>
-    <listitem><para>Update earthdistance to use cube (Bruno Wolff III)</para></listitem>
-    <listitem><para>Update btree_gist (Oleg)</para></listitem>
-    <listitem><para>New tsearch2 full-text search module (Oleg, Teodor)</para></listitem>
-    <listitem><para>Add hash-based crosstab function to tablefuncs (Joe)</para></listitem>
-    <listitem><para>Add serial column to order <function>connectby()</> siblings in tablefuncs (Nabil Sayegh,Joe)</para></listitem>
-    <listitem><para>Add named persistent connections to dblink (Shridhar Daithanka)</para></listitem>
-    <listitem><para>New pg_autovacuum allows automatic <command>VACUUM</command> (Matthew T. O'Connor)</para></listitem>
-    <listitem><para>Make pgbench honor environment variables <envar>PGHOST</>, <envar>PGPORT</>, <envar>PGUSER</> (Tatsuo)</para></listitem>
-    <listitem><para>Improve intarray (Teodor Sigaev)</para></listitem>
-    <listitem><para>Improve pgstattuple (Rod)</para></listitem>
-    <listitem><para>Fix bug in <function>metaphone()</function> in fuzzystrmatch</para></listitem>
-    <listitem><para>Improve adddepend (Rod)</para></listitem>
-    <listitem><para>Update spi/timetravel (Böjthe Zoltán)</para></listitem>
-    <listitem><para>Fix dbase <option>-s</> option and improve non-ASCII handling (Thomas Behr, Márcio Smiderle)</para></listitem>
-    <listitem><para>Remove array module because features now included by default (Joe)</para></listitem>
-   </itemizedlist>
-  </sect3>
   </sect2>
  </sect1>
 
-  <sect1 id="release-7-3-20">
-   <title>Release 7.3.20</title>
+ <sect1 id="release-7-3-20">
+  <title>Release 7.3.20</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2007-09-17</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-09-17</simpara>
+  </note>
+
+  <para>
+   This release contains fixes from 7.3.19.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.20</title>
 
    <para>
-    This release contains fixes from 7.3.19.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.20</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
-    </para>
+  <sect2>
+   <title>Changes</title>
 
-   </sect2>
+   <itemizedlist>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+     <para>
+      Prevent index corruption when a transaction inserts rows and
+      then aborts close to the end of a concurrent <command>VACUUM</>
+      on the same table (Tom)
+     </para>
+    </listitem>
 
-    <itemizedlist>
+    <listitem>
+     <para>
+      Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Prevent index corruption when a transaction inserts rows and
-       then aborts close to the end of a concurrent <command>VACUUM</>
-       on the same table (Tom)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Fix crash when <varname>log_min_error_statement</> logging runs out
+      of memory (Tom)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Make <command>CREATE DOMAIN ... DEFAULT NULL</> work properly (Tom)
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      Require non-superusers who use <filename>/contrib/dblink</> to use only
+      password authentication, as a security measure (Joe)
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Fix crash when <varname>log_min_error_statement</> logging runs out
-       of memory (Tom)
-      </para>
-     </listitem>
+   </itemizedlist>
 
-     <listitem>
-      <para>
-       Require non-superusers who use <filename>/contrib/dblink</> to use only
-       password authentication, as a security measure (Joe)
-      </para>
-     </listitem>
+  </sect2>
+ </sect1>
 
-    </itemizedlist>
+ <sect1 id="release-7-3-19">
+  <title>Release 7.3.19</title>
 
-   </sect2>
-  </sect1>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-04-23</simpara>
+  </note>
 
-  <sect1 id="release-7-3-19">
-   <title>Release 7.3.19</title>
+  <para>
+   This release contains fixes from 7.3.18,
+   including a security fix.
+  </para>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2007-04-23</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.3.19</title>
 
    <para>
-    This release contains fixes from 7.3.18,
-    including a security fix.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.19</title>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
+
+   <itemizedlist>
+
+    <listitem>
     <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
+     Support explicit placement of the temporary-table schema within
+     <varname>search_path</>, and disable searching it for functions
+     and operators (Tom)
     </para>
+    <para>
+     This is needed to allow a security-definer function to set a
+     truly secure value of <varname>search_path</>.  Without it,
+     an unprivileged SQL user can use temporary objects to execute code
+     with the privileges of the security-definer function (CVE-2007-2138).
+     See <command>CREATE FUNCTION</> for more information.
+    </para>
+    </listitem>
 
-   </sect2>
+    <listitem>
+    <para>
+     Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
+     <command>UPDATE</> chains (Tom, Pavan Deolasee)
+    </para>
+    </listitem>
 
-   <sect2>
-    <title>Changes</title>
+   </itemizedlist>
 
-    <itemizedlist>
+  </sect2>
+ </sect1>
 
-     <listitem>
-     <para>
-      Support explicit placement of the temporary-table schema within
-      <varname>search_path</>, and disable searching it for functions
-      and operators (Tom)
-     </para>
-     <para>
-      This is needed to allow a security-definer function to set a
-      truly secure value of <varname>search_path</>.  Without it,
-      an unprivileged SQL user can use temporary objects to execute code
-      with the privileges of the security-definer function (CVE-2007-2138).
-      See <command>CREATE FUNCTION</> for more information.
-     </para>
-     </listitem>
+ <sect1 id="release-7-3-18">
+  <title>Release 7.3.18</title>
 
-     <listitem>
-     <para>
-      Fix potential-data-corruption bug in how <command>VACUUM FULL</> handles
-      <command>UPDATE</> chains (Tom, Pavan Deolasee)
-     </para>
-     </listitem>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-02-05</simpara>
+  </note>
 
-    </itemizedlist>
+  <para>
+   This release contains a variety of fixes from 7.3.17, including
+   a security fix.
+  </para>
 
-   </sect2>
-  </sect1>
-
-  <sect1 id="release-7-3-18">
-   <title>Release 7.3.18</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2007-02-05</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.3.18</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.17, including
-    a security fix.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.18</title>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
+
+   <itemizedlist>
+
+    <listitem>
     <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
+     Remove security vulnerability that allowed connected users
+     to read backend memory (Tom)
     </para>
+    <para>
+     The vulnerability involves changing the
+     data type of a table column used in a SQL function (CVE-2007-0555).
+     This error can easily be exploited to cause a backend crash, and in
+     principle might be used to read database content that the user
+     should not be able to access.
+    </para>
+    </listitem>
 
-   </sect2>
+    <listitem>
+    <para>
+     Fix rare bug wherein btree index page splits could fail
+     due to choosing an infeasible split point (Heikki Linnakangas)
+    </para>
+    </listitem>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+    <para>
+     Tighten security of multi-byte character processing for UTF8 sequences
+     over three bytes long (Tom)
+    </para>
+    </listitem>
 
-    <itemizedlist>
+   </itemizedlist>
 
-     <listitem>
-     <para>
-      Remove security vulnerability that allowed connected users
-      to read backend memory (Tom)
-     </para>
-     <para>
-      The vulnerability involves changing the
-      data type of a table column used in a SQL function (CVE-2007-0555).
-      This error can easily be exploited to cause a backend crash, and in
-      principle might be used to read database content that the user
-      should not be able to access.
-     </para>
-     </listitem>
+  </sect2>
+ </sect1>
 
-     <listitem>
-     <para>
-      Fix rare bug wherein btree index page splits could fail
-      due to choosing an infeasible split point (Heikki Linnakangas)
-     </para>
-     </listitem>
+ <sect1 id="release-7-3-17">
+  <title>Release 7.3.17</title>
 
-     <listitem>
-     <para>
-      Tighten security of multi-byte character processing for UTF8 sequences
-      over three bytes long (Tom)
-     </para>
-     </listitem>
+  <note>
+  <title>Release date</title>
+  <simpara>2007-01-08</simpara>
+  </note>
 
-    </itemizedlist>
+  <para>
+   This release contains a variety of fixes from 7.3.16.
+  </para>
 
-   </sect2>
-  </sect1>
-
-  <sect1 id="release-7-3-17">
-   <title>Release 7.3.17</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2007-01-08</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.3.17</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.16.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.17</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
-    </para>
+  <sect2>
+   <title>Changes</title>
 
-   </sect2>
+   <itemizedlist>
 
-   <sect2>
-    <title>Changes</title>
+    <listitem>
+     <para>
+      <function>to_number()</> and <function>to_char(numeric)</>
+      are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
+      new <application>initdb</> installs (Tom)
+     </para>
 
-    <itemizedlist>
+     <para>
+      This is because <varname>lc_numeric</> can potentially
+      change the output of these functions.
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       <function>to_number()</> and <function>to_char(numeric)</>
-       are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
-       new <application>initdb</> installs (Tom)
-      </para>
+    <listitem>
+     <para>
+      Improve index usage of regular expressions that use parentheses (Tom)
+     </para>
 
-      <para>
-       This is because <varname>lc_numeric</> can potentially
-       change the output of these functions.
-      </para>
-     </listitem>
+     <para>
+      This improves <application>psql</> <literal>\d</> performance also.
+     </para>
+    </listitem>
 
-     <listitem>
-      <para>
-       Improve index usage of regular expressions that use parentheses (Tom)
-      </para>
+   </itemizedlist>
 
-      <para>
-       This improves <application>psql</> <literal>\d</> performance also.
-      </para>
-     </listitem>
+  </sect2>
+ </sect1>
 
-    </itemizedlist>
+ <sect1 id="release-7-3-16">
+  <title>Release 7.3.16</title>
 
-   </sect2>
-  </sect1>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-10-16</simpara>
+  </note>
 
-  <sect1 id="release-7-3-16">
-   <title>Release 7.3.16</title>
+  <para>
+   This release contains a variety of fixes from 7.3.15.
+  </para>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-10-16</simpara>
-   </note>
+  <sect2>
+   <title>Migration to Version 7.3.16</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.15.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.16</title>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix corner cases in pattern matching for
-  <application>psql</>'s <literal>\d</> commands</para></listitem>
+ <application>psql</>'s <literal>\d</> commands</para></listitem>
 <listitem><para>Fix index-corrupting bugs in /contrib/ltree
-  (Teodor)</para></listitem>
+ (Teodor)</para></listitem>
 <listitem><para>Back-port 7.4 spinlock code to improve performance and support
 64-bit architectures better</para> </listitem>
 <listitem><para>Fix SSL-related memory leak in libpq</para> </listitem>
@@ -3567,46 +3831,46 @@ DROP SCHEMA information_schema CASCADE;
 </para> </listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-15">
-   <title>Release 7.3.15</title>
+ <sect1 id="release-7-3-15">
+  <title>Release 7.3.15</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-05-23</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-05-23</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.14,
+   including patches for extremely serious security issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.15</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.14,
-    including patches for extremely serious security issues.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.15</title>
+   <para>
+    Full security against the SQL-injection attacks described in
+    CVE-2006-2313 and CVE-2006-2314 might require changes in application
+    code.  If you have applications that embed untrustworthy strings
+    into SQL commands, you should examine them as soon as possible to
+    ensure that they are using recommended escaping techniques.  In
+    most cases, applications should be using subroutines provided by
+    libraries or drivers (such as <application>libpq</>'s
+    <function>PQescapeStringConn()</>) to perform string escaping,
+    rather than relying on <foreignphrase>ad hoc</> code to do it.
+   </para>
+  </sect2>
 
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
-    </para>
-
-    <para>
-     Full security against the SQL-injection attacks described in
-     CVE-2006-2313 and CVE-2006-2314 might require changes in application
-     code.  If you have applications that embed untrustworthy strings
-     into SQL commands, you should examine them as soon as possible to
-     ensure that they are using recommended escaping techniques.  In
-     most cases, applications should be using subroutines provided by
-     libraries or drivers (such as <application>libpq</>'s
-     <function>PQescapeStringConn()</>) to perform string escaping,
-     rather than relying on <foreignphrase>ad hoc</> code to do it.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Change the server to reject invalidly-encoded multibyte
@@ -3659,33 +3923,33 @@ Fuhr)</para></listitem>
 <listitem><para>Fix various minor memory leaks</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-14">
-   <title>Release 7.3.14</title>
+ <sect1 id="release-7-3-14">
+  <title>Release 7.3.14</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-02-14</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-02-14</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.13.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.14</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.13.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.13, see the release
+    notes for 7.3.13.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.14</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.13, see the release
-     notes for 7.3.13.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -3716,36 +3980,36 @@ and <function>isinf</> during configure (Tom)</para></listitem>
 
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-13">
-   <title>Release 7.3.13</title>
+ <sect1 id="release-7-3-13">
+  <title>Release 7.3.13</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2006-01-09</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2006-01-09</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.12.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.13</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.12.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.10, see the release
+    notes for 7.3.10.
+    Also, you might need to <command>REINDEX</> indexes on textual
+    columns after updating, if you are affected by the locale or
+    <application>plperl</> issues described below.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.13</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.10, see the release
-     notes for 7.3.10.
-     Also, you might need to <command>REINDEX</> indexes on textual
-     columns after updating, if you are affected by the locale or
-     <application>plperl</> issues described below.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -3778,33 +4042,33 @@ what's actually returned by the query (Joe)</para></listitem>
 
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-12">
-   <title>Release 7.3.12</title>
+ <sect1 id="release-7-3-12">
+  <title>Release 7.3.12</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-12-12</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-12-12</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.11.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.12</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.11.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.10, see the release
+    notes for 7.3.10.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.12</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.10, see the release
-     notes for 7.3.10.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 
@@ -3825,33 +4089,33 @@ table has been dropped</para></listitem>
 
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-11">
-   <title>Release 7.3.11</title>
+ <sect1 id="release-7-3-11">
+  <title>Release 7.3.11</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-10-04</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-10-04</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.10.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.11</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.10.
+    A dump/restore is not required for those running 7.3.X.  However,
+    if you are upgrading from a version earlier than 7.3.10, see the release
+    notes for 7.3.10.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.11</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     if you are upgrading from a version earlier than 7.3.10, see the release
-     notes for 7.3.10.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix error that allowed <command>VACUUM</> to remove
@@ -3876,87 +4140,87 @@ enabled</para></listitem>
 the variable is of pass-by-reference type</para></listitem>
 </itemizedlist>
 
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-3-10">
-   <title>Release 7.3.10</title>
+ <sect1 id="release-7-3-10">
+  <title>Release 7.3.10</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-05-09</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-05-09</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.9, including several
+   security-related issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.10</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.9, including several
-    security-related issues.
+    A dump/restore is not required for those running 7.3.X.  However,
+    it is one possible way of handling a significant security problem
+    that has been found in the initial contents of 7.3.X system
+    catalogs.  A dump/initdb/reload sequence using 7.3.10's initdb will
+    automatically correct this problem.
    </para>
 
-   <sect2>
-    <title>Migration to version 7.3.10</title>
+   <para>
+    The security problem is that the built-in character set encoding
+    conversion functions can be invoked from SQL commands by unprivileged
+    users, but the functions were not designed for such use and are not
+    secure against malicious choices of arguments.  The fix involves changing
+    the declared parameter list of these functions so that they can no longer
+    be invoked from SQL commands.  (This does not affect their normal use
+    by the encoding conversion machinery.)
+    It is strongly recommended that all installations repair this error,
+    either by initdb or by following the manual repair procedure given
+    below.  The error at least allows unprivileged database users to crash
+    their server process, and might allow unprivileged users to gain the
+    privileges of a database superuser.
+   </para>
 
-    <para>
-     A dump/restore is not required for those running 7.3.X.  However,
-     it is one possible way of handling a significant security problem
-     that has been found in the initial contents of 7.3.X system
-     catalogs.  A dump/initdb/reload sequence using 7.3.10's initdb will
-     automatically correct this problem.
-    </para>
-
-    <para>
-     The security problem is that the built-in character set encoding
-     conversion functions can be invoked from SQL commands by unprivileged
-     users, but the functions were not designed for such use and are not
-     secure against malicious choices of arguments.  The fix involves changing
-     the declared parameter list of these functions so that they can no longer
-     be invoked from SQL commands.  (This does not affect their normal use
-     by the encoding conversion machinery.)
-     It is strongly recommended that all installations repair this error,
-     either by initdb or by following the manual repair procedure given
-     below.  The error at least allows unprivileged database users to crash
-     their server process, and might allow unprivileged users to gain the
-     privileges of a database superuser.
-    </para>
-
-    <para>
-     If you wish not to do an initdb, perform the following procedure instead.
-     As the database superuser, do:
+   <para>
+    If you wish not to do an initdb, perform the following procedure instead.
+    As the database superuser, do:
 
 <programlisting>
 BEGIN;
 UPDATE pg_proc SET proargtypes[3] = 'internal'::regtype
 WHERE pronamespace = 11 AND pronargs = 5
-      AND proargtypes[2] = 'cstring'::regtype;
+     AND proargtypes[2] = 'cstring'::regtype;
 -- The command should report having updated 90 rows;
 -- if not, rollback and investigate instead of committing!
 COMMIT;
 </programlisting>
-    </para>
+   </para>
 
-    <para>
-     The above procedure must be carried out in <emphasis>each</> database
-     of an installation, including <literal>template1</>, and ideally
-     including <literal>template0</> as well.  If you do not fix the
-     template databases then any subsequently created databases will contain
-     the same error.  <literal>template1</> can be fixed in the same way
-     as any other database, but fixing <literal>template0</> requires
-     additional steps.  First, from any database issue:
+   <para>
+    The above procedure must be carried out in <emphasis>each</> database
+    of an installation, including <literal>template1</>, and ideally
+    including <literal>template0</> as well.  If you do not fix the
+    template databases then any subsequently created databases will contain
+    the same error.  <literal>template1</> can be fixed in the same way
+    as any other database, but fixing <literal>template0</> requires
+    additional steps.  First, from any database issue:
 <programlisting>
 UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
 </programlisting>
-      Next connect to <literal>template0</> and perform the above repair
-      procedure.  Finally, do:
+     Next connect to <literal>template0</> and perform the above repair
+     procedure.  Finally, do:
 <programlisting>
 -- re-freeze template0:
 VACUUM FREEZE;
 -- and protect it against future alterations:
 UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
 </programlisting>
-    </para>
-   </sect2>
+   </para>
+  </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Change encoding function signature to prevent
@@ -4002,32 +4266,32 @@ month-related formats</para></listitem>
 <type>RECORD</></para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-9">
-   <title>Release 7.3.9</title>
+ <sect1 id="release-7-3-9">
+  <title>Release 7.3.9</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-01-31</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-01-31</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.8, including several
+   security-related issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.3.9</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.8, including several
-    security-related issues.
+    A dump/restore is not required for those running 7.3.X.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.9</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Disallow <command>LOAD</> to non-superusers</para>
@@ -4058,32 +4322,32 @@ in case of nested merge joins could give outright wrong answers.
 datestyles</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-8">
-   <title>Release 7.3.8</title>
+ <sect1 id="release-7-3-8">
+  <title>Release 7.3.8</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-10-22</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-10-22</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.7.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.3.8</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.7.
+    A dump/restore is not required for those running 7.3.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.3.8</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair possible failure to update hint bits on disk</para>
@@ -4108,32 +4372,32 @@ concern since there is no reason for non-developers to use this script anyway.
 </para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-7">
-   <title>Release 7.3.7</title>
+ <sect1 id="release-7-3-7">
+  <title>Release 7.3.7</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-08-16</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-08-16</simpara>
+  </note>
+
+  <para>
+   This release contains one critical fix over 7.3.6, and some minor items.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.3.7</title>
 
    <para>
-    This release contains one critical fix over 7.3.6, and some minor items.
+    A dump/restore is not required for those running 7.3.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.3.7</title>
-
-    <para>
-     A dump/restore is not required for those running 7.3.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Prevent possible loss of committed transactions during crash</para>
@@ -4148,34 +4412,34 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Properly schema-qualify function names when pg_dump'ing a CAST</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-6">
-   <title>Release 7.3.6</title>
+ <sect1 id="release-7-3-6">
+  <title>Release 7.3.6</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-03-02</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-03-02</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.3.5.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.3.6</title>
 
    <para>
-    This release contains a variety of fixes from 7.3.5.
+    A dump/restore is <emphasis>not</emphasis> required for those
+    running 7.3.*.
    </para>
 
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.3.6</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those
-     running 7.3.*.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Revert erroneous changes in rule permissions checking</para>
@@ -4213,33 +4477,33 @@ in multibyte cases (Korea PostgreSQL Users' Group)</para></listitem>
 operations on bytea columns (Joe)</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-5">
-   <title>Release 7.3.5</title>
+ <sect1 id="release-7-3-5">
+  <title>Release 7.3.5</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2003-12-03</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2003-12-03</simpara>
+  </note>
+
+  <para>
+   This has a variety of fixes from 7.3.4.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.3.5</title>
 
    <para>
-    This has a variety of fixes from 7.3.4.
+    A dump/restore is <emphasis>not</emphasis> required for those
+    running 7.3.*.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.3.5</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those
-     running 7.3.*.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Force zero_damaged_pages to be on during recovery from WAL</para></listitem>
@@ -4264,33 +4528,33 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix corner case for btree search in parallel with first root page split</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-3-4">
-   <title>Release 7.3.4</title>
+ <sect1 id="release-7-3-4">
+  <title>Release 7.3.4</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2003-07-24</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2003-07-24</simpara>
+  </note>
+
+  <para>
+   This has a variety of fixes from 7.3.3.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.3.4</title>
 
    <para>
-    This has a variety of fixes from 7.3.3.
+    A dump/restore is <emphasis>not</emphasis> required for those
+    running 7.3.*.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.3.4</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those
-     running 7.3.*.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair breakage in timestamp-to-date conversion for dates before 2000</para></listitem>
@@ -4303,33 +4567,33 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Work around buggy strxfrm() present in some Solaris releases (Tom)</para></listitem>
 <listitem><para>Properly escape jdbc setObject() strings to improve security (Barry)</para></listitem>
 </itemizedlist>
-   </sect2>
-  </sect1>
+  </sect2>
+ </sect1>
 
 
- <sect1 id="release-7-3-3">
-  <title>Release 7.3.3</title>
+<sect1 id="release-7-3-3">
+ <title>Release 7.3.3</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2003-05-22</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2003-05-22</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.3.2.
+ </para>
+
+ <sect2>
+  <title>Migration to Version 7.3.3</title>
 
   <para>
-   This release contains a variety of fixes for version 7.3.2.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.3.*.
   </para>
+ </sect2>
 
-  <sect2>
-   <title>Migration to version 7.3.3</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.3.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair sometimes-incorrect computation of StartUpID after a crash</para></listitem>
@@ -4345,21 +4609,21 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Issue notice, not error, if <type>TIMESTAMP</type>,
 <type> TIME</type>, or <type>INTERVAL</type> precision too large</para></listitem>
 <listitem><para>Fix <function>abstime-to-time</function> cast function (fix is
-       not applied unless you <application>initdb</application>)</para></listitem>
+      not applied unless you <application>initdb</application>)</para></listitem>
 <listitem><para>Fix <application>pg_proc</application> entry for
-      <type>timestampt_izone</type> (fix is not applied unless you
-        <application>initdb</application>)</para></listitem>
+     <type>timestampt_izone</type> (fix is not applied unless you
+       <application>initdb</application>)</para></listitem>
 <listitem><para>Make <function>EXTRACT(EPOCH FROM timestamp without time zone)</function> treat input as local time</para></listitem>
 <listitem><para><command>'now'::timestamptz</command> gave wrong answer if timezone changed earlier in transaction</para></listitem>
 <listitem><para><envar>HAVE_INT64_TIMESTAMP</envar> code for time with timezone overwrote its input</para></listitem>
 <listitem><para>Accept <command>GLOBAL TEMP/TEMPORARY</command> as a
-       synonym for <command>TEMPORARY</command></para></listitem>
+      synonym for <command>TEMPORARY</command></para></listitem>
 <listitem><para>Avoid improper schema-privilege-check failure in foreign-key triggers</para></listitem>
 <listitem><para>Fix bugs in foreign-key triggers for <command>SET DEFAULT</command> action</para></listitem>
 <listitem><para>Fix incorrect time-qual check in row fetch for
-       <command>UPDATE</command> and <command>DELETE</command> triggers</para></listitem>
+      <command>UPDATE</command> and <command>DELETE</command> triggers</para></listitem>
 <listitem><para>Foreign-key clauses were parsed but ignored in
-       <command>ALTER TABLE ADD COLUMN</command></para></listitem>
+      <command>ALTER TABLE ADD COLUMN</command></para></listitem>
 <listitem><para>Fix createlang script breakage for case where handler function already exists</para></listitem>
 <listitem><para>Fix misbehavior on zero-column tables in <application>pg_dump</application>, COPY, ANALYZE, other places</para></listitem>
 <listitem><para>Fix misbehavior of <function>func_error()</function> on type names containing '%'</para></listitem>
@@ -4393,13 +4657,13 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix replace_vars_with_subplan_refs failure in complex views</para></listitem>
 <listitem><para>Fix regexp slowness in single-byte encodings (Tatsuo)</para></listitem>
 <listitem><para>Allow qualified type names in <command>CREATE CAST</command>
-       and <command> DROP CAST</command></para></listitem>
+      and <command> DROP CAST</command></para></listitem>
 <listitem><para>Accept <function>SETOF type[]</function>, which formerly had to
-       be written <function>SETOF _type</function></para></listitem>
+      be written <function>SETOF _type</function></para></listitem>
 <listitem><para>Fix <application>pg_dump</application> core dump in some cases with procedural languages</para></listitem>
 <listitem><para>Force ISO datestyle in <application>pg_dump</application> output, for portability (Oliver)</para></listitem>
 <listitem><para><application>pg_dump</application> failed to handle error return
-       from <function>lo_read</function> (Oleg Drokin)</para></listitem>
+      from <function>lo_read</function> (Oleg Drokin)</para></listitem>
 <listitem><para><application>pg_dumpall</application> failed with groups having no members (Nick Eskelinen)</para></listitem>
 <listitem><para><application>pg_dumpall</application> failed to recognize --globals-only switch</para></listitem>
 <listitem><para>pg_restore failed to restore blobs if -X disable-triggers is specified</para></listitem>
@@ -4413,34 +4677,34 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fixed problem with parsing table ACLs in JDBC</para></listitem>
 <listitem><para>Better error message for character set conversion problems in JDBC</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-3-2">
-  <title>Release 7.3.2</title>
+<sect1 id="release-7-3-2">
+ <title>Release 7.3.2</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2003-02-04</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2003-02-04</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.3.1.
+ </para>
+
+
+ <sect2>
+  <title>Migration to Version 7.3.2</title>
 
   <para>
-   This release contains a variety of fixes for version 7.3.1.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.3.*.
   </para>
+ </sect2>
 
-
-  <sect2>
-   <title>Migration to version 7.3.2</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.3.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Restore creation of OID column in CREATE TABLE AS / SELECT INTO</para></listitem>
@@ -4474,37 +4738,37 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Add casts between types lo and oid in contrib/lo</para></listitem>
 <listitem><para>fastpath code now checks for privilege to call function</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-3-1">
-  <title>Release 7.3.1</title>
+<sect1 id="release-7-3-1">
+ <title>Release 7.3.1</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-12-18</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-12-18</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.3.
+ </para>
+
+
+ <sect2>
+  <title>Migration to Version 7.3.1</title>
 
   <para>
-   This release contains a variety of fixes for version 7.3.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.3. However, it should be noted that the main
+   <productname>PostgreSQL</productname> interface library, libpq,
+   has a new major version number for this release, which might require
+   recompilation of client code in certain cases.
   </para>
+ </sect2>
 
-
-  <sect2>
-   <title>Migration to version 7.3.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.3. However, it should be noted that the main
-    <productname>PostgreSQL</productname> interface library, libpq,
-    has a new major version number for this release, which might require
-    recompilation of client code in certain cases.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix a core dump of COPY TO when client/server encodings don't match (Tom)</para></listitem>
@@ -4524,265 +4788,265 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>SSL fixes (Nathan Mueller)</para></listitem>
 <listitem><para>Prevent composite column creation via ALTER TABLE (Tom)</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-3">
-  <title>Release 7.3</title>
+<sect1 id="release-7-3">
+ <title>Release 7.3</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-11-27</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-11-27</simpara>
+ </note>
 
-  <sect2>
-   <title>Overview</title>
+ <sect2>
+  <title>Overview</title>
 
-   <para>
-    Major changes in this release:
-   </para>
+  <para>
+   Major changes in this release:
+  </para>
 
-   <variablelist>
-    <varlistentry>
-     <term>Schemas</term>
-     <listitem>
-      <para>
-       Schemas allow users to create objects in separate namespaces,
-       so two people or applications can have tables with the same
-       name. There is also a public schema for shared tables.
-       Table/index creation can be restricted by removing privileges
-       on the public schema.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Drop Column</term>
-     <listitem>
-      <para>
-       <productname>PostgreSQL</productname> now supports the
-       <literal>ALTER TABLE ... DROP COLUMN</literal> functionality.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Table Functions</term>
-     <listitem>
-      <para>
-       Functions returning multiple rows and/or multiple columns are
-       now much easier to use than before.  You can call such a
-       <quote>table function</quote> in the <literal>SELECT</literal>
-       <literal>FROM</literal> clause, treating its output like a
-       table. Also, <application>PL/pgSQL</application> functions can
-       now return sets.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Prepared Queries</term>
-     <listitem>
-      <para>
-       <productname>PostgreSQL</productname> now supports prepared
-       queries, for improved performance.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Dependency Tracking</term>
-     <listitem>
-      <para>
-       <productname>PostgreSQL</productname> now records object
-       dependencies, which allows improvements in many areas.
-       <command>DROP</command> statements now take either
-       <literal>CASCADE</> or <literal>RESTRICT</> to control whether
-       dependent objects are also dropped.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Privileges</term>
-     <listitem>
-      <para>
-       Functions and procedural languages now have privileges, and
-       functions can be defined to run with the privileges of their
-       creator.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Internationalization</term>
-     <listitem>
-      <para>
-       Both multibyte and locale support are now always enabled.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Logging</term>
-     <listitem>
-      <para>
-       A variety of logging options have been enhanced.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Interfaces</term>
-     <listitem>
-      <para>
-       A large number of interfaces have been moved to <ulink
-       url="http://gborg.postgresql.org">http://gborg.postgresql.org</>
-       where they can be developed and released independently.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Functions/Identifiers</term>
-     <listitem>
-      <para>
-       By default, functions can now take up to 32 parameters, and
-       identifiers can be up to 63 bytes long.  Also, <literal>OPAQUE</>
-       is now deprecated: there are specific <quote>pseudo-datatypes</>
-       to represent each of the former meanings of <literal>OPAQUE</>
-       in function argument and result types.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
-
-  <sect2>
-   <title>Migration to version 7.3</title>
-
-   <para>
-    A dump/restore using <application>pg_dump</> is required for those
-    wishing to migrate data from any previous release. If your
-    application examines the system catalogs, additional changes will
-    be required due to the introduction of schemas in 7.3; for more
-    information, see: <ulink
-    url="http://developer.postgresql.org/~momjian/upgrade_tips_7.3"></>.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
+  <variablelist>
+   <varlistentry>
+    <term>Schemas</term>
     <listitem>
      <para>
-      Pre-6.3 clients are no longer supported.
+      Schemas allow users to create objects in separate namespaces,
+      so two people or applications can have tables with the same
+      name. There is also a public schema for shared tables.
+      Table/index creation can be restricted by removing privileges
+      on the public schema.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Drop Column</term>
     <listitem>
      <para>
-      <filename>pg_hba.conf</filename> now has a column for the user
-      name and additional features.  Existing files need to be
-      adjusted.
+      <productname>PostgreSQL</productname> now supports the
+      <literal>ALTER TABLE ... DROP COLUMN</literal> functionality.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Table Functions</term>
     <listitem>
      <para>
-      Several <filename>postgresql.conf</filename> logging parameters
-      have been renamed.
+      Functions returning multiple rows and/or multiple columns are
+      now much easier to use than before.  You can call such a
+      <quote>table function</quote> in the <literal>SELECT</literal>
+      <literal>FROM</literal> clause, treating its output like a
+      table. Also, <application>PL/pgSQL</application> functions can
+      now return sets.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Prepared Queries</term>
     <listitem>
      <para>
-      <literal>LIMIT #,#</literal> has been disabled; use
-      <literal>LIMIT # OFFSET #</literal>.
+      <productname>PostgreSQL</productname> now supports prepared
+      queries, for improved performance.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Dependency Tracking</term>
     <listitem>
      <para>
-      <command>INSERT</command> statements with column lists must
-      specify a value for each specified column. For example,
-      <literal>INSERT INTO tab (col1, col2) VALUES ('val1')</literal>
-      is now invalid.  It's still allowed to supply fewer columns than
-      expected if the <command>INSERT</command> does not have a column list.
+      <productname>PostgreSQL</productname> now records object
+      dependencies, which allows improvements in many areas.
+      <command>DROP</command> statements now take either
+      <literal>CASCADE</> or <literal>RESTRICT</> to control whether
+      dependent objects are also dropped.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Privileges</term>
     <listitem>
      <para>
-      <type>serial</type> columns are no longer automatically
-      <literal>UNIQUE</>; thus, an index will not automatically be
-      created.
+      Functions and procedural languages now have privileges, and
+      functions can be defined to run with the privileges of their
+      creator.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Internationalization</term>
     <listitem>
      <para>
-      A <command>SET</command> command inside an aborted transaction
-      is now rolled back.
+      Both multibyte and locale support are now always enabled.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Logging</term>
     <listitem>
      <para>
-      <command>COPY</command> no longer considers missing trailing
-      columns to be null.  All columns need to be specified.
-      (However, one can achieve a similar effect by specifying a
-      column list in the <command>COPY</command> command.)
+      A variety of logging options have been enhanced.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Interfaces</term>
     <listitem>
      <para>
-      The data type <type>timestamp</type> is now equivalent to
-      <type>timestamp without time zone</type>, instead of
-      <type>timestamp with time zone</type>.
+      A large number of interfaces have been moved to <ulink
+      url="http://gborg.postgresql.org">http://gborg.postgresql.org</>
+      where they can be developed and released independently.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Functions/Identifiers</term>
     <listitem>
      <para>
-      Pre-7.3 databases loaded into 7.3 will not have the new object
-      dependencies for <type>serial</type> columns, unique
-      constraints, and foreign keys. See the directory
-      <filename>contrib/adddepend/</filename> for a detailed
-      description and a script that will add such dependencies.
+      By default, functions can now take up to 32 parameters, and
+      identifiers can be up to 63 bytes long.  Also, <literal>OPAQUE</>
+      is now deprecated: there are specific <quote>pseudo-datatypes</>
+      to represent each of the former meanings of <literal>OPAQUE</>
+      in function argument and result types.
      </para>
     </listitem>
+   </varlistentry>
 
-    <listitem>
-     <para>
-      An empty string (<literal>''</literal>) is no longer allowed as
-      the input into an integer field.  Formerly, it was silently
-      interpreted as 0.
-     </para>
-    </listitem>
+  </variablelist>
+ </sect2>
 
-   </itemizedlist>
-  </sect2>
+ <sect2>
+  <title>Migration to Version 7.3</title>
 
-  <sect2>
-   <title>Changes</title>
+  <para>
+   A dump/restore using <application>pg_dump</> is required for those
+   wishing to migrate data from any previous release. If your
+   application examines the system catalogs, additional changes will
+   be required due to the introduction of schemas in 7.3; for more
+   information, see: <ulink
+   url="http://developer.postgresql.org/~momjian/upgrade_tips_7.3"></>.
+  </para>
 
-   <sect3>
-    <title>Server Operation</title>
+  <para>
+   Observe the following incompatibilities:
+  </para>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     Pre-6.3 clients are no longer supported.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <filename>pg_hba.conf</filename> now has a column for the user
+     name and additional features.  Existing files need to be
+     adjusted.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Several <filename>postgresql.conf</filename> logging parameters
+     have been renamed.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <literal>LIMIT #,#</literal> has been disabled; use
+     <literal>LIMIT # OFFSET #</literal>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <command>INSERT</command> statements with column lists must
+     specify a value for each specified column. For example,
+     <literal>INSERT INTO tab (col1, col2) VALUES ('val1')</literal>
+     is now invalid.  It's still allowed to supply fewer columns than
+     expected if the <command>INSERT</command> does not have a column list.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <type>serial</type> columns are no longer automatically
+     <literal>UNIQUE</>; thus, an index will not automatically be
+     created.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     A <command>SET</command> command inside an aborted transaction
+     is now rolled back.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     <command>COPY</command> no longer considers missing trailing
+     columns to be null.  All columns need to be specified.
+     (However, one can achieve a similar effect by specifying a
+     column list in the <command>COPY</command> command.)
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The data type <type>timestamp</type> is now equivalent to
+     <type>timestamp without time zone</type>, instead of
+     <type>timestamp with time zone</type>.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     Pre-7.3 databases loaded into 7.3 will not have the new object
+     dependencies for <type>serial</type> columns, unique
+     constraints, and foreign keys. See the directory
+     <filename>contrib/adddepend/</filename> for a detailed
+     description and a script that will add such dependencies.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     An empty string (<literal>''</literal>) is no longer allowed as
+     the input into an integer field.  Formerly, it was silently
+     interpreted as 0.
+    </para>
+   </listitem>
+
+  </itemizedlist>
+ </sect2>
+
+ <sect2>
+  <title>Changes</title>
+
+  <sect3>
+   <title>Server Operation</title>
 <itemizedlist>
 <listitem><para>Add pg_locks view to show locks (Neil)</para></listitem>
 <listitem><para>Security fixes for password negotiation memory allocation (Neil)</para></listitem>
 <listitem><para>Remove support for version 0 FE/BE protocol (<productname>PostgreSQL</productname> 6.2 and earlier) (Tom)</para></listitem>
 <listitem><para>Reserve the last few backend slots for superusers, add parameter superuser_reserved_connections to control this (Nigel J. Andrews)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Performance</title>
+  <sect3>
+   <title>Performance</title>
 <itemizedlist>
 <listitem><para>Improve startup by calling localtime() only once (Tom)</para></listitem>
 <listitem><para>Cache system catalog information in flat files for faster startup (Tom)</para></listitem>
@@ -4803,10 +5067,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Improve free space map performance on large tables (Stephen Marshall, Tom)</para></listitem>
 <listitem><para>Improved WAL write concurrency (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Privileges</title>
+  <sect3>
+   <title>Privileges</title>
 <itemizedlist>
 <listitem><para>Add privileges on functions and procedural languages (Peter)</para></listitem>
 <listitem><para>Add OWNER to CREATE DATABASE so superusers can create databases on behalf of unprivileged users (Gavin Sherry, Tom)</para></listitem>
@@ -4814,10 +5078,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Add SET SESSION AUTHORIZATION DEFAULT and RESET SESSION AUTHORIZATION (Tom)</para></listitem>
 <listitem><para>Allow functions to be executed with the privilege of the function owner (Peter)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Server Configuration</title>
+  <sect3>
+   <title>Server Configuration</title>
 <itemizedlist>
 <listitem><para>Server log messages now tagged with LOG, not DEBUG (Bruce)</para></listitem>
 <listitem><para>Add user column to pg_hba.conf (Bruce)</para></listitem>
@@ -4836,10 +5100,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Rename show_query_stats to show_statement_stats (Bruce)</para></listitem>
 <listitem><para>Add param log_min_error_statement to print commands to logs on error (Gavin)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Queries</title>
+  <sect3>
+   <title>Queries</title>
 <itemizedlist>
 <listitem><para>Make cursors insensitive, meaning their contents do not change (Tom)</para></listitem>
 <listitem><para>Disable LIMIT #,# syntax; now only LIMIT # OFFSET # supported (Bruce)</para></listitem>
@@ -4860,10 +5124,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Allow FOR UPDATE to appear after LIMIT/OFFSET (Bruce)</para></listitem>
 <listitem><para>Add variable autocommit (Tom, David Van Wie)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Object Manipulation</title>
+  <sect3>
+   <title>Object Manipulation</title>
 <itemizedlist>
 <listitem><para>Make equals signs optional in CREATE DATABASE (Gavin Sherry)</para></listitem>
 <listitem><para>Make ALTER TABLE OWNER change index ownership too (Neil)</para></listitem>
@@ -4897,10 +5161,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Add /contrib/adddepend to handle pre-7.3 object dependencies (Rod)</para></listitem>
 <listitem><para>Allow better casting when inserting/updating values (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Utility Commands</title>
+  <sect3>
+   <title>Utility Commands</title>
 <itemizedlist>
 <listitem><para>Have COPY TO output embedded carriage returns and newlines as \r and \n (Tom)</para></listitem>
 <listitem><para>Allow DELIMITER in COPY FROM to be 8-bit clean (Tatsuo)</para></listitem>
@@ -4937,10 +5201,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix rare index corruption when a page split affects bulk delete (Tom)</para></listitem>
 <listitem><para>Fix ALTER TABLE ... ADD COLUMN for inheritance (Alvaro Herrera)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Data Types and Functions</title>
+  <sect3>
+   <title>Data Types and Functions</title>
 <itemizedlist>
 <listitem><para>Fix factorial(0) to return 1 (Bruce)</para></listitem>
 <listitem><para>Date/time/timezone improvements (Thomas)</para></listitem>
@@ -4983,10 +5247,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix to_char(1,'FM999.99') to return a period (Karel)</para></listitem>
 <listitem><para>Fix trigger/type/language functions returning OPAQUE to return proper type (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Internationalization</title>
+  <sect3>
+   <title>Internationalization</title>
 <itemizedlist>
 <listitem><para>Add additional encodings: Korean (JOHAB), Thai (WIN874), Vietnamese (TCVN), Arabic (WIN1256), Simplified Chinese (GBK), Korean (UHC) (Eiji Tokuya)</para></listitem>
 <listitem><para>Enable locale support by default (Peter)</para></listitem>
@@ -5001,10 +5265,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>pg_dumpall, pg_controldata, and pg_resetxlog now national-language aware (Peter)</para></listitem>
 <listitem><para>New and updated translations</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Server-side Languages</title>
+  <sect3>
+   <title>Server-side Languages</title>
 <itemizedlist>
 <listitem><para>Allow recursive SQL function (Peter)</para></listitem>
 <listitem><para>Change PL/Tcl build to use configured compiler and Makefile.shlib (Peter)</para></listitem>
@@ -5014,10 +5278,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Make PL/pgSQL schema-aware (Joe)</para></listitem>
 <listitem><para>Remove some memory leaks (Nigel J. Andrews, Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>psql</title>
+  <sect3>
+   <title>psql</title>
 <itemizedlist>
 <listitem><para>Don't lowercase psql \connect database name for 7.2.0 compatibility (Tom)</para></listitem>
 <listitem><para>Add psql \timing to time user queries (Greg Sabino Mullane)</para></listitem>
@@ -5031,10 +5295,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Have psql reports its version number on startup (Tom)</para></listitem>
 <listitem><para>Allow \copy to specify column names (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>libpq</title>
+  <sect3>
+   <title>libpq</title>
 <itemizedlist>
 <listitem><para>Add ~/.pgpass to store host/user password combinations (Alvaro Herrera)</para></listitem>
 <listitem><para>Add PQunescapeBytea() function to libpq (Patrick Welche)</para></listitem>
@@ -5045,10 +5309,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix for SSL with non-blocking connections (Jack Bates)</para></listitem>
 <listitem><para>Add libpq connection timeout parameter (Denis A Ustimenko)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>JDBC</title>
+  <sect3>
+   <title>JDBC</title>
 <itemizedlist>
 <listitem><para>Allow JDBC to compile with JDK 1.4 (Dave)</para></listitem>
 <listitem><para>Add JDBC 3 support (Barry)</para></listitem>
@@ -5061,10 +5325,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fix MD5 encryption handling for multibyte servers (Jun Kawai)</para></listitem>
 <listitem><para>Add support for prepared statements (Barry)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Miscellaneous Interfaces</title>
+  <sect3>
+   <title>Miscellaneous Interfaces</title>
 <itemizedlist>
 <listitem><para>Fixed ECPG bug concerning octal numbers in single quotes (Michael)</para></listitem>
 <listitem><para>Move src/interfaces/libpgeasy to http://gborg.postgresql.org (Marc, Bruce)</para></listitem>
@@ -5077,10 +5341,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Remove src/bin/pgaccess from main tree, now at http://www.pgaccess.org (Bruce)</para></listitem>
 <listitem><para>Add pg_on_connection_loss command to libpgtcl (Gerhard Hintermayer, Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Source Code</title>
+  <sect3>
+   <title>Source Code</title>
 <itemizedlist>
 <listitem><para>Fix for parallel make (Peter)</para></listitem>
 <listitem><para>AIX fixes for linking Tcl (Andreas Zeugswetter)</para></listitem>
@@ -5132,10 +5396,10 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Remove parameter wal_files because WAL files are now recycled (Bruce)</para></listitem>
 <listitem><para>Add version numbers to heap pages (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Contrib</title>
+  <sect3>
+   <title>Contrib</title>
 <itemizedlist>
 <listitem><para>Allow inet arrays in /contrib/array (Neil)</para></listitem>
 <listitem><para>GiST fixes (Teodor Sigaev, Neil)</para></listitem>
@@ -5159,34 +5423,34 @@ operations on bytea columns (Joe)</para></listitem>
 <listitem><para>Fixes to /contrib/cube (Bruno Wolff)</para></listitem>
 <listitem><para>Improve /contrib/fulltextindex (Christopher)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-2-8">
-   <title>Release 7.2.8</title>
+ <sect1 id="release-7-2-8">
+  <title>Release 7.2.8</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-05-09</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-05-09</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.2.7, including one
+   security-related issue.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.2.8</title>
 
    <para>
-    This release contains a variety of fixes from 7.2.7, including one
-    security-related issue.
+    A dump/restore is not required for those running 7.2.X.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.2.8</title>
-
-    <para>
-     A dump/restore is not required for those running 7.2.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair ancient race condition that allowed a transaction to be
@@ -5212,32 +5476,32 @@ month-related formats</para></listitem>
 (Marko Kreen)</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-2-7">
-   <title>Release 7.2.7</title>
+ <sect1 id="release-7-2-7">
+  <title>Release 7.2.7</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2005-01-31</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2005-01-31</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.2.6, including several
+   security-related issues.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.2.7</title>
 
    <para>
-    This release contains a variety of fixes from 7.2.6, including several
-    security-related issues.
+    A dump/restore is not required for those running 7.2.X.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.2.7</title>
-
-    <para>
-     A dump/restore is not required for those running 7.2.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Disallow <command>LOAD</> to non-superusers</para>
@@ -5260,32 +5524,32 @@ in case of nested merge joins could give outright wrong answers.
 datestyles</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-2-6">
-   <title>Release 7.2.6</title>
+ <sect1 id="release-7-2-6">
+  <title>Release 7.2.6</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-10-22</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-10-22</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.2.5.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.2.6</title>
 
    <para>
-    This release contains a variety of fixes from 7.2.5.
+    A dump/restore is not required for those running 7.2.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.2.6</title>
-
-    <para>
-     A dump/restore is not required for those running 7.2.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Repair possible failure to update hint bits on disk</para>
@@ -5311,32 +5575,32 @@ concern since there is no reason for non-developers to use this script anyway.
 <listitem><para>Update to newer versions of Bison</para></listitem>
 </itemizedlist>
 
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
-  <sect1 id="release-7-2-5">
-   <title>Release 7.2.5</title>
+ <sect1 id="release-7-2-5">
+  <title>Release 7.2.5</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2004-08-16</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2004-08-16</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from 7.2.4.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.2.5</title>
 
    <para>
-    This release contains a variety of fixes from 7.2.4.
+    A dump/restore is not required for those running 7.2.X.
    </para>
+  </sect2>
 
-
-   <sect2>
-    <title>Migration to version 7.2.5</title>
-
-    <para>
-     A dump/restore is not required for those running 7.2.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Prevent possible loss of committed transactions during crash</para>
@@ -5354,33 +5618,33 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Repair memory leaks in pg_dump</para></listitem>
 <listitem><para>Avoid conflict with system definition of <function>isblank()</function> function or macro</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
- <sect1 id="release-7-2-4">
-  <title>Release 7.2.4</title>
+<sect1 id="release-7-2-4">
+ <title>Release 7.2.4</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2003-01-30</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2003-01-30</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.2.3,
+  including fixes to prevent possible data loss.
+ </para>
+
+ <sect2>
+  <title>Migration to Version 7.2.4</title>
 
   <para>
-   This release contains a variety of fixes for version 7.2.3,
-   including fixes to prevent possible data loss.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.2.*.
   </para>
+ </sect2>
 
-  <sect2>
-   <title>Migration to version 7.2.4</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.2.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Fix some additional cases of VACUUM "No one parent tuple was found" error</para></listitem>
@@ -5392,34 +5656,34 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix integer overflows in circle_poly(), path_encode(), path_add()  (Neil)</para></listitem>
 <listitem><para>Repair long-standing logic errors in lseg_eq(), lseg_ne(), lseg_center()</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-2-3">
-  <title>Release 7.2.3</title>
+<sect1 id="release-7-2-3">
+ <title>Release 7.2.3</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-10-01</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-10-01</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.2.2,
+  including fixes to prevent possible data loss.
+ </para>
+
+ <sect2>
+  <title>Migration to Version 7.2.3</title>
 
   <para>
-   This release contains a variety of fixes for version 7.2.2,
-   including fixes to prevent possible data loss.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.2.*.
   </para>
+ </sect2>
 
-  <sect2>
-   <title>Migration to version 7.2.3</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.2.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Prevent possible compressed transaction log loss (Tom)</para></listitem>
@@ -5429,33 +5693,33 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Prevent spinlock hangs on SMP PPC machines (Tomoyuki Niijima)</para></listitem>
 <listitem><para>Fix <application>pg_dump</> to properly dump FULL JOIN USING (Tom)</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-2-2">
-  <title>Release 7.2.2</title>
+<sect1 id="release-7-2-2">
+ <title>Release 7.2.2</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-08-23</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-08-23</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.2.1.
+ </para>
+
+ <sect2>
+  <title>Migration to Version 7.2.2</title>
 
   <para>
-   This release contains a variety of fixes for version 7.2.1.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.2.*.
   </para>
+ </sect2>
 
-  <sect2>
-   <title>Migration to version 7.2.2</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.2.*.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
@@ -5472,33 +5736,33 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix for crash with long DATA strings (Thomas, Neil)</para></listitem>
 <listitem><para>Fix for repeat(), lpad(), rpad() and long strings (Neil)</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-2-1">
-  <title>Release 7.2.1</title>
+<sect1 id="release-7-2-1">
+ <title>Release 7.2.1</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-03-21</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-03-21</simpara>
+ </note>
+
+ <para>
+  This release contains a variety of fixes for version 7.2.
+ </para>
+
+ <sect2>
+  <title>Migration to Version 7.2.1</title>
 
   <para>
-   This release contains a variety of fixes for version 7.2.
+   A dump/restore is <emphasis>not</emphasis> required for those
+   running version 7.2.
   </para>
+ </sect2>
 
-  <sect2>
-   <title>Migration to version 7.2.1</title>
-
-   <para>
-    A dump/restore is <emphasis>not</emphasis> required for those
-    running version 7.2.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Changes</title>
 
 <itemizedlist>
 <listitem><para>Ensure that sequence counters do not go backwards after a crash (Tom)</para></listitem>
@@ -5518,183 +5782,183 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix for array subscripts handling (Tom)</para></listitem>
 <listitem><para>Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/pgSQL (Tom)</para></listitem>
 </itemizedlist>
-  </sect2>
- </sect1>
+ </sect2>
+</sect1>
 
 
- <sect1 id="release-7-2">
-  <title>Release 7.2</title>
+<sect1 id="release-7-2">
+ <title>Release 7.2</title>
 
-  <note>
-   <title>Release date</title>
-   <simpara>2002-02-04</simpara>
-  </note>
+ <note>
+  <title>Release date</title>
+  <simpara>2002-02-04</simpara>
+ </note>
 
-  <sect2>
-   <title>Overview</title>
+ <sect2>
+  <title>Overview</title>
 
-   <para>
-    This release improves <productname>PostgreSQL</> for use in
-    high-volume applications.
-   </para>
+  <para>
+   This release improves <productname>PostgreSQL</> for use in
+   high-volume applications.
+  </para>
 
-   <para>
-    Major changes in this release:
-   </para>
+  <para>
+   Major changes in this release:
+  </para>
 
-   <variablelist>
-    <varlistentry>
-     <term>VACUUM</term>
-     <listitem>
-      <para>
-       Vacuuming no longer locks tables, thus allowing normal user
-       access during the vacuum.  A new <command>VACUUM FULL</>
-       command does old-style vacuum by locking the table and
-       shrinking the on-disk copy of the table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Transactions</term>
-     <listitem>
-      <para>
-       There is no longer a problem with installations that exceed
-       four billion transactions.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>OIDs</term>
-     <listitem>
-      <para>
-       OIDs are now optional.  Users can now create tables without
-       OIDs for cases where OID usage is excessive.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Optimizer</term>
-     <listitem>
-      <para>
-       The system now computes histogram column statistics during
-       <command>ANALYZE</>, allowing much better optimizer choices.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Security</term>
-     <listitem>
-      <para>
-       A new MD5 encryption option allows more secure storage and
-       transfer of passwords.  A new Unix-domain socket
-       authentication option is available on Linux and BSD systems.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Statistics</term>
-     <listitem>
-      <para>
-       Administrators can use the new table access statistics module
-       to get fine-grained information about table and index usage.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>Internationalization</term>
-     <listitem>
-      <para>
-       Program and library messages can now be displayed in several
-       languages.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </sect2>
-
-  <sect2>
-   <title>Migration to version 7.2</title>
-
-   <para>
-    A dump/restore using <command>pg_dump</command> is required for
-    those wishing to migrate data from any previous release.
-   </para>
-
-   <para>
-    Observe the following incompatibilities:
-   </para>
-
-   <itemizedlist>
+  <variablelist>
+   <varlistentry>
+    <term>VACUUM</term>
     <listitem>
      <para>
-      The semantics of the <command>VACUUM</command> command have
-      changed in this release.  You might wish to update your
-      maintenance procedures accordingly.
+      Vacuuming no longer locks tables, thus allowing normal user
+      access during the vacuum.  A new <command>VACUUM FULL</>
+      command does old-style vacuum by locking the table and
+      shrinking the on-disk copy of the table.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Transactions</term>
     <listitem>
      <para>
-      In this release, comparisons using <literal>= NULL</literal>
-      will always return false (or NULL, more precisely).  Previous
-      releases automatically transformed this syntax to <literal>IS
-      NULL</literal>.  The old behavior can be re-enabled using a
-      <filename>postgresql.conf</filename> parameter.
+      There is no longer a problem with installations that exceed
+      four billion transactions.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>OIDs</term>
     <listitem>
      <para>
-      The <filename>pg_hba.conf</> and <filename>pg_ident.conf</>
-      configuration is now only reloaded after receiving a
-      <systemitem>SIGHUP</> signal, not with each connection.
+      OIDs are now optional.  Users can now create tables without
+      OIDs for cases where OID usage is excessive.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Optimizer</term>
     <listitem>
      <para>
-      The function <filename>octet_length()</> now returns the uncompressed data length.
+      The system now computes histogram column statistics during
+      <command>ANALYZE</>, allowing much better optimizer choices.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Security</term>
     <listitem>
      <para>
-      The date/time value <literal>'current'</literal> is no longer
-      available.  You will need to rewrite your applications.
+      A new MD5 encryption option allows more secure storage and
+      transfer of passwords.  A new Unix-domain socket
+      authentication option is available on Linux and BSD systems.
      </para>
     </listitem>
+   </varlistentry>
 
+   <varlistentry>
+    <term>Statistics</term>
     <listitem>
      <para>
-      The <literal>timestamp()</literal>, <literal>time()</literal>,
-      and <literal>interval()</literal> functions are no longer
-      available.  Instead of <literal>timestamp()</literal>, use
-      <literal>timestamp 'string'</literal> or <literal>CAST</literal>.
+      Administrators can use the new table access statistics module
+      to get fine-grained information about table and index usage.
      </para>
     </listitem>
+   </varlistentry>
 
-   </itemizedlist>
+   <varlistentry>
+    <term>Internationalization</term>
+    <listitem>
+     <para>
+      Program and library messages can now be displayed in several
+      languages.
+     </para>
+    </listitem>
+   </varlistentry>
 
-   <para>
-    The <literal>SELECT ... LIMIT #,#</literal> syntax will be removed
-    in the next release. You should change your queries to use
-    separate LIMIT and OFFSET clauses, e.g. <literal>LIMIT 10 OFFSET
-    20</literal>.
-   </para>
-  </sect2>
+  </variablelist>
+ </sect2>
 
-  <sect2>
-   <title>Changes</title>
+ <sect2>
+  <title>Migration to Version 7.2</title>
 
-   <sect3>
-    <title>Server Operation</title>
+  <para>
+   A dump/restore using <command>pg_dump</command> is required for
+   those wishing to migrate data from any previous release.
+  </para>
+
+  <para>
+   Observe the following incompatibilities:
+  </para>
+
+  <itemizedlist>
+   <listitem>
+    <para>
+     The semantics of the <command>VACUUM</command> command have
+     changed in this release.  You might wish to update your
+     maintenance procedures accordingly.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     In this release, comparisons using <literal>= NULL</literal>
+     will always return false (or NULL, more precisely).  Previous
+     releases automatically transformed this syntax to <literal>IS
+     NULL</literal>.  The old behavior can be re-enabled using a
+     <filename>postgresql.conf</filename> parameter.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The <filename>pg_hba.conf</> and <filename>pg_ident.conf</>
+     configuration is now only reloaded after receiving a
+     <systemitem>SIGHUP</> signal, not with each connection.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The function <filename>octet_length()</> now returns the uncompressed data length.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The date/time value <literal>'current'</literal> is no longer
+     available.  You will need to rewrite your applications.
+    </para>
+   </listitem>
+
+   <listitem>
+    <para>
+     The <literal>timestamp()</literal>, <literal>time()</literal>,
+     and <literal>interval()</literal> functions are no longer
+     available.  Instead of <literal>timestamp()</literal>, use
+     <literal>timestamp 'string'</literal> or <literal>CAST</literal>.
+    </para>
+   </listitem>
+
+  </itemizedlist>
+
+  <para>
+   The <literal>SELECT ... LIMIT #,#</literal> syntax will be removed
+   in the next release. You should change your queries to use
+   separate LIMIT and OFFSET clauses, e.g. <literal>LIMIT 10 OFFSET
+   20</literal>.
+  </para>
+ </sect2>
+
+ <sect2>
+  <title>Changes</title>
+
+  <sect3>
+   <title>Server Operation</title>
 <itemizedlist>
 <listitem><para>Create temporary files in a separate directory (Bruce)</para></listitem>
 <listitem><para>Delete orphaned temporary files on postmaster startup (Bruce)</para></listitem>
@@ -5717,10 +5981,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Superuser ID now fixed at 1 (Peter E)</para></listitem>
 <listitem><para>New pg_ctl "reload" option (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Performance</title>
+  <sect3>
+   <title>Performance</title>
 <itemizedlist>
 <listitem><para>Optimizer improvements (Tom)</para></listitem>
 <listitem><para>New histogram column statistics for optimizer (Tom)</para></listitem>
@@ -5733,10 +5997,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>R-tree performance improvements (Kenneth Been)</para></listitem>
 <listitem><para>B-tree splits more efficient (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Privileges</title>
+  <sect3>
+   <title>Privileges</title>
 <itemizedlist>
 <listitem><para>Change UPDATE, DELETE privileges to be distinct (Peter E)</para></listitem>
 <listitem><para>New REFERENCES, TRIGGER privileges (Peter E)</para></listitem>
@@ -5747,10 +6011,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix bug in privilege modifications on newly created tables (Tom)</para></listitem>
 <listitem><para>Disallow access to pg_statistic for non-superuser, add user-accessible views (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Client Authentication</title>
+  <sect3>
+   <title>Client Authentication</title>
 <itemizedlist>
 <listitem><para>Fork postmaster before doing authentication to prevent hangs (Peter E)</para></listitem>
 <listitem><para>Add ident authentication over Unix domain sockets on Linux, *BSD (Helge Bahmann, Oliver Elphick, Teodor Sigaev, Bruce)</para></listitem>
@@ -5759,10 +6023,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>PAM authentication (Dominic J. Eidson)</para></listitem>
 <listitem><para>Load pg_hba.conf and pg_ident.conf only on startup and SIGHUP (Bruce)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Server Configuration</title>
+  <sect3>
+   <title>Server Configuration</title>
 <itemizedlist>
 <listitem><para>Interpretation of some time zone abbreviations as Australian rather than North American now settable at run time (Bruce)</para></listitem>
 <listitem><para>New parameter to set default transaction isolation level (Peter E)</para></listitem>
@@ -5771,10 +6035,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>New parameter to set client authentication timeout (Tom)</para></listitem>
 <listitem><para>New parameter to set maximum number of open files (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Queries</title>
+  <sect3>
+   <title>Queries</title>
 <itemizedlist>
 <listitem><para>Statements added by INSERT rules now execute after the INSERT (Jan)</para></listitem>
 <listitem><para>Prevent unadorned relation names in target list (Bruce)</para></listitem>
@@ -5786,10 +6050,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix for LIMIT, DISTINCT ON pushed into subqueries (Tom)</para></listitem>
 <listitem><para>Fix nested EXCEPT/INTERSECT (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Schema Manipulation</title>
+  <sect3>
+   <title>Schema Manipulation</title>
 <itemizedlist>
 <listitem><para>Fix SERIAL in temporary tables (Bruce)</para></listitem>
 <listitem><para>Allow temporary sequences (Bruce)</para></listitem>
@@ -5809,10 +6073,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom)</para></listitem>
 <listitem><para>Enable partial indexes (Martijn van Oosterhout)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Utility Commands</title>
+  <sect3>
+   <title>Utility Commands</title>
 <itemizedlist>
 <listitem><para>Add RESET ALL, SHOW ALL (Marko Kreen)</para></listitem>
 <listitem><para>CREATE/ALTER USER/GROUP now allow options in any order (Vince)</para></listitem>
@@ -5825,10 +6089,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Fix privilege checks for CREATE INDEX (Tom)</para></listitem>
 <listitem><para>Disallow inappropriate use of CREATE/DROP INDEX/TRIGGER/VIEW (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Data Types and Functions</title>
+  <sect3>
+   <title>Data Types and Functions</title>
 <itemizedlist>
 <listitem><para>SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom)</para></listitem>
 <listitem><para>Add convert(), convert2() (Tatsuo)</para></listitem>
@@ -5868,10 +6132,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Some datatype() function calls now evaluated differently</para></listitem>
 <listitem><para>Add support for Julian and ISO time specifications (Thomas)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Internationalization</title>
+  <sect3>
+   <title>Internationalization</title>
 <itemizedlist>
 <listitem><para>National language support in psql, <application>pg_dump</>, libpq, and server (Peter E)</para></listitem>
 <listitem><para>Message translations in Chinese (simplified, traditional), Czech, French, German, Hungarian, Russian, Swedish (Peter E, Serguei A. Mokhov, Karel Zak, Weiping He, Zhenbang Wei, Kovacs Zoltan)</para></listitem>
@@ -5882,10 +6146,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Make mic2ascii() non-ASCII aware (Tatsuo)</para></listitem>
 <listitem><para>Reject invalid multibyte character sequences (Tatsuo)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title><application>PL/pgSQL</></title>
+  <sect3>
+   <title><application>PL/pgSQL</></title>
 <itemizedlist>
 <listitem><para>Now uses portals for SELECT loops, allowing huge result sets (Jan)</para></listitem>
 <listitem><para>CURSOR and REFCURSOR support (Jan)</para></listitem>
@@ -5899,33 +6163,33 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Memory leak fix (Jan, Tom)</para></listitem>
 <listitem><para>Make trailing semicolon optional (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>PL/Perl</title>
+  <sect3>
+   <title>PL/Perl</title>
 <itemizedlist>
 <listitem><para>New untrusted PL/Perl (Alex Pilosov)</para></listitem>
 <listitem><para>PL/Perl is now built on some platforms even if libperl is not shared (Peter E)</para></listitem>
 </itemizedlist>
-    </sect3>
+   </sect3>
 
-   <sect3>
-    <title>PL/Tcl</title>
+  <sect3>
+   <title>PL/Tcl</title>
 <itemizedlist>
 <listitem><para>Now reports errorInfo (Vsevolod Lobko)</para></listitem>
 <listitem><para>Add spi_lastoid function (bob@redivi.com)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>PL/Python</title>
+  <sect3>
+   <title>PL/Python</title>
 <itemizedlist>
 <listitem><para>...is new (Andrew Bosma)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title><application>psql</></title>
+  <sect3>
+   <title><application>psql</></title>
 <itemizedlist>
 <listitem><para>\d displays indexes in unique, primary groupings (Christopher Kings-Lynne)</para></listitem>
 <listitem><para>Allow trailing semicolons in backslash commands (Greg Sabino Mullane)</para></listitem>
@@ -5933,18 +6197,18 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Force new password prompt when changing user and database (Tatsuo, Tom)</para></listitem>
 <listitem><para>Format the correct number of columns for Unicode (Patrice)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title><application>libpq</></title>
+  <sect3>
+   <title><application>libpq</></title>
 <itemizedlist>
 <listitem><para>New function PQescapeString() to escape quotes in command strings (Florian Weimer)</para></listitem>
 <listitem><para>New function PQescapeBytea() escapes binary strings for use as SQL string literals</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>JDBC</title>
+  <sect3>
+   <title>JDBC</title>
 <itemizedlist>
 <listitem><para>Return OID of INSERT (Ken K)</para></listitem>
 <listitem><para>Handle more data types (Ken K)</para></listitem>
@@ -5979,10 +6243,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>MD5 password encryption support (Jeremy Wohl)</para></listitem>
 <listitem><para>Fix to actually use type cache (Ned Wolpert)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>ODBC</title>
+  <sect3>
+   <title>ODBC</title>
 <itemizedlist>
 <listitem><para>Remove query size limit (Hiroshi)</para></listitem>
 <listitem><para>Remove text field size limit (Hiroshi)</para></listitem>
@@ -5995,10 +6259,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>MD5 password encryption support (Bruce)</para></listitem>
 <listitem><para>Add more compatibility functions to odbc.sql (Peter E)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title><application>ECPG</></title>
+  <sect3>
+   <title><application>ECPG</></title>
 <itemizedlist>
 <listitem><para>EXECUTE ... INTO implemented (Christof Petig)</para></listitem>
 <listitem><para>Multiple row descriptor support (e.g. CARDINALITY) (Christof Petig)</para></listitem>
@@ -6011,10 +6275,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>All function names with external linkage are now prefixed by ECPG</para></listitem>
 <listitem><para>Fixes for arrays of structures (Michael)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Misc. Interfaces</title>
+  <sect3>
+   <title>Misc. Interfaces</title>
 <itemizedlist>
 <listitem><para>Python fix fetchone() (Gerhard Haring)</para></listitem>
 <listitem><para>Use UTF, Unicode in Tcl where appropriate (Vsevolod Lobko, Reinhard Max)</para></listitem>
@@ -6022,10 +6286,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Prevent output of default index op class in <application>pg_dump</> (Tom)</para></listitem>
 <listitem><para>Fix libpgeasy memory leak (Bruce)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Build and Install</title>
+  <sect3>
+   <title>Build and Install</title>
 <itemizedlist>
 <listitem><para>Configure, dynamic loader, and shared library fixes (Peter E)</para></listitem>
 <listitem><para>Fixes in QNX 4 port (Bernd Tegge)</para></listitem>
@@ -6040,10 +6304,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Rename config.h to pg_config.h (Peter E)</para></listitem>
 <listitem><para>Reorganize installation layout of header files (Peter E)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Source Code</title>
+  <sect3>
+   <title>Source Code</title>
 <itemizedlist>
 <listitem><para>Remove SEP_CHAR (Bruce)</para></listitem>
 <listitem><para>New GUC hooks (Tom)</para></listitem>
@@ -6057,10 +6321,10 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>Add 'volatile' usage in spinlock structures</para></listitem>
 <listitem><para>Improve signal handling logic (Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
 
-   <sect3>
-    <title>Contrib</title>
+  <sect3>
+   <title>Contrib</title>
 <itemizedlist>
 <listitem><para>New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev)</para></listitem>
 <listitem><para>New contrib/tsearch full-text indexing (Oleg, Teodor Sigaev)</para></listitem>
@@ -6073,33 +6337,33 @@ since <productname>PostgreSQL</productname> 7.1.
 <listitem><para>New pg_upgrade utility (Bruce)</para></listitem>
 <listitem><para>Add new pg_resetxlog options (Bruce, Tom)</para></listitem>
 </itemizedlist>
-   </sect3>
+  </sect3>
+ </sect2>
+</sect1>
+
+
+ <sect1 id="release-7-1-3">
+  <title>Release 7.1.3</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2001-08-15</simpara>
+  </note>
+
+  <sect2>
+   <title>Migration to Version 7.1.3</title>
+
+   <para>
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.1.X.
+   </para>
   </sect2>
- </sect1>
 
+  <sect2>
+   <title>Changes</title>
 
-  <sect1 id="release-7-1-3">
-   <title>Release 7.1.3</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2001-08-15</simpara>
-   </note>
-
-   <sect2>
-    <title>Migration to version 7.1.3</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.1.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Remove unused WAL segments of large transactions (Tom)
 Multiaction rule fix (Tom)
 PL/pgSQL memory allocation fix (Jan)
@@ -6110,77 +6374,77 @@ Fix subselects with DISTINCT ON or LIMIT (Tom)
 BeOS fix
 Disable COPY TO/FROM a view (Tom)
 Cygwin build (Jason Tishler)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-7-1-2">
-   <title>Release 7.1.2</title>
+ <sect1 id="release-7-1-2">
+  <title>Release 7.1.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2001-05-11</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2001-05-11</simpara>
+  </note>
+
+  <para>
+   This has one fix from 7.1.1.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.1.2</title>
 
    <para>
-    This has one fix from 7.1.1.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.1.X.
    </para>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 7.1.2</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.1.X.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Fix PL/pgSQL SELECTs when returning no rows
 Fix for psql backslash core dump
 Referential integrity privilege fix
 Optimizer fixes
 pg_dump cleanups
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-7-1-1">
-   <title>Release 7.1.1</title>
+ <sect1 id="release-7-1-1">
+  <title>Release 7.1.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2001-05-05</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2001-05-05</simpara>
+  </note>
+
+  <para>
+   This has a variety of fixes from 7.1.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.1.1</title>
 
    <para>
-    This has a variety of fixes from 7.1.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.1.
    </para>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 7.1.1</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.1.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Fix for numeric MODULO operator (Tom)
 pg_dump fixes (Philip)
 pg_dump can dump 7.0 databases (Philip)
@@ -6195,119 +6459,119 @@ Fix for pg_ctl and option strings with spaces (Peter E)
 ODBC fixes (Hiroshi)
 EXTRACT can now take string argument (Thomas)
 Python fixes (Darcy)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
-
-
-  <sect1 id="release-7-1">
-   <title>Release 7.1</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>2001-04-13</simpara>
-   </note>
-
-   <para>
-        This release focuses on removing limitations that have existed in the
-        <productname>PostgreSQL</productname> code for many years.
+    </programlisting>
    </para>
+  </sect2>
+ </sect1>
 
-   <para>
-    Major changes in this release:
-   </para>
 
-   <variablelist>
-    <varlistentry>
-     <term>
-       Write-ahead Log (WAL)
-     </term>
-     <listitem>
-      <para>
+ <sect1 id="release-7-1">
+  <title>Release 7.1</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>2001-04-13</simpara>
+  </note>
+
+  <para>
+       This release focuses on removing limitations that have existed in the
+       <productname>PostgreSQL</productname> code for many years.
+  </para>
+
+  <para>
+   Major changes in this release:
+  </para>
+
+  <variablelist>
+   <varlistentry>
+    <term>
+      Write-ahead Log (WAL)
+    </term>
+    <listitem>
+     <para>
 To maintain database consistency in case of an operating system crash,
 previous releases of <productname>PostgreSQL</productname> have forced
 all data modifications to disk before each transaction commit.  With
 WAL, only one log file must be flushed to disk, greatly improving
 performance.  If you have been using -F in previous releases to
 disable disk flushes, you might want to consider discontinuing its use.
-      </para>
-     </listitem>
-    </varlistentry>
+     </para>
+    </listitem>
+   </varlistentry>
 
-    <varlistentry>
-     <term>
-       TOAST
-     </term>
-     <listitem>
-      <para>
-       TOAST - Previous releases had a compiled-in row length limit,
+   <varlistentry>
+    <term>
+      TOAST
+    </term>
+    <listitem>
+     <para>
+      TOAST - Previous releases had a compiled-in row length limit,
 typically 8k - 32k. This limit made storage of long text fields
 difficult.  With TOAST, long rows of any length can be stored with good
 performance.
-      </para>
-     </listitem>
-    </varlistentry>
+     </para>
+    </listitem>
+   </varlistentry>
 
-    <varlistentry>
-     <term>
-       Outer Joins
-     </term>
-     <listitem>
-      <para>
+   <varlistentry>
+    <term>
+      Outer Joins
+    </term>
+    <listitem>
+     <para>
 We now support outer joins.  The UNION/NOT IN
 workaround for outer joins is no longer required.  We use the SQL92
 outer join syntax.
-      </para>
-     </listitem>
-    </varlistentry>
+     </para>
+    </listitem>
+   </varlistentry>
 
-    <varlistentry>
-     <term>
-       Function Manager
-     </term>
-     <listitem>
-      <para>
+   <varlistentry>
+    <term>
+      Function Manager
+    </term>
+    <listitem>
+     <para>
 The previous C function manager did not
 handle null values properly, nor did it support 64-bit <acronym>CPU</acronym>'s (Alpha).  The new
 function manager does.  You can continue using your old custom
 functions, but you might want to rewrite them in the future to use the new
 function manager call interface.
-      </para>
-     </listitem>
-    </varlistentry>
+     </para>
+    </listitem>
+   </varlistentry>
 
-    <varlistentry>
-     <term>
-       Complex Queries
-     </term>
-     <listitem>
-      <para>
+   <varlistentry>
+    <term>
+      Complex Queries
+    </term>
+    <listitem>
+     <para>
 A large number of complex queries that were
 unsupported in previous releases now work.  Many combinations of views,
 aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables
 now work properly. Inherited tables are now accessed by default.
 Subqueries in FROM are now supported.
-      </para>
-     </listitem>
-    </varlistentry>
+     </para>
+    </listitem>
+   </varlistentry>
 
-   </variablelist>
+  </variablelist>
 
-   <sect2>
-    <title>Migration to version 7.1</title>
+  <sect2>
+   <title>Migration to Version 7.1</title>
 
-    <para>
-        A dump/restore using pg_dump is required for those wishing to migrate
-        data from any previous release.
-    </para>
-   </sect2>
+   <para>
+       A dump/restore using pg_dump is required for those wishing to migrate
+       data from any previous release.
+   </para>
+  </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 Many multibyte/Unicode/locale fixes (Tatsuo and others)
@@ -6317,7 +6581,7 @@ Fix for INSERT INTO...SELECT where targetlist has subqueries (Tom)
 Prompt username/password on standard error (Bruce)
 Large objects inv_read/inv_write fixes (Tom)
 Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel,
-    Daniel Baldoni)
+   Daniel Baldoni)
 Prevent query expressions from leaking memory (Tom)
 Allow UPDATE of arrays elements (Tom)
 Wake up lock waiters during cancel (Hiroshi)
@@ -6333,7 +6597,7 @@ Allow PL/pgSQL accept non-ASCII identifiers (Tatsuo)
 Allow views to proper handle GROUP BY, aggregates, DISTINCT (Tom)
 Fix rare failure with TRUNCATE command (Tom)
 Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views,
-    DISTINCT, ORDER BY, SELECT...INTO (Tom)
+   DISTINCT, ORDER BY, SELECT...INTO (Tom)
 Fix parser failures during aborted transactions (Tom)
 Allow temporary relations to properly clean up indexes (Bruce)
 Fix VACUUM problem with moving rows in same page (Tom)
@@ -6367,16 +6631,16 @@ Improve CLUSTER (Tom)
 Improve ps status display for more platforms (Peter E, Marc)
 Improve CREATE FUNCTION failure message (Ross)
 JDBC improvements (Peter, Travis Bauer, Christopher Cain, William Webber,
-    Gunnar)
+   Gunnar)
 Grand Unified Configuration scheme/GUC.  Many options can now be set in
-    data/postgresql.conf, postmaster/postgres flags, or SET commands (Peter E)
+   data/postgresql.conf, postmaster/postgres flags, or SET commands (Peter E)
 Improved handling of file descriptor cache (Tom)
 New warning code about auto-created table alias entries (Bruce)
 Overhaul initdb process (Tom, Peter E)
 Overhaul of inherited tables; inherited tables now accessed by default;
-   new ONLY key word prevents it (Chris Bitmead, Tom)
+  new ONLY key word prevents it (Chris Bitmead, Tom)
 ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs,
-    Michael Fork)
+   Michael Fork)
 Allow renaming of temp tables (Tom)
 Overhaul memory manager contexts (Tom)
 pg_dumpall uses CREATE USER or CREATE GROUP rather using COPY (Peter E)
@@ -6401,7 +6665,7 @@ Allow functional indexes to use binary-compatible type (Tom)
 Allow SQL functions to be used in more contexts (Tom)
 New pg_config utility (Peter E)
 New PL/pgSQL EXECUTE command which allows dynamic SQL and utility statements
-    (Jan)
+   (Jan)
 New PL/pgSQL GET DIAGNOSTICS statement for SPI value access (Jan)
 New quote_identifiers() and quote_literal() functions (Jan)
 New ALTER TABLE table OWNER TO user command (Mark Hollomon)
@@ -6420,7 +6684,7 @@ New AT TIME ZONE syntax (Thomas)
 Allow location of Unix domain socket to be configurable (David J. MacKenzie)
 Allow postmaster to listen on a specific IP address (David J. MacKenzie)
 Allow socket path name to be specified in hostname by using leading slash
-    (David J. MacKenzie)
+   (David J. MacKenzie)
 Allow CREATE DATABASE to specify template database (Tom)
 New utility to convert MySQL schema dumps to SQL92 and PostgreSQL (Thomas)
 New /contrib/rserv replication toolkit (Vadim)
@@ -6447,7 +6711,7 @@ New CIDR abbrev() function (Tom)
 Performance
 -----------
 Write-Ahead Log (WAL) to provide crash recovery with less performance
-    overhead (Vadim)
+   overhead (Vadim)
 ANALYZE stage of VACUUM no longer exclusively locks table (Bruce)
 Reduced file seeks (Denis Perchine)
 Improve BTREE code for duplicate keys (Tom)
@@ -6493,39 +6757,39 @@ New contrib/pg_logger
 New --template option to createdb
 New contrib/pg_control utility (Oliver)
 New FreeBSD tools ipc_check, start-scripts/freebsd
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-7-0-3">
-   <title>Release 7.0.3</title>
+ <sect1 id="release-7-0-3">
+  <title>Release 7.0.3</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2000-11-11</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2000-11-11</simpara>
+  </note>
+
+  <para>
+   This has a variety of fixes from 7.0.2.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.0.3</title>
 
    <para>
-    This has a variety of fixes from 7.0.2.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.0.*.
    </para>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 7.0.3</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.0.*.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Jdbc fixes (Peter)
 Large object fix (Tom)
 Fix lean in COPY WITH OIDS leak (Tom)
@@ -6541,11 +6805,11 @@ Fix for memory allocation problem in user authentication code (Tom)
 Remove bogus use of int4out() (Tom)
 Fixes for multiple subqueries in COALESCE or BETWEEN (Tom)
 Fix for failure of triggers on heap open in certain cases (Jeroen van
-    Vianen)
+   Vianen)
 Fix for erroneous selectivity of not-equals (Tom)
 Fix for erroneous use of strcmp() (Tom)
 Fix for bug where storage manager accesses items beyond end of file
-    (Tom)
+   (Tom)
 Fix to include kernel errno message in all smgr elog messages (Tom)
 Fix for '.' not in PATH at build time (SL Baur)
 Fix for out-of-file-descriptors error (Tom)
@@ -6556,81 +6820,81 @@ Fix TRUNCATE failure on relations with indexes (Tom)
 Avoid database-wide restart on write error (Hiroshi)
 Fix nodeMaterial to honor chgParam by recomputing its output (Tom)
 Fix VACUUM problem with moving chain of update row versions when source
-    and destination of a row version lie on the same page (Tom)
+   and destination of a row version lie on the same page (Tom)
 Fix user.c CommandCounterIncrement (Tom)
 Fix for AM/PM boundary problem in to_char() (Karel Zak)
 Fix TIME aggregate handling (Tom)
 Fix to_char() to avoid coredump on NULL input (Tom)
 Buffer fix (Tom)
 Fix for inserting/copying longer multibyte strings into char() data
-    types (Tatsuo)
+   types (Tatsuo)
 Fix for crash of backend, on abort (Tom)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-7-0-2">
-   <title>Release 7.0.2</title>
+ <sect1 id="release-7-0-2">
+  <title>Release 7.0.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2000-06-05</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2000-06-05</simpara>
+  </note>
+
+  <para>
+   This is a repackaging of 7.0.1 with added documentation.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 7.0.2</title>
 
    <para>
-    This is a repackaging of 7.0.1 with added documentation.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.*.
    </para>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 7.0.2</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.*.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Added documentation to tarball.
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-7-0-1">
-   <title>Release 7.0.1</title>
+ <sect1 id="release-7-0-1">
+  <title>Release 7.0.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2000-06-01</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2000-06-01</simpara>
+  </note>
+
+  <para>
+   This is a cleanup release for 7.0.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 7.0.1</title>
 
    <para>
-    This is a cleanup release for 7.0.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    7.0.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 7.0.1</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.0.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Fix many CLUSTER failures (Tom)
 Allow ALTER TABLE RENAME works on indexes (Tom)
 Fix plpgsql to handle datetime-&gt;timestamp and timespan-&gt;interval (Bruce)
@@ -6653,160 +6917,160 @@ Copy pg_ident.conf.sample into /lib directory in install (Bruce)
 Add SJIS UDC (NEC selection IBM kanji) support (Eiji Tokuya)
 Fix too long syslog message (Tatsuo)
 Fix problem with quoted indexes that are too long (Tom)
-JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
+JDBC ResultSet.getTimestamp() fix (Gregory Krasnow &amp; Floyd Marinescu)
 ecpg changes (Michael)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-7-0">
-   <title>Release 7.0</title>
+ <sect1 id="release-7-0">
+  <title>Release 7.0</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>2000-05-08</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>2000-05-08</simpara>
+  </note>
+
+  <para>
+   This release contains improvements in many areas, demonstrating
+   the continued growth of <productname>PostgreSQL</productname>.
+   There are more improvements and fixes in 7.0 than in any previous
+   release. The developers have confidence that this is the best
+   release yet; we do our best to put out only solid releases, and
+   this one is no exception.
+  </para>
+
+  <para>
+   Major changes in this release:
+  </para>
+
+  <variablelist>
+   <varlistentry>
+    <term>
+     Foreign Keys
+    </term>
+    <listitem>
+     <para>
+      Foreign keys are now implemented, with the exception of PARTIAL MATCH
+      foreign keys. Many users have been asking for this feature, and we are
+      pleased to offer it.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Optimizer Overhaul
+    </term>
+    <listitem>
+     <para>
+      Continuing on work started a year ago, the optimizer has been
+      improved, allowing better query plan selection and faster performance
+      with less memory usage.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Updated <application>psql</application>
+    </term>
+    <listitem>
+     <para>
+      <application>psql</application>, our interactive terminal monitor, has been
+      updated with a variety of new features. See the <application>psql</application> manual page for details.
+     </para>
+    </listitem>
+   </varlistentry>
+
+   <varlistentry>
+    <term>
+     Join Syntax
+    </term>
+    <listitem>
+     <para>
+      SQL92 join syntax is now supported, though only as
+      <literal>INNER JOIN</> for this release. <literal>JOIN</>,
+      <literal>NATURAL JOIN</>, <literal>JOIN</>/<literal>USING</>,
+      and <literal>JOIN</>/<literal>ON</> are available, as are
+      column correlation names.
+     </para>
+    </listitem>
+
+   </varlistentry>
+  </variablelist>
+
+  <sect2>
+   <title>Migration to Version 7.0</title>
 
    <para>
-    This release contains improvements in many areas, demonstrating
-    the continued growth of <productname>PostgreSQL</productname>.
-    There are more improvements and fixes in 7.0 than in any previous
-    release. The developers have confidence that this is the best
-    release yet; we do our best to put out only solid releases, and
-    this one is no exception.
+    A dump/restore using <application>pg_dump</application>
+    is required for those wishing to migrate data from any
+    previous release of <productname>PostgreSQL</productname>.
+    For those upgrading from 6.5.*, you can instead use
+    <application>pg_upgrade</application> to upgrade to this
+    release; however, a full dump/reload installation is always the
+    most robust method for upgrades.
    </para>
 
    <para>
-    Major changes in this release:
+    Interface and compatibility issues to consider for the new
+    release include:
    </para>
 
-   <variablelist>
-    <varlistentry>
-     <term>
-      Foreign Keys
-     </term>
-     <listitem>
-      <para>
-       Foreign keys are now implemented, with the exception of PARTIAL MATCH
-       foreign keys. Many users have been asking for this feature, and we are
-       pleased to offer it.
-      </para>
-     </listitem>
-    </varlistentry>
+   <itemizedlist>
+    <listitem>
+     <para>
+      The date/time types <type>datetime</type> and
+      <type>timespan</type> have been superseded by the
+      SQL92-defined types <type>timestamp</type> and
+      <type>interval</type>. Although there has been some effort to
+      ease the transition by allowing
+      <productname>PostgreSQL</productname> to recognize
+      the deprecated type names and translate them to the new type
+      names, this mechanism cannot be completely transparent to
+      your existing application.
+     </para>
+    </listitem>
 
-    <varlistentry>
-     <term>
-      Optimizer Overhaul
-     </term>
-     <listitem>
-      <para>
-       Continuing on work started a year ago, the optimizer has been
-       improved, allowing better query plan selection and faster performance
-       with less memory usage.
-      </para>
-     </listitem>
-    </varlistentry>
+    <listitem>
+     <para>
+      The optimizer has been substantially improved in the area of
+      query cost estimation. In some cases, this will result in
+      decreased query times as the optimizer makes a better choice
+      for the preferred plan. However, in a small number of cases,
+      usually involving pathological distributions of data, your
+      query times might go up. If you are dealing with large amounts
+      of data, you might want to check your queries to verify
+      performance.
+     </para>
+    </listitem>
 
-    <varlistentry>
-     <term>
-      Updated <application>psql</application>
-     </term>
-     <listitem>
-      <para>
-       <application>psql</application>, our interactive terminal monitor, has been
-       updated with a variety of new features. See the <application>psql</application> manual page for details.
-      </para>
-     </listitem>
-    </varlistentry>
+    <listitem>
+     <para>
+      The <acronym>JDBC</acronym> and <acronym>ODBC</acronym>
+      interfaces have been upgraded and extended.
+     </para>
+    </listitem>
 
-    <varlistentry>
-     <term>
-      Join Syntax
-     </term>
-     <listitem>
-      <para>
-       SQL92 join syntax is now supported, though only as
-       <literal>INNER JOIN</> for this release. <literal>JOIN</>,
-       <literal>NATURAL JOIN</>, <literal>JOIN</>/<literal>USING</>,
-       and <literal>JOIN</>/<literal>ON</> are available, as are
-       column correlation names.
-      </para>
-     </listitem>
+    <listitem>
+     <para>
+      The string function <function>CHAR_LENGTH</function> is now a
+      native function. Previous versions translated this into a call
+      to <function>LENGTH</function>, which could result in
+      ambiguity with other types implementing
+      <function>LENGTH</function> such as the geometric types.
+     </para>
+    </listitem>
+   </itemizedlist>
+  </sect2>
 
-    </varlistentry>
-   </variablelist>
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 7.0</title>
-
-    <para>
-     A dump/restore using <application>pg_dump</application>
-     is required for those wishing to migrate data from any
-     previous release of <productname>PostgreSQL</productname>.
-     For those upgrading from 6.5.*, you can instead use
-     <application>pg_upgrade</application> to upgrade to this
-     release; however, a full dump/reload installation is always the
-     most robust method for upgrades.
-    </para>
-
-    <para>
-     Interface and compatibility issues to consider for the new
-     release include:
-    </para>
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The date/time types <type>datetime</type> and
-       <type>timespan</type> have been superseded by the
-       SQL92-defined types <type>timestamp</type> and
-       <type>interval</type>. Although there has been some effort to
-       ease the transition by allowing
-       <productname>PostgreSQL</productname> to recognize
-       the deprecated type names and translate them to the new type
-       names, this mechanism cannot be completely transparent to
-       your existing application.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The optimizer has been substantially improved in the area of
-       query cost estimation. In some cases, this will result in
-       decreased query times as the optimizer makes a better choice
-       for the preferred plan. However, in a small number of cases,
-       usually involving pathological distributions of data, your
-       query times might go up. If you are dealing with large amounts
-       of data, you might want to check your queries to verify
-       performance.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <acronym>JDBC</acronym> and <acronym>ODBC</acronym>
-       interfaces have been upgraded and extended.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The string function <function>CHAR_LENGTH</function> is now a
-       native function. Previous versions translated this into a call
-       to <function>LENGTH</function>, which could result in
-       ambiguity with other types implementing
-       <function>LENGTH</function> such as the geometric types.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 Prevent function calls exceeding maximum number of arguments (Tom)
@@ -6922,8 +7186,8 @@ Added psql LASTOID variable to return last inserted oid (Peter E)
 Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom)
 Add privilege check for vacuum (Peter E)
 New libpq functions to allow asynchronous connections: PQconnectStart(),
-   PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(),
-   PQsetenvPoll(), PQsetenvAbort (Ewan Mellor)
+  PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(),
+  PQsetenvPoll(), PQsetenvAbort (Ewan Mellor)
 New libpq PQsetenv() function (Ewan Mellor)
 create/alter user extension (Peter E)
 New postmaster.pid and postmaster.opts under $PGDATA (Tatsuo)
@@ -6941,7 +7205,7 @@ All administration scripts now support --long options (Peter E, Karel)
 Vacuumdb script now supports --all option (Peter E)
 ecpg new portable FETCH syntax
 Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF
-        and EXEC SQL ENDIF directives
+       and EXEC SQL ENDIF directives
 Add pg_ctl script to control backend start-up (Tatsuo)
 Add postmaster.opts.default file to store start-up flags (Tatsuo)
 Allow --with-mb=SQL_ASCII
@@ -6963,7 +7227,7 @@ Allow COPY IN to read file that do not end with a newline (Tom)
 Indicate when long identifiers are truncated (Tom)
 Allow aggregates to use type equivalency (Peter E)
 Add Oracle's to_char(), to_date(), to_datetime(), to_timestamp(), to_number()
-        conversion functions (Karel Zak &lt;zakkr@zf.jcu.cz&gt;)
+       conversion functions (Karel Zak &lt;zakkr@zf.jcu.cz&gt;)
 Add SELECT DISTINCT ON (expr [, expr ...]) targetlist ... (Tom)
 Check to be sure ORDER BY is compatible with the DISTINCT operation (Tom)
 Add NUMERIC and int8 types to ODBC
@@ -7124,75 +7388,75 @@ NT fixes
 NetBSD fixes (Johnny C. Lam <email>lamj@stat.cmu.edu</email>)
 Fixes for Alpha compiles
 New multibyte encodings
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-6-5-3">
-   <title>Release 6.5.3</title>
+ <sect1 id="release-6-5-3">
+  <title>Release 6.5.3</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1999-10-13</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1999-10-13</simpara>
+  </note>
+
+  <para>
+   This is basically a cleanup release for 6.5.2.  We have added a new
+   <application>PgAccess</> that was missing in 6.5.2, and installed an NT-specific fix.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 6.5.3</title>
 
    <para>
-    This is basically a cleanup release for 6.5.2.  We have added a new
-    <application>PgAccess</> that was missing in 6.5.2, and installed an NT-specific fix.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    6.5.*.
    </para>
+  </sect2>
+  <sect2>
+   <title>Changes</title>
 
-
-   <sect2>
-    <title>Migration to version 6.5.3</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     6.5.*.
-    </para>
-   </sect2>
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Updated version of pgaccess 0.98
 NT-specific patch
 Fix dumping rules on inherited tables
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
-  <sect1 id="release-6-5-2">
-   <title>Release 6.5.2</title>
+ <sect1 id="release-6-5-2">
+  <title>Release 6.5.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1999-09-15</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1999-09-15</simpara>
+  </note>
+
+  <para>
+   This is basically a cleanup release for 6.5.1.  We have fixed a variety of
+   problems reported by 6.5.1 users.
+  </para>
+
+
+  <sect2>
+   <title>Migration to Version 6.5.2</title>
 
    <para>
-    This is basically a cleanup release for 6.5.1.  We have fixed a variety of
-    problems reported by 6.5.1 users.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    6.5.*.
    </para>
+  </sect2>
 
+  <sect2>
+   <title>Changes</title>
 
-   <sect2>
-    <title>Migration to version 6.5.2</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     6.5.*.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 subselect+CASE fixes(Tom)
 Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren Sefcik)
 Fixes for CASE in WHERE join clauses(Tom)
@@ -7214,41 +7478,41 @@ Fix for unary operators in rule deparser(Tom)
 Comment out FileUnlink of excess segments during mdtruncate()(Tom)
 IRIX linking fix from Yu Cao &gt;yucao@falcon.kla-tencor.com&lt;
 Repair logic error in LIKE: should not return LIKE_ABORT
-   when reach end of pattern before end of text(Tom)
+  when reach end of pattern before end of text(Tom)
 Repair incorrect cleanup of heap memory allocation during transaction abort(Tom)
 Updated version of pgaccess 0.98
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-6-5-1">
-   <title>Release 6.5.1</title>
+ <sect1 id="release-6-5-1">
+  <title>Release 6.5.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1999-07-15</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1999-07-15</simpara>
+  </note>
+
+  <para>
+   This is basically a cleanup release for 6.5.  We have fixed a variety of
+   problems reported by 6.5 users.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 6.5.1</title>
 
    <para>
-    This is basically a cleanup release for 6.5.  We have fixed a variety of
-    problems reported by 6.5 users.
+    A dump/restore is <emphasis>not</emphasis> required for those running
+    6.5.
    </para>
+  </sect2>
 
-   <sect2>
-    <title>Migration to version 6.5.1</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     6.5.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Add NT README file
 Portability fixes for linux_ppc, IRIX, linux_alpha, OpenBSD, alpha
 Remove QUERY_LIMIT, use SELECT...LIMIT
@@ -7272,244 +7536,244 @@ Shared library dependencies fixed (Tom)
 Fixed glitches affecting GROUP BY in subselects(Tom)
 Fix some compiler warnings (Tomoaki Nishiyama)
 Add Win1250 (Czech) support (Pavel Behal)
-     </programlisting>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
+
+ <sect1 id="release-6-5">
+  <title>Release 6.5</title>
+
+  <note>
+  <title>Release date</title>
+  <simpara>1999-06-09</simpara>
+  </note>
+
+  <para>
+   This release marks a major step in the development team's mastery of the source
+   code we inherited from Berkeley.  You will see we are now easily adding
+   major features, thanks to the increasing size and experience of our
+   world-wide development team.
+  </para>
+
+  <para>
+   Here is a brief summary of the more notable changes:
+
+   <variablelist>
+    <varlistentry>
+     <term>
+      Multiversion concurrency control(MVCC)
+     </term>
+     <listitem>
+      <para>
+       This removes our old table-level locking, and replaces it with
+       a locking system that is superior to most commercial database
+       systems.  In a traditional system, each row that is modified
+       is locked until committed, preventing reads by other users.
+       MVCC uses the natural multiversion nature of
+       <productname>PostgreSQL</productname> to allow readers to
+       continue reading consistent data during writer activity.
+       Writers continue to use the compact pg_log transaction system.
+       This is all performed without having to allocate a lock for
+       every row like traditional database systems.  So, basically,
+       we no longer are restricted by simple table-level locking; we
+       have something better than row-level locking.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Hot backups from <application>pg_dump</application>
+     </term>
+     <listitem>
+      <para>
+       <application>pg_dump</application> takes advantage of the new
+       MVCC features to give a consistent database dump/backup while
+       the database stays online and available for queries.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Numeric data type
+     </term>
+     <listitem>
+      <para>
+       We now have a true numeric data type, with
+       user-specified precision.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Temporary tables
+     </term>
+     <listitem>
+      <para>
+       Temporary tables are guaranteed to have unique names
+       within a database session, and are destroyed on session exit.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      New SQL features
+     </term>
+     <listitem>
+      <para>
+       We now have CASE, INTERSECT, and EXCEPT statement
+       support.  We have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL,
+       SELECT ... FOR UPDATE, and an improved LOCK TABLE command.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Speedups
+     </term>
+     <listitem>
+      <para>
+       We continue to speed up <productname>PostgreSQL</productname>,
+       thanks to the variety of talents within our team.  We have
+       sped up memory allocation, optimization, table joins, and row
+       transfer routines.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Ports
+     </term>
+     <listitem>
+      <para>
+       We continue to expand our port list, this time including
+       <systemitem class="osname">Windows NT</>/<systemitem>ix86</> and <systemitem class="osname">NetBSD</>/<systemitem>arm32</>.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Interfaces
+     </term>
+     <listitem>
+      <para>
+       Most interfaces have new versions, and existing functionality
+       has been improved.
+      </para>
+     </listitem>
+    </varlistentry>
+
+    <varlistentry>
+     <term>
+      Documentation
+     </term>
+     <listitem>
+      <para>
+       New and updated material is present throughout the
+       documentation. New <acronym>FAQ</acronym>s have been
+       contributed for <systemitem class="osname">SGI</> and <systemitem class="osname">AIX</> platforms.
+       The <citetitle>Tutorial</citetitle> has introductory information
+       on <acronym>SQL</acronym> from Stefan Simkovics.
+       For the <citetitle>User's Guide</citetitle>, there are
+       reference pages covering the postmaster and more utility
+       programs, and a new appendix
+       contains details on date/time behavior.
+       The <citetitle>Administrator's Guide</citetitle> has a new
+       chapter on troubleshooting from Tom Lane.
+       And the <citetitle>Programmer's Guide</citetitle> has a
+       description of query processing, also from Stefan, and details
+       on obtaining the <productname>PostgreSQL</productname> source
+       tree via anonymous <productname>CVS</productname> and
+       <productname>CVSup</productname>.
+      </para>
+     </listitem>
+    </varlistentry>
+   </variablelist>
+  </para>
+
+  <sect2>
+   <title>Migration to Version 6.5</title>
+
+   <para>
+    A dump/restore using <application>pg_dump</application>
+    is required for those wishing to migrate data from any
+    previous release of <productname>PostgreSQL</productname>.
+    <application>pg_upgrade</application> can <emphasis>not</emphasis>
+    be used to upgrade to this release because the on-disk structure
+    of the tables has changed compared to previous releases.
+   </para>
+
+   <para>
+    The new Multiversion Concurrency Control (MVCC) features can
+    give somewhat different behaviors in multiuser
+    environments. <emphasis>Read and understand the following section
+     to ensure that your existing applications will give you the
+     behavior you need.</emphasis>
+   </para>
+
+   <sect3>
+    <title>Multiversion Concurrency Control</title>
+
+    <para>
+     Because readers in 6.5 don't lock data, regardless of transaction
+     isolation level, data read by one transaction can be overwritten by
+     another. In other words, if a row is returned by
+     <command>SELECT</command> it doesn't mean that this row really exists
+     at the time it is returned (i.e. sometime after the statement or
+     transaction began) nor that the row is protected from being deleted or
+     updated by concurrent transactions before the current transaction does
+     a commit or rollback.
     </para>
+
+    <para>
+     To ensure the actual existence of a row and protect it against
+     concurrent updates one must use <command>SELECT FOR UPDATE</command> or
+     an appropriate <command>LOCK TABLE</command> statement. This should be
+     taken into account when porting applications from previous releases of
+     <productname>PostgreSQL</productname> and other environments.
+    </para>
+
+    <para>
+     Keep the above in mind if you are using
+     <filename>contrib/refint.*</filename> triggers for
+     referential integrity. Additional techniques are required now. One way is
+     to use <command>LOCK parent_table IN SHARE ROW EXCLUSIVE MODE</command>
+     command if a transaction is going to update/delete a primary key and
+     use <command>LOCK parent_table IN SHARE MODE</command> command if a
+     transaction is going to update/insert a foreign key.
+
+     <note>
+      <para>
+       Note that if you run a transaction in SERIALIZABLE mode then you must
+       execute the <command>LOCK</command> commands above before execution of any
+       <acronym>DML</acronym> statement
+       (<command>SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO</command>) in the
+       transaction.
+      </para>
+     </note>
+    </para>
+
+    <para>
+     These inconveniences will disappear in the future
+     when the ability to read dirty
+     (uncommitted) data (regardless of isolation level) and true referential
+     integrity will be implemented.
+    </para>
+   </sect3>
    </sect2>
-  </sect1>
 
-  <sect1 id="release-6-5">
-   <title>Release 6.5</title>
-
-   <note>
-   <title>Release date</title>
-   <simpara>1999-06-09</simpara>
-   </note>
+  <sect2>
+   <title>Changes</title>
 
    <para>
-    This release marks a major step in the development team's mastery of the source
-    code we inherited from Berkeley.  You will see we are now easily adding
-    major features, thanks to the increasing size and experience of our
-    world-wide development team.
-   </para>
-
-   <para>
-    Here is a brief summary of the more notable changes:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       Multiversion concurrency control(MVCC)
-      </term>
-      <listitem>
-       <para>
-        This removes our old table-level locking, and replaces it with
-        a locking system that is superior to most commercial database
-        systems.  In a traditional system, each row that is modified
-        is locked until committed, preventing reads by other users.
-        MVCC uses the natural multiversion nature of
-        <productname>PostgreSQL</productname> to allow readers to
-        continue reading consistent data during writer activity.
-        Writers continue to use the compact pg_log transaction system.
-        This is all performed without having to allocate a lock for
-        every row like traditional database systems.  So, basically,
-        we no longer are restricted by simple table-level locking; we
-        have something better than row-level locking.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Hot backups from <application>pg_dump</application>
-      </term>
-      <listitem>
-       <para>
-        <application>pg_dump</application> takes advantage of the new
-        MVCC features to give a consistent database dump/backup while
-        the database stays online and available for queries.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Numeric data type
-      </term>
-      <listitem>
-       <para>
-        We now have a true numeric data type, with
-        user-specified precision.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Temporary tables
-      </term>
-      <listitem>
-       <para>
-        Temporary tables are guaranteed to have unique names
-        within a database session, and are destroyed on session exit.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       New SQL features
-      </term>
-      <listitem>
-       <para>
-        We now have CASE, INTERSECT, and EXCEPT statement
-        support.  We have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL,
-        SELECT ... FOR UPDATE, and an improved LOCK TABLE command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Speedups
-      </term>
-      <listitem>
-       <para>
-        We continue to speed up <productname>PostgreSQL</productname>,
-        thanks to the variety of talents within our team.  We have
-        sped up memory allocation, optimization, table joins, and row
-        transfer routines.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Ports
-      </term>
-      <listitem>
-       <para>
-        We continue to expand our port list, this time including
-        <systemitem class="osname">Windows NT</>/<systemitem>ix86</> and <systemitem class="osname">NetBSD</>/<systemitem>arm32</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Interfaces
-      </term>
-      <listitem>
-       <para>
-        Most interfaces have new versions, and existing functionality
-        has been improved.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Documentation
-      </term>
-      <listitem>
-       <para>
-        New and updated material is present throughout the
-        documentation. New <acronym>FAQ</acronym>s have been
-        contributed for <systemitem class="osname">SGI</> and <systemitem class="osname">AIX</> platforms.
-        The <citetitle>Tutorial</citetitle> has introductory information
-        on <acronym>SQL</acronym> from Stefan Simkovics.
-        For the <citetitle>User's Guide</citetitle>, there are
-        reference pages covering the postmaster and more utility
-        programs, and a new appendix
-        contains details on date/time behavior.
-        The <citetitle>Administrator's Guide</citetitle> has a new
-        chapter on troubleshooting from Tom Lane.
-        And the <citetitle>Programmer's Guide</citetitle> has a
-        description of query processing, also from Stefan, and details
-        on obtaining the <productname>PostgreSQL</productname> source
-        tree via anonymous <productname>CVS</productname> and
-        <productname>CVSup</productname>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <sect2>
-    <title>Migration to version 6.5</title>
-
-    <para>
-     A dump/restore using <application>pg_dump</application>
-     is required for those wishing to migrate data from any
-     previous release of <productname>PostgreSQL</productname>.
-     <application>pg_upgrade</application> can <emphasis>not</emphasis>
-     be used to upgrade to this release because the on-disk structure
-     of the tables has changed compared to previous releases.
-    </para>
-
-    <para>
-     The new Multiversion Concurrency Control (MVCC) features can
-     give somewhat different behaviors in multiuser
-     environments. <emphasis>Read and understand the following section
-      to ensure that your existing applications will give you the
-      behavior you need.</emphasis>
-    </para>
-
-    <sect3>
-     <title>Multiversion Concurrency Control</title>
-
-     <para>
-      Because readers in 6.5 don't lock data, regardless of transaction
-      isolation level, data read by one transaction can be overwritten by
-      another. In other words, if a row is returned by
-      <command>SELECT</command> it doesn't mean that this row really exists
-      at the time it is returned (i.e. sometime after the statement or
-      transaction began) nor that the row is protected from being deleted or
-      updated by concurrent transactions before the current transaction does
-      a commit or rollback.
-     </para>
-
-     <para>
-      To ensure the actual existence of a row and protect it against
-      concurrent updates one must use <command>SELECT FOR UPDATE</command> or
-      an appropriate <command>LOCK TABLE</command> statement. This should be
-      taken into account when porting applications from previous releases of
-      <productname>PostgreSQL</productname> and other environments.
-     </para>
-
-     <para>
-      Keep the above in mind if you are using
-      <filename>contrib/refint.*</filename> triggers for
-      referential integrity. Additional techniques are required now. One way is
-      to use <command>LOCK parent_table IN SHARE ROW EXCLUSIVE MODE</command>
-      command if a transaction is going to update/delete a primary key and
-      use <command>LOCK parent_table IN SHARE MODE</command> command if a
-      transaction is going to update/insert a foreign key.
-
-      <note>
-       <para>
-        Note that if you run a transaction in SERIALIZABLE mode then you must
-        execute the <command>LOCK</command> commands above before execution of any
-        <acronym>DML</acronym> statement
-        (<command>SELECT/INSERT/DELETE/UPDATE/FETCH/COPY_TO</command>) in the
-        transaction.
-       </para>
-      </note>
-     </para>
-
-     <para>
-      These inconveniences will disappear in the future
-      when the ability to read dirty
-      (uncommitted) data (regardless of isolation level) and true referential
-      integrity will be implemented.
-     </para>
-    </sect3>
-    </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+    <programlisting>
 Bug Fixes
 ---------
 Fix text&lt;-&gt;float8 and text&lt;-&gt;float4 conversion functions(Thomas)
@@ -7618,7 +7882,7 @@ New routines to convert between int8 and text/varchar types(Thomas)
 New bushy plans, where meta-tables are joined(Bruce)
 Enable right-hand queries by default(Bruce)
 Allow reliable maximum number of backends to be set at configure time
-      (--with-maxbackends and postmaster switch (-N backends))(Tom)
+     (--with-maxbackends and postmaster switch (-N backends))(Tom)
 GEQO default now 10 tables because of optimizer speedups(Tom)
 Allow NULL=Var for MS-SQL portability(Michael, Bruce)
 Modify contrib check_primary_key() so either "automatic" or "dependent"(Anand)
@@ -7671,19 +7935,19 @@ Add ARM32 support(Andrew McMurry)
 Better support for HP-UX 11 and UnixWare
 Improve file handling to be more uniform, prevent file descriptor leak(Tom)
 New install commands for plpgsql(Jan)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 
 <sect1 id="release-6-4-2">
 <title>Release 6.4.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-12-20</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-12-20</simpara>
+  </note>
 
 <para>
 The 6.4.1 release was improperly packaged.  This also has one additional
@@ -7692,7 +7956,7 @@ bug fix.
 
 
 <sect2>
-<title>Migration to version 6.4.2</title>
+<title>Migration to Version 6.4.2</title>
 
 <para>
 A dump/restore is <emphasis>not</emphasis> required for those running
@@ -7715,10 +7979,10 @@ Fix for datetime constant problem on some platforms(Thomas)
 <sect1 id="release-6-4-1">
 <title>Release 6.4.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-12-18</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-12-18</simpara>
+  </note>
 
 <para>
 This is basically a cleanup release for 6.4.  We have fixed a variety of
@@ -7727,7 +7991,7 @@ problems reported by 6.4 users.
 
 
 <sect2>
-<title>Migration to version 6.4.1</title>
+<title>Migration to Version 6.4.1</title>
 
 <para>
 A dump/restore is <emphasis>not</emphasis> required for those running
@@ -7740,12 +8004,12 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 <para>
 <programlisting>
 Add pg_dump -N flag to force double quotes around identifiers.  This is
-        the default(Thomas)
+       the default(Thomas)
 Fix for NOT in where clause causing crash(Bruce)
 EXPLAIN VERBOSE coredump fix(Vadim)
 Fix shared-library problems on Linux
 Fix test for table existence to allow mixed-case and whitespace in
-        the table name(Thomas)
+       the table name(Thomas)
 Fix a couple of pg_dump bugs
 Configure matches template/.similar entries better(Tom)
 Change builtin function names from SPI_* to spi_*
@@ -7779,10 +8043,10 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
 <sect1 id="release-6-4">
 <title>Release 6.4</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-10-30</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-10-30</simpara>
+  </note>
 
 <para>
 There are <emphasis>many</emphasis> new features and improvements in this release.
@@ -7861,7 +8125,7 @@ been.
 </para>
 
 <sect2>
-<title>Migration to version 6.4</title>
+<title>Migration to Version 6.4</title>
 
 <para>
 A dump/restore using <application>pg_dump</application>
@@ -7871,11 +8135,11 @@ previous release of <productname>PostgreSQL</productname>.
 </para>
 </sect2>
 
-   <sect2>
+  <sect2>
 <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 Fix for a tiny memory leak in PQsetdb/PQfinish(Bryan)
@@ -7988,22 +8252,22 @@ Indexes for restriction clauses containing a constant(Thomas)
 New ISBN/ISSN code in /contrib/isbn_issn
 Allow NOT LIKE, IN, NOT IN, BETWEEN, and NOT BETWEEN constraint(Thomas)
 New rewrite system fixes many problems with rules and views(Jan)
-        * Rules on relations work
-        * Event qualifications on insert/update/delete work
-        * New OLD variable to reference CURRENT, CURRENT will be remove in future
-        * Update rules can reference NEW and OLD in rule qualifications/actions
-        * Insert/update/delete rules on views work
-        * Multiple rule actions are now supported, surrounded by parentheses
-        * Regular users can create views/rules on tables they have RULE permits
-        * Rules and views inherit the privileges of the creator
-        * No rules at the column level
-        * No UPDATE NEW/OLD rules
-        * New pg_tables, pg_indexes, pg_rules and pg_views system views
-        * Only a single action on SELECT rules
-        * Total rewrite overhaul, perhaps for 6.5
-        * handle subselects
-        * handle aggregates on views
-        * handle insert into select from view works
+       * Rules on relations work
+       * Event qualifications on insert/update/delete work
+       * New OLD variable to reference CURRENT, CURRENT will be remove in future
+       * Update rules can reference NEW and OLD in rule qualifications/actions
+       * Insert/update/delete rules on views work
+       * Multiple rule actions are now supported, surrounded by parentheses
+       * Regular users can create views/rules on tables they have RULE permits
+       * Rules and views inherit the privileges of the creator
+       * No rules at the column level
+       * No UPDATE NEW/OLD rules
+       * New pg_tables, pg_indexes, pg_rules and pg_views system views
+       * Only a single action on SELECT rules
+       * Total rewrite overhaul, perhaps for 6.5
+       * handle subselects
+       * handle aggregates on views
+       * handle insert into select from view works
 System indexes are now multikey(Bruce)
 Oidint2, oidint4, and oidname types are removed(Bruce)
 Use system cache for more system table lookups(Bruce)
@@ -8076,10 +8340,10 @@ new Makefile.shlib for shared library configuration(Tom)
 <sect1 id="release-6-3-2">
 <title>Release 6.3.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-04-07</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-04-07</simpara>
+  </note>
 
 <para>
 This is a bug-fix release for 6.3.x.
@@ -8115,11 +8379,11 @@ For upgrades from pre-6.3 installations,
 refer to the installation and migration instructions for version 6.3.
 </para>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Configure detection improvements for tcl/tk(Brook Milligan, Alvin)
 Manual page improvements(Bruce)
 BETWEEN and LIKE fix(Thomas)
@@ -8138,21 +8402,21 @@ libreadline cleanup(Erwan MAS)
 Remove DISTDIR(Bruce)
 Makefile dependency cleanup(Jeroen van Vianen)
 ASSERT fixes(Bruce)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-6-3-1">
-   <title>Release 6.3.1</title>
+ <sect1 id="release-6-3-1">
+  <title>Release 6.3.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-03-23</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-03-23</simpara>
+  </note>
 
-   <para>
-    Summary:
+  <para>
+   Summary:
 
 <itemizedlist>
 <listitem>
@@ -8192,11 +8456,11 @@ For upgrades from pre-6.3 installations,
 refer to the installation and migration instructions for version 6.3.
 </para>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 ecpg cleanup/fixes, now version 1.1(Michael Meskes)
 pg_user cleanup(Bruce)
 large object fix for pg_dump and tclsh (alvin)
@@ -8224,154 +8488,154 @@ Fix Alpha port(Dwayne Bailey)
 Fix for text arrays containing quotes(Doug Gibson)
 Solaris compile fix(Albert Chin-A-Young)
 Better identify tcl and tk libs and includes(Bruce)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
-  <sect1 id="release-6-3">
-   <title>Release 6.3</title>
+ <sect1 id="release-6-3">
+  <title>Release 6.3</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1998-03-01</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1998-03-01</simpara>
+  </note>
+
+  <para>
+   There are <emphasis>many</emphasis> new features and improvements in this release.
+   Here is a brief, incomplete summary:
+
+   <itemizedlist>
+    <listitem>
+     <para>
+      Many new SQL features, including
+      full <acronym>SQL92</acronym> subselect capability
+      (everything is here but target-list subselects).
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Support for client-side environment variables to specify time zone and date style.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Socket interface for client/server connection. This is the default now
+      so you might need to start <application>postmaster</application> with the
+      <option>-i</option> flag.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Better password authorization mechanisms. Default table privileges have changed.
+     </para>
+    </listitem>
+
+    <listitem>
+     <para>
+      Old-style <firstterm>time travel</firstterm>
+      has been removed. Performance has been improved.
+     </para>
+    </listitem>
+   </itemizedlist>
+  </para>
+
+  <note>
+   <para>
+    Bruce Momjian wrote the following notes to introduce the new release.
+   </para>
+  </note>
+
+  <para>
+   There are some general 6.3 issues that I want to mention.  These are
+   only the big items that cannot be described in one sentence.  A review
+   of the detailed changes list is still needed.
+  </para>
+  <para>
+   First, we now have subselects.  Now that we have them, I would like to
+   mention that without subselects, SQL is a very limited language.
+   Subselects are a major feature, and you should review your code for
+   places where subselects provide a better solution for your queries.  I
+   think you will find that there are more uses for subselects than you might
+   think.  Vadim has put us on the big SQL map with subselects, and fully
+   functional ones too.  The only thing you cannot do with subselects is to
+   use them in the target list.
+  </para>
+  <para>
+   Second, 6.3 uses Unix domain sockets rather than TCP/IP by default.  To
+   enable connections from other machines, you have to use the new
+   postmaster -i option, and of course edit <filename>pg_hba.conf</filename>.  Also, for this
+   reason, the format of <filename>pg_hba.conf</filename> has changed.
+  </para>
+  <para>
+   Third, <type>char()</type> fields will now allow faster access than <type>varchar()</type> or
+   <type>text</type>. Specifically, the <type>text</> and <type>varchar()</type> have a penalty for access to
+   any columns after the first column of this type.  <type>char()</type> used to also
+   have this access penalty, but it no longer does.  This might suggest that
+   you redesign some of your tables, especially if you have short character
+   columns that you have defined as <type>varchar()</type> or <type>text</type>.  This and other
+   changes make 6.3 even faster than earlier releases.
+  </para>
+  <para>
+   We now have passwords definable independent of any Unix file.  There are
+   new SQL USER commands.
+   See the <citetitle>Administrator's Guide</citetitle> for more
+   information.  There is a new table, pg_shadow, which is used to store
+   user information and user passwords, and it by default only SELECT-able
+   by the <systemitem>postgres</systemitem> super-user.  pg_user is now a view of pg_shadow, and is
+   SELECT-able by PUBLIC.  You should keep using pg_user in your
+   application without changes.
+  </para>
+  <para>
+   User-created tables now no longer have SELECT privilege to PUBLIC by
+   default.  This was done because the ANSI standard requires it.  You can
+   of course GRANT any privileges you want after the table is created.
+   System tables continue to be SELECT-able by PUBLIC.
+  </para>
+  <para>
+   We also have real deadlock detection code.  No more sixty-second
+   timeouts.  And the new locking code implements a <acronym>FIFO</acronym> better, so there
+   should be less resource starvation during heavy use.
+  </para>
+  <para>
+   Many complaints have been made about inadequate documentation in previous
+   releases.  Thomas has put much effort into many new manuals for this
+   release.  Check out the doc/ directory.
+  </para>
+  <para>
+   For performance reasons, time travel is gone, but can be implemented
+   using triggers (see <filename>pgsql/contrib/spi/README</filename>).  Please check out the new
+   \d command for types, operators, etc.  Also, views have their own
+   privileges now, not based on the underlying tables, so privileges on
+   them have to be set separately.  Check <filename>/pgsql/interfaces</filename> for some new
+   ways to talk to <productname>PostgreSQL</productname>.
+  </para>
+  <para>
+   This is the first release that really required an explanation for
+   existing users.  In many ways, this was necessary because the new
+   release removes many limitations, and the work-arounds people were using
+   are no longer needed.
+  </para>
+
+  <sect2>
+   <title>Migration to Version 6.3</title>
 
    <para>
-    There are <emphasis>many</emphasis> new features and improvements in this release.
-    Here is a brief, incomplete summary:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Many new SQL features, including
-       full <acronym>SQL92</acronym> subselect capability
-       (everything is here but target-list subselects).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Support for client-side environment variables to specify time zone and date style.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Socket interface for client/server connection. This is the default now
-       so you might need to start <application>postmaster</application> with the
-       <option>-i</option> flag.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Better password authorization mechanisms. Default table privileges have changed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Old-style <firstterm>time travel</firstterm>
-       has been removed. Performance has been improved.
-      </para>
-     </listitem>
-    </itemizedlist>
+    A dump/restore using <application>pg_dump</application>
+    or <application>pg_dumpall</application>
+    is required for those wishing to migrate data from any
+    previous release of <productname>PostgreSQL</productname>.
    </para>
+  </sect2>
 
-   <note>
-    <para>
-     Bruce Momjian wrote the following notes to introduce the new release.
-    </para>
-   </note>
+  <sect2>
+   <title>Changes</title>
 
    <para>
-    There are some general 6.3 issues that I want to mention.  These are
-    only the big items that cannot be described in one sentence.  A review
-    of the detailed changes list is still needed.
-   </para>
-   <para>
-    First, we now have subselects.  Now that we have them, I would like to
-    mention that without subselects, SQL is a very limited language.
-    Subselects are a major feature, and you should review your code for
-    places where subselects provide a better solution for your queries.  I
-    think you will find that there are more uses for subselects than you might
-    think.  Vadim has put us on the big SQL map with subselects, and fully
-    functional ones too.  The only thing you cannot do with subselects is to
-    use them in the target list.
-   </para>
-   <para>
-    Second, 6.3 uses Unix domain sockets rather than TCP/IP by default.  To
-    enable connections from other machines, you have to use the new
-    postmaster -i option, and of course edit <filename>pg_hba.conf</filename>.  Also, for this
-    reason, the format of <filename>pg_hba.conf</filename> has changed.
-   </para>
-   <para>
-    Third, <type>char()</type> fields will now allow faster access than <type>varchar()</type> or
-    <type>text</type>. Specifically, the <type>text</> and <type>varchar()</type> have a penalty for access to
-    any columns after the first column of this type.  <type>char()</type> used to also
-    have this access penalty, but it no longer does.  This might suggest that
-    you redesign some of your tables, especially if you have short character
-    columns that you have defined as <type>varchar()</type> or <type>text</type>.  This and other
-    changes make 6.3 even faster than earlier releases.
-   </para>
-   <para>
-    We now have passwords definable independent of any Unix file.  There are
-    new SQL USER commands.
-    See the <citetitle>Administrator's Guide</citetitle> for more
-    information.  There is a new table, pg_shadow, which is used to store
-    user information and user passwords, and it by default only SELECT-able
-    by the <systemitem>postgres</systemitem> super-user.  pg_user is now a view of pg_shadow, and is
-    SELECT-able by PUBLIC.  You should keep using pg_user in your
-    application without changes.
-   </para>
-   <para>
-    User-created tables now no longer have SELECT privilege to PUBLIC by
-    default.  This was done because the ANSI standard requires it.  You can
-    of course GRANT any privileges you want after the table is created.
-    System tables continue to be SELECT-able by PUBLIC.
-   </para>
-   <para>
-    We also have real deadlock detection code.  No more sixty-second
-    timeouts.  And the new locking code implements a <acronym>FIFO</acronym> better, so there
-    should be less resource starvation during heavy use.
-   </para>
-   <para>
-    Many complaints have been made about inadequate documentation in previous
-    releases.  Thomas has put much effort into many new manuals for this
-    release.  Check out the doc/ directory.
-   </para>
-   <para>
-    For performance reasons, time travel is gone, but can be implemented
-    using triggers (see <filename>pgsql/contrib/spi/README</filename>).  Please check out the new
-    \d command for types, operators, etc.  Also, views have their own
-    privileges now, not based on the underlying tables, so privileges on
-    them have to be set separately.  Check <filename>/pgsql/interfaces</filename> for some new
-    ways to talk to <productname>PostgreSQL</productname>.
-   </para>
-   <para>
-    This is the first release that really required an explanation for
-    existing users.  In many ways, this was necessary because the new
-    release removes many limitations, and the work-arounds people were using
-    are no longer needed.
-   </para>
-
-   <sect2>
-    <title>Migration to version 6.3</title>
-
-    <para>
-     A dump/restore using <application>pg_dump</application>
-     or <application>pg_dumpall</application>
-     is required for those wishing to migrate data from any
-     previous release of <productname>PostgreSQL</productname>.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-     <programlisting>
+    <programlisting>
 Bug Fixes
 ---------
 Fix binary cursors broken by MOVE implementation(Vadim)
@@ -8391,19 +8655,19 @@ Fix for count(*), aggs with views and multiple tables and sum(3)(Bruce)
 Fix cluster(Bruce)
 Fix for PQtrace start/stop several times(Bruce)
 Fix a variety of locking problems like newer lock waiters getting
-        lock before older waiters, and having readlock people not share
-        locks if a writer is waiting for a lock, and waiting writers not
-        getting priority over waiting readers(Bruce)
+       lock before older waiters, and having readlock people not share
+       locks if a writer is waiting for a lock, and waiting writers not
+       getting priority over waiting readers(Bruce)
 Fix crashes in psql when executing queries from external files(James)
 Fix problem with multiple order by columns, with the first one having
-        NULL values(Jeroen)
+       NULL values(Jeroen)
 Use correct hash table support functions for float8 and int4(Thomas)
 Re-enable JOIN= option in CREATE OPERATOR statement (Thomas)
 Change precedence for boolean operators to match expected behavior(Thomas)
 Generate elog(ERROR) on over-large integer(Bruce)
 Allow multiple-argument functions in constraint clauses(Thomas)
 Check boolean input literals for 'true','false','yes','no','1','0'
-        and throw elog(ERROR) if unrecognized(Thomas)
+       and throw elog(ERROR) if unrecognized(Thomas)
 Major large objects fix
 Fix for GROUP BY showing duplicates(Vadim)
 Fix for index scans in MergeJoin(Vadim)
@@ -8415,7 +8679,7 @@ New User Manual(Thomas, others)
 Speedup by inlining some frequently-called functions
 Real deadlock detection, no more timeouts(Bruce)
 Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
-        CURRENT_USER(Thomas)
+       CURRENT_USER(Thomas)
 Modify constraint syntax to be SQL92-compliant(Thomas)
 Implement SQL92 PRIMARY KEY and UNIQUE clauses using indexes(Thomas)
 Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
@@ -8427,11 +8691,11 @@ Allow shorter strings for boolean literals (e.g. "t", "tr", "tru")(Thomas)
 Allow SQL92 delimited identifiers(Thomas)
 Implement SQL92 binary and hexadecimal string decoding (b'10' and x'1F')(Thomas)
 Support SQL92 syntax for type coercion of literal strings
-        (e.g. "DATETIME 'now'")(Thomas)
+       (e.g. "DATETIME 'now'")(Thomas)
 Add conversions for int2, int4, and OID types to and from text(Thomas)
 Use shared lock when building indexes(Vadim)
 Free memory allocated for an user query inside transaction block after
-        this query is done, was turned off in &lt;= 6.2.1(Vadim)
+       this query is done, was turned off in &lt;= 6.2.1(Vadim)
 New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)
 New <productname>PostgreSQL</productname> Procedural Language (PL) backend interface(Jan)
 Rename pg_dump -H option to -h(Bruce)
@@ -8449,10 +8713,10 @@ Implement SET keyword = DEFAULT and SET TIME ZONE DEFAULT(Thomas)
 Enable SET TIME ZONE using TZ environment variable(Thomas)
 Add PGDATESTYLE environment variable to frontend and backend initialization(Thomas)
 Add PGTZ, PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
-        frontend library initialization environment variables(Thomas)
+       frontend library initialization environment variables(Thomas)
 Regression tests time zone automatically set with "setenv PGTZ PST8PDT"(Thomas)
 Add pg_description table for info on tables, columns, operators, types, and
-        aggregates(Bruce)
+       aggregates(Bruce)
 Increase 16 char limit on system table/index names to 32 characters(Bruce)
 Rename system indexes(Bruce)
 Add 'GERMAN' option to SET DATESTYLE(Thomas)
@@ -8463,7 +8727,7 @@ Implement day of year as possible input to date_part()(Thomas)
 Define timespan_finite() and text_timespan() functions(Thomas)
 Remove archive stuff(Bruce)
 Allow for a pg_password authentication database that is separate from
-        the system password file(Todd)
+       the system password file(Todd)
 Dump ACLs, GRANT, REVOKE privileges(Matt)
 Define text, varchar, and bpchar string length functions(Thomas)
 Fix Query handling for inheritance, and cost computations(Bruce)
@@ -8495,9 +8759,9 @@ Remove pg_time table(Vadim)
 Add pg_type attribute to identify types that need length (bpchar, varchar)
 Add report of offending line when COPY command fails
 Allow VIEW privileges to be set separately from the underlying tables.
-        For security, use GRANT/REVOKE on views as appropriate(Jan)
+       For security, use GRANT/REVOKE on views as appropriate(Jan)
 Tables now have no default GRANT SELECT TO PUBLIC.  You must
-        explicitly grant such privileges.
+       explicitly grant such privileges.
 Clean up tutorial examples(Darren)
 
 Source Tree Changes
@@ -8505,12 +8769,12 @@ Source Tree Changes
 Add new html development tools, and flow chart in /tools/backend
 Fix for SCO compiles
 Stratus computer port Robert Gillies
-Added support for shlib for BSD44_derived & i386_solaris
+Added support for shlib for BSD44_derived &amp; i386_solaris
 Make configure more automated(Brook)
 Add script to check regression test results
 Break parser functions into smaller files, group together(Bruce)
 Rename heap_create to heap_create_and_catalog, rename heap_creatr
-        to heap_create()(Bruce)
+       to heap_create()(Bruce)
 Sparc/Linux patch for locking(TomS)
 Remove PORTNAME and reorganize port-specific stuff(Marc)
 Add optimizer README file(Bruce)
@@ -8519,7 +8783,7 @@ Fix for NetBSD locking(Henry)
 Fix for libptcl make(Tatsuo)
 AIX patch(Darren)
 Change IS TRUE, IS FALSE, ... to expressions using "=" rather than
-        function calls to istrue() or isfalse() to allow optimization(Thomas)
+       function calls to istrue() or isfalse() to allow optimization(Thomas)
 Various fixes NetBSD/Sparc related(TomH)
 Alpha linux locking(Travis,Ryan)
 Change elog(WARN) to elog(ERROR)(Bruce)
@@ -8544,10 +8808,10 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
 <sect1 id="release-6-2-1">
 <title>Release 6.2.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1997-10-17</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1997-10-17</simpara>
+  </note>
 
 <para>
 6.2.1 is a bug-fix and usability release on 6.2.
@@ -8593,8 +8857,8 @@ Another way to avoid dump/reload is to use the following SQL command
 from <command>psql</command> to update the existing system table:
 
 <programlisting>
-  update pg_aggregate set aggfinalfn = 'cash_div_flt8'
-   where aggname = 'avg' and aggbasetype = 790;
+ update pg_aggregate set aggfinalfn = 'cash_div_flt8'
+  where aggname = 'avg' and aggbasetype = 790;
 </programlisting>
 </para>
 <para>
@@ -8602,11 +8866,11 @@ This will need to be done to every existing database, including template1.
 </para>
 </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Allow TIME and TYPE column names(Thomas)
 Allow larger range of true/false as boolean values(Thomas)
 Support output of "now" and "current"(Thomas)
@@ -8618,18 +8882,18 @@ Fix avg(cash) computation(Thomas)
 Fix for specifying a column twice in ORDER/GROUP BY(Vadim)
 Documented new libpq function to return affected rows, PQcmdTuples(Bruce)
 Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 <sect1 id="release-6-2">
 <title>Release 6.2</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1997-10-02</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1997-10-02</simpara>
+  </note>
 
 <para>
 A dump/restore is required for those wishing to migrate data from
@@ -8658,56 +8922,56 @@ because the COPY output format was improved from the 1.02 release.
 </para>
 </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 Fix problems with pg_dump for inheritance, sequences, archive tables(Bruce)
 Fix compile errors on overflow due to shifts, unsigned, and bad prototypes
-         from Solaris(Diab Jerius)
+        from Solaris(Diab Jerius)
 Fix bugs in geometric line arithmetic (bad intersection calculations)(Thomas)
 Check for geometric intersections at endpoints to avoid rounding ugliness(Thomas)
 Catch non-functional delete attempts(Vadim)
 Change time function names to be more consistent(Michael Reifenberg)
 Check for zero divides(Michael Reifenberg)
 Fix very old bug which made rows changed/inserted by a command
-        visible to the command itself (so we had multiple update of
-        updated rows, etc.)(Vadim)
+       visible to the command itself (so we had multiple update of
+       updated rows, etc.)(Vadim)
 Fix for SELECT null, 'fail' FROM pg_am (Patrick)
 SELECT NULL as EMPTY_FIELD now allowed(Patrick)
 Remove un-needed signal stuff from contrib/pginterface
 Fix OR (where x != 1 or x isnull didn't return rows with x NULL) (Vadim)
 Fix time_cmp function (Vadim)
 Fix handling of functions with non-attribute first argument in
-        WHERE clauses (Vadim)
+       WHERE clauses (Vadim)
 Fix GROUP BY when order of entries is different from order
-        in target list (Vadim)
+       in target list (Vadim)
 Fix pg_dump for aggregates without sfunc1 (Vadim)
 
 Enhancements
 ------------
 Default genetic optimizer GEQO parameter is now 8(Bruce)
 Allow use parameters in target list having aggregates in functions(Vadim)
-Added JDBC driver as an interface(Adrian & Peter)
+Added JDBC driver as an interface(Adrian &amp; Peter)
 pg_password utility
 Return number of rows inserted/affected by INSERT/UPDATE/DELETE etc.(Vadim)
 Triggers implemented with CREATE TRIGGER (SQL3)(Vadim)
 SPI (Server Programming Interface) allows execution of queries inside
-        C-functions (Vadim)
+       C-functions (Vadim)
 NOT NULL implemented (SQL92)(Robson Paniago de Miranda)
 Include reserved words for string handling, outer joins, and unions(Thomas)
 Implement extended comments ("/* ... */") using exclusive states(Thomas)
 Add "//" single-line comments(Bruce)
 Remove some restrictions on characters in operator names(Thomas)
-DEFAULT and CONSTRAINT for tables implemented (SQL92)(Vadim & Thomas)
+DEFAULT and CONSTRAINT for tables implemented (SQL92)(Vadim &amp; Thomas)
 Add text concatenation operator and function (SQL92)(Thomas)
 Support WITH TIME ZONE syntax (SQL92)(Thomas)
 Support INTERVAL unit TO unit syntax (SQL92)(Thomas)
 Define types DOUBLE PRECISION, INTERVAL, CHARACTER,
-        and CHARACTER VARYING (SQL92)(Thomas)
+       and CHARACTER VARYING (SQL92)(Thomas)
 Define type FLOAT(p) and rudimentary DECIMAL(p,s), NUMERIC(p,s) (SQL92)(Thomas)
 Define EXTRACT(), POSITION(), SUBSTRING(), and TRIM() (SQL92)(Thomas)
 Define CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP (SQL92)(Thomas)
@@ -8717,14 +8981,14 @@ Allow hh:mm:ss time entry for timespan/reltime types(Thomas)
 Add center() routines for lseg, path, polygon(Thomas)
 Add distance() routines for circle-polygon, polygon-polygon(Thomas)
 Check explicitly for points and polygons contained within polygons
-        using an axis-crossing algorithm(Thomas)
+       using an axis-crossing algorithm(Thomas)
 Add routine to convert circle-box(Thomas)
 Merge conflicting operators for different geometric data types(Thomas)
 Replace distance operator "&lt;===&gt;" with "&lt;-&gt;"(Thomas)
 Replace "above" operator "!^" with "&gt;^" and "below" operator "!|" with "&lt;^"(Thomas)
 Add routines for text trimming on both ends, substring, and string position(Thomas)
 Added conversion routines circle(box) and poly(circle)(Thomas)
-Allow internal sorts to be stored in memory rather than in files(Bruce & Vadim)
+Allow internal sorts to be stored in memory rather than in files(Bruce &amp; Vadim)
 Allow functions and operators on internally-identical types to succeed(Bruce)
 Speed up backend start-up after profiling analysis(Bruce)
 Inline frequently called functions for performance(Bruce)
@@ -8757,7 +9021,7 @@ new interfaces directory(Marc)
 Replace fopen() calls with calls to fd.c functions(Bruce)
 Make functions static where possible(Bruce)
 enclose unused functions in #ifdef NOT_USED(Bruce)
-Remove call to difftime() in timestamp support to fix SunOS(Bruce & Thomas)
+Remove call to difftime() in timestamp support to fix SunOS(Bruce &amp; Thomas)
 Changes for Digital Unix
 Portability fix for pg_dumpall(Bruce)
 Rename pg_attribute.attnvals to attdispersion(Bruce)
@@ -8765,12 +9029,12 @@ Rename pg_attribute.attnvals to attdispersion(Bruce)
 "built-in" manual page now "pgbuiltin"(Bruce)
 "drop" manual page now "drop_table"(Bruce)
 Add "create_trigger", "drop_trigger" manual pages(Thomas)
-Add constraints regression test(Vadim & Thomas)
+Add constraints regression test(Vadim &amp; Thomas)
 Add comments syntax regression test(Thomas)
 Add PGINDENT and support program(Bruce)
 Massive commit to run PGINDENT on all *.c and *.h files(Bruce)
 Files moved to /src/tools directory(Bruce)
-SPI and Trigger programming guides (Vadim & D'Arcy)
+SPI and Trigger programming guides (Vadim &amp; D'Arcy)
 </programlisting>
 </para>
 </sect2>
@@ -8779,10 +9043,10 @@ SPI and Trigger programming guides (Vadim & D'Arcy)
 <sect1 id="release-6-1-1">
 <title>Release 6.1.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1997-07-22</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1997-07-22</simpara>
+  </note>
 
 <sect2>
 <title>Migration from version 6.1 to version 6.1.1</title>
@@ -8794,11 +9058,11 @@ Refer to the release notes for 6.1 for more details.
 </para>
 </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 fix for SET with options (Thomas)
 allow pg_dump/pg_dumpall to preserve ownership of all tables/objects(Bruce)
 new psql \connect option allows changing usernames without changing databases
@@ -8816,68 +9080,68 @@ major fix for endian handling of communication to server(Thomas, Tatsuo)
 Fix for Solaris assembler and include files(Yoshihiko Ichikawa)
 allow underscores in usernames(Bruce)
 pg_dumpall now returns proper status, portability fix(Bruce)
-     </programlisting>
-    </para>
-   </sect2>
-  </sect1>
+    </programlisting>
+   </para>
+  </sect2>
+ </sect1>
 
 <sect1 id="release-6-1">
 <title>Release 6.1</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1997-06-08</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1997-06-08</simpara>
+  </note>
 
 <para>
-  The regression tests have been adapted and extensively modified for the
-  6.1 release of <productname>PostgreSQL</productname>.
+ The regression tests have been adapted and extensively modified for the
+ 6.1 release of <productname>PostgreSQL</productname>.
 </para>
 
 <para>
-  Three new data types (<type>datetime</type>, <type>timespan</type>, and <type>circle</type>) have been added to
-  the native set of <productname>PostgreSQL</productname> types. Points, boxes, paths, and polygons
-  have had their output formats made consistent across the data types.
-  The polygon output in misc.out has only been spot-checked for correctness
-  relative to the original regression output.
+ Three new data types (<type>datetime</type>, <type>timespan</type>, and <type>circle</type>) have been added to
+ the native set of <productname>PostgreSQL</productname> types. Points, boxes, paths, and polygons
+ have had their output formats made consistent across the data types.
+ The polygon output in misc.out has only been spot-checked for correctness
+ relative to the original regression output.
 </para>
 
 <para>
-  <productname>PostgreSQL</productname> 6.1 introduces a new, alternate
+ <productname>PostgreSQL</productname> 6.1 introduces a new, alternate
 optimizer which uses <firstterm>genetic</firstterm>
-  algorithms. These algorithms introduce a random behavior in the ordering
-  of query results when the query contains multiple qualifiers or multiple
-  tables (giving the optimizer a choice on order of evaluation). Several
-  regression tests have been modified to explicitly order the results, and
-  hence are insensitive to optimizer choices. A few regression tests are
-  for data types which are inherently unordered (e.g. points and time
-  intervals) and tests involving those types are explicitly bracketed with
-  <command>set geqo to 'off'</command> and <command>reset geqo</command>.
+ algorithms. These algorithms introduce a random behavior in the ordering
+ of query results when the query contains multiple qualifiers or multiple
+ tables (giving the optimizer a choice on order of evaluation). Several
+ regression tests have been modified to explicitly order the results, and
+ hence are insensitive to optimizer choices. A few regression tests are
+ for data types which are inherently unordered (e.g. points and time
+ intervals) and tests involving those types are explicitly bracketed with
+ <command>set geqo to 'off'</command> and <command>reset geqo</command>.
 </para>
 
 <para>
-  The interpretation of array specifiers (the curly braces around atomic
-  values) appears to have changed sometime after the original regression
-  tests were generated. The current <filename>./expected/*.out</filename> files reflect this
-  new interpretation, which might not be correct!
+ The interpretation of array specifiers (the curly braces around atomic
+ values) appears to have changed sometime after the original regression
+ tests were generated. The current <filename>./expected/*.out</filename> files reflect this
+ new interpretation, which might not be correct!
 </para>
 
 <para>
-  The float8 regression test fails on at least some platforms. This is due
-  to differences in implementations of <function>pow()</function> and <function>exp()</function> and the signaling
-  mechanisms used for overflow and underflow conditions.
+ The float8 regression test fails on at least some platforms. This is due
+ to differences in implementations of <function>pow()</function> and <function>exp()</function> and the signaling
+ mechanisms used for overflow and underflow conditions.
 </para>
 
 <para>
-  The <quote>random</> results in the random test should cause the
-  <quote>random</quote> test to be <quote>failed</quote>, since the
-  regression tests are evaluated using a simple diff. However,
-  <quote>random</> does not seem to produce random results on my test
-  machine (Linux/<application>gcc</>/i686).
+ The <quote>random</> results in the random test should cause the
+ <quote>random</quote> test to be <quote>failed</quote>, since the
+ regression tests are evaluated using a simple diff. However,
+ <quote>random</> does not seem to produce random results on my test
+ machine (Linux/<application>gcc</>/i686).
 </para>
 
 <sect2>
-<title>Migration to version 6.1</title>
+<title>Migration to Version 6.1</title>
 
 <para>
 This migration requires a complete dump of the 6.0 database and a
@@ -8889,11 +9153,11 @@ because the COPY output format was improved from the 1.02 release.
 </para>
 </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 packet length checking in library routines
@@ -8996,10 +9260,10 @@ DG/UX, Ultrix, IRIX, AIX portability fixes
 <sect1 id="release-6-0">
 <title>Release 6.0</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1997-01-29</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1997-01-29</simpara>
+  </note>
 
 <para>
 A dump/restore is required for those wishing to migrate data from
@@ -9024,11 +9288,11 @@ because the COPY output format was improved from the 1.02 release.
 </para>
 </sect2>
 
-   <sect2>
-    <title>Changes</title>
+  <sect2>
+   <title>Changes</title>
 
-    <para>
-     <programlisting>
+   <para>
+    <programlisting>
 Bug Fixes
 ---------
 ALTER TABLE bug - running postgres process needs to re-read table definition
@@ -9077,7 +9341,7 @@ Allow libpq to distinguish between text value '' and null(Bruce)
 Allow non-postgres users with createdb privs to destroydb's
 Allow restriction on who can create C functions(Bryan)
 Allow restriction on who can do backend COPY(Bryan)
-Can shrink tables, pg_time and pg_log(Vadim & Erich)
+Can shrink tables, pg_time and pg_log(Vadim &amp; Erich)
 Change debug level 2 to print queries only, changed debug heading layout(Bruce)
 Change default decimal constant representation from float4 to float8(Bruce)
 European date format now set when postmaster is started
@@ -9140,10 +9404,10 @@ Unused/uninitialized variables corrected
 <sect1 id="release-1-09">
 <title>Release 1.09</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1996-11-04</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1996-11-04</simpara>
+  </note>
 
 <para>
 Sorry, we didn't keep track of changes from 1.02 to 1.09.  Some of
@@ -9155,10 +9419,10 @@ releases.
 <sect1 id="release-1-02">
 <title>Release 1.02</title>
 
-   <note>
-   <title>Release date</title>
-   <simpara>1996-08-01</simpara>
-   </note>
+  <note>
+  <title>Release date</title>
+  <simpara>1996-08-01</simpara>
+  </note>
 
 <sect2>
 <title>Migration from version 1.02 to version 1.02.1</title>
@@ -9191,13 +9455,13 @@ Start up a new 1.02.1 postmaster
 <step>
 <para>
 Add the new built-in functions and operators of 1.02.1 to 1.01 or 1.02
-   databases.  This is done by running the new 1.02.1 server against
-   your own 1.01 or 1.02 database and applying the queries attached at
-   the end of the file.   This can be done easily through <command>psql</>.  If your
-   1.01 or 1.02 database is named <literal>testdb</literal> and you have cut the commands
-   from the end of this file and saved them in <filename>addfunc.sql</filename>:
+  databases.  This is done by running the new 1.02.1 server against
+  your own 1.01 or 1.02 database and applying the queries attached at
+  the end of the file.   This can be done easily through <command>psql</>.  If your
+  1.01 or 1.02 database is named <literal>testdb</literal> and you have cut the commands
+  from the end of this file and saved them in <filename>addfunc.sql</filename>:
 <programlisting>
-        % psql testdb -f addfunc.sql
+       % psql testdb -f addfunc.sql
 </programlisting>
 
 Those upgrading 1.02 databases will get a warning when executing the
@@ -9220,7 +9484,7 @@ end-of-data marker.  Also, empty strings are now loaded in as '' rather
 than NULL. See the copy manual page for full details.
 
 <programlisting>
-        sed 's/^\.$/\\./g' &lt;in_file &gt;out_file
+       sed 's/^\.$/\\./g' &lt;in_file &gt;out_file
 </programlisting>
 </para>
 <para>