Fixups for 7.0.1

2 files changed, 196 insertions, 101 deletions

diff --git a/doc/src/FAQ.html b/doc/src/FAQ.html
index 1ed10902d88..bbee79245fe 100644
--- a/doc/src/FAQ.html
+++ b/doc/src/FAQ.html
@@ -18,12 +18,15 @@ Web site, <A HREF="http://www.Postgresql.org">http://www.PostgreSQL.org</A>.<P>
 Linux-specific questions are answered in <A
 HREF="http://www.PostgreSQL.org/docs/faq-linux.html">http://www.PostgreSQL.org/docs/faq-linux.html</A>.<P>
 
+HPUX-specific questions are answered in <A
+HREF="http://www.PostgreSQL.org/docs/faq-hpux.html">http://www.PostgreSQL.org/docs/faq-hpux.html</A>.<P>
+
+Solaris-specific questions are answered in <A
+HREF="http://www.postgresql.org/docs/faq-solaris.html">http://www.postgresql.org/docs/faq-solaris.html</A>.<P>
+
 Irix-specific questions are answered in <A
 HREF="http://www.PostgreSQL.org/docs/faq-irix.html">http://www.PostgreSQL.org/docs/faq-irix.html</A>.<P>
 
-HPUX-specific questions are answered in <A
-HREF="http://www.PostgreSQL.org/docs/faq-hpux.shtml">http://www.PostgreSQL.org/docs/faq-hpux.shtml</A>.<P>
-
 <HR><P>
 
 <H2><CENTER>General Questions</CENTER></H2>
@@ -42,7 +45,6 @@ HREF="http://www.PostgreSQL.org/docs/faq-hpux.shtml">http://www.PostgreSQL.org/d
 <A HREF="#1.12">1.12</A>) How do I join the development team?<BR>
 <A HREF="#1.13">1.13</A>) How do I submit a bug report?<BR>
 <A HREF="#1.14">1.14</A>) How does PostgreSQL compare to other DBMS's?<BR>
-<A HREF="#1.15">1.15</A>) What are the maximum size limits?
 
 
 <H2><CENTER>User Client Questions</CENTER></H2>
@@ -120,7 +122,8 @@ is NULL?<BR>
 various character types?<BR>
 <A HREF="#4.16.1">4.16.1</A>) How do I create a serial/auto-incrementing field?<BR>
 <A HREF="#4.16.2">4.16.2</A>) How do I get the value of a serial insert?<BR>
-<A HREF="#4.16.3">4.16.3</A>) Wouldn't use of currval() and nextval() lead to a race condition with other concurrent backend processes?<BR>
+<A HREF="#4.16.3">4.16.3</A>) Don't currval() and nextval() lead to a
+race condition with other concurrent backend processes?<BR>
 
 <A HREF="#4.17">4.17</A>) What is an oid?  What is a tid?<BR>
 <A HREF="#4.18">4.18</A>) What is the meaning of some of the terms
@@ -139,7 +142,7 @@ current time?<BR>
 <H2><CENTER>Extending PostgreSQL</CENTER></H2>
 
 <A HREF="#5.1">5.1</A>) I wrote a user-defined function.  When I run
-it in <I>psql,</I> why does it dumps core?<BR>
+it in <I>psql,</I> why does it dump core?<BR>
 <A HREF="#5.2">5.2</A>) What does the message:
 <I>NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!</I> mean?<BR>
 <A HREF="#5.3">5.3</A>) How can I contribute some nifty new types and functions
@@ -353,6 +356,10 @@ http://www.postgresql.org/docs/postgres.</A>
 in the distribution.
 <P>
 
+There is a PostgreSQL book availiable at <A
+HREF="http://www.postgresql.org/docs/awbook.html">
+http://www.postgresql.org/docs/awbook.html</A><P>
+
 <I>psql</I> has some nice \d commands to show information about types,
 operators, functions, aggregates, etc.<P>
 
@@ -367,6 +374,10 @@ TODO</A> for a list of known bugs, missing features, and future plans.<P>
 
 <H4><A NAME="1.10">1.10</A>) How can I learn SQL?</H4><P>
 
+The PostgreSQL book at <A
+HREF="http://www.postgresql.org/docs/awbook.html">
+http://www.postgresql.org/docs/awbook.html</A> teaches SQL.
+
 There is a nice tutorial at <A
 HREF="http://w3.one.net/~jhoffman/sqltut.htm">
 http://w3.one.net/~jhoffman/sqltut.htm</A> and at <A
@@ -378,8 +389,8 @@ HREF="http://members.tripod.com/er4ebus/sql/index.htm">
 http://members.tripod.com/er4ebus/sql/index.htm </A><P>
 
 Many of our users like <I>The Practical SQL Handbook</I>, Bowman et al.,
-Addison Wesley.  Others like <I>Lan Times Guide to SQL</I>, Groff et al.,
-Osborne McGraw-Hill.<P>
+Addison Wesley.  Others like <I>The Complete Reference SQL</I>, Groff et al.,
+McGraw-Hill.<P>
 
 
 <H4><A NAME="1.11">1.11</A>) Is PostgreSQL Y2K compliant?</H4><P>
@@ -484,20 +495,6 @@ add our code to your product with no limitations, except those outlined
 in our BSD-style license stated above.<BR><BR>
 </DL>
 
-<H4><A NAME="1.15">1.15</A>) What are the maximum size limits?</H4><P>
-
-These are the limits:
-
-<PRE>
-Maximum size for a database? 	         unlimited (60GB databases exist)
-Maximum size for a table?                unlimited on all operating systems
-Maximum size for a row?                  8k, configurable to 32k
-Maximum number of rows in a table?	 unlimited
-Maximum number of columns table?         unlimited
-Maximun number of indexes on a table?	 unlimited
-</PRE>
-The row length limit will be removed in 7.1.<P>
-
 <HR>
 
 <H2><CENTER>User Client Questions</CENTER></H2>
@@ -580,9 +577,8 @@ We have:
 
 <UL>
 <LI> check that you don't have any of the previous version's binaries in
-your path   (If you see the message <CODE>WARN:heap_modifytuple: repl is
-\  9</CODE>, this is the problem.)
-<Li> check to see that you have the proper paths set
+your path   
+<LI> check to see that you have the proper paths set
 <LI> check that the <I>postgres</I> user owns the proper files
 </UL><P>
 
@@ -848,15 +844,23 @@ this:
 <H4><A NAME="4.6">4.6</A>) What is the maximum size for a
 row, table, database?</H4><P>
 
-Rows are limited to 8K bytes, but this can be changed by editing
-<I>include/config.h</I> and changing <SMALL>BLCKSZ.</SMALL> To use attributes
-larger than 8K, you can also use the large object interface.<P>
+These are the limits:
 
-Rows do not cross 8k boundaries so a 5k row will require 8k of
-storage.<P>
+<PRE>
+Maximum size for a database? 	         unlimited (60GB databases exist)
+Maximum size for a table?                unlimited on all operating systems
+Maximum size for a row?                  8k, configurable to 32k
+Maximum number of rows in a table?	 unlimited
+Maximum number of columns table?         unlimited
+Maximun number of indexes on a table?	 unlimited
+</PRE>
+
+To change the maximum row size, edit <I>include/config.h</I> and change
+<SMALL>BLCKSZ.</SMALL> To use attributes larger than 8K, you can also
+use the large object interface.<P>
+
+Row length limit will be removed in 7.1.<P>
 
-Table and database sizes are unlimited.  There are many databases that
-are tens of gigabytes, and probably some that are hundreds.
 
 <H4><A NAME="4.7">4.7</A>)How much database disk space is required to
 store data from a typical flat file?<BR></H4><P>
@@ -1056,7 +1060,8 @@ Similarly, you could retrieve the just-assigned SERIAL value with the <I>currval
 </PRE>
 Finally, you could use the <A HREF="#4.17">oid</A> returned from the INSERT statement to lookup the default value, though this is probably the least portable approach.  In perl, using DBI with Edmund Mergl's DBD::Pg module, the oid value is made available via $sth->{pg_oid_status} after $sth->execute().
 
-<H4><A NAME="4.16.3">4.16.3</A>) Wouldn't use of currval() and nextval() lead to a race condition with other concurrent backend processes?</H4><P>
+<H4><A NAME="4.16.3">4.16.3</A>) Don't currval() and nextval() lead to a race condition with other
+concurrent backend processes?</H4><P>
 
 No.  That has been handled by the backends.
 
@@ -1232,4 +1237,3 @@ have to do a <I>make clean</I> and then another <I>make.</I><P>
 </BODY>
 </HTML>
 
-
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index f790e164404..b582e9f911f 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,10 +1,70 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.49 2000/05/08 23:56:50 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.50 2000/06/01 05:13:18 momjian Exp $
 -->
 
  <chapter id="release">
   <title>Release Notes</title>
 
+<sect1>
+<title>Release 7.0.1</title>
+<!--
+<docinfo>
+<authorgroup>
+<author>
+<firstname>Bruce</firstname>
+<surname>Momjian</surname>
+</author>
+</authorgroup>
+<date>2000-06-01</date>
+</docinfo>
+-->
+
+<para>
+2000-06-01
+</para>
+<para>
+This is basically a cleanup release for 7.0.
+</para>
+
+
+<sect2>
+<title>Migration to v7.0.1</title>
+
+<para>
+A dump/restore is <emphasis>not</emphasis> required for those running
+7.0.
+</para>
+</sect2>
+<sect2>
+<title>Changes</title>
+
+<para>
+<programlisting>
+Fix many CLUSTER failures (Tom)
+Allow ALTER TABLE RENAME works on indexes (Tom)
+Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce)
+New configure --with-setproctitle switch to use setproctitle() (Marc, Bruce)
+Fix the off by one errors in ResultSet from 6.5.3, and more.
+jdbc ResultSet fixes (Joseph Shraibman)
+optimizer tunings (Tom)
+Fix create user for pgaccess
+Fix for UNLISTEN failure
+IRIX fixes (David Kaelbling)
+QNX fixes (Andreas Kardos)
+Reduce COPY IN lock level (Tom)
+Change libpqeasy to use PQconnectdb() style parameters (Bruce)
+Fix pg_dump to handle OID indexes (Tom)
+Fix small memory leak (Tom)
+Solaris fix for createdb/dropdb
+Fix for non-blocking connections (Alfred Perlstein)
+Fix improper recovery after RENAME TABLE failures (Tom)
+Copy pg_ident.conf.sample into /lib directory in install (Bruce)
+</programlisting>
+</para>
+</sect2>
+</sect1>
+
+
   <sect1>
    <title>Release 7.0</title>
    <!--
@@ -18,6 +78,9 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.49 2000/05/08 23:56:50 mom
   <date>2000-05-08</date>
   </docinfo>
    -->
+   <para> 
+2000-05-08
+   </para>
    <para>
     This release contains improvements in many areas, demonstrating
     the continued growth of <productname>PostgreSQL</productname>.
@@ -177,7 +240,6 @@ Ack! This isn't yet in the code?? - thomas 2000-04-30
    </sect2>
 
    <sect2>
-    <title>Detailed Change List</title>
     <para>
      <programlisting>
 Bug Fixes
@@ -517,9 +579,11 @@ New multibyte encodings
 -->
 
 <para>
+1999-10-13
+</para>
+<para>
 This is basically a cleanup release for 6.5.2.  We have added a new
-pgaccess that was missing in 6.5.2, and installed an NT-specific
-fix.
+pgaccess that was missing in 6.5.2, and installed an NT-specific fix.
 </para>
 
 
@@ -532,7 +596,7 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -560,6 +624,9 @@ Fix dumping rules on inherited tables
 -->
 
 <para>
+1999-09-15
+</para>
+<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>
@@ -574,7 +641,7 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -623,6 +690,9 @@ Updated version of pgaccess 0.98
 -->
 
 <para>
+1999-07-15
+</para>
+<para>
 This is basically a cleanup release for 6.5.  We have fixed a variety of
 problems reported by 6.5 users.
 </para>
@@ -637,7 +707,7 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -685,6 +755,9 @@ Add Win1250 (Czech) support (Pavel Behal)
 -->
 
    <para>
+1999-06-09
+</para>
+<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
@@ -903,7 +976,6 @@ Add Win1250 (Czech) support (Pavel Behal)
     </sect2>
 
    <sect2>
-    <title>Detailed Change List</title>
     <para>
      <programlisting>
 Bug Fixes
@@ -1088,6 +1160,9 @@ New install commands for plpgsql(Jan)
 -->
 
 <para>
+1999-12-20
+</para>
+<para>
 The 6.4.1 release was improperly packaged.  This also has one additional
 bug fix.
 </para>
@@ -1102,7 +1177,7 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -1129,6 +1204,9 @@ Fix for datetime constant problem on some platforms(Thomas)
 -->
 
 <para>
+1999-12-18
+</para>
+<para>
 This is basically a cleanup release for 6.4.  We have fixed a variety of
 problems reported by 6.4 users.
 </para>
@@ -1143,7 +1221,7 @@ A dump/restore is <emphasis>not</emphasis> required for those running
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -1199,6 +1277,9 @@ Upgrade to PyGreSQL 2.2(D'Arcy)
 -->
 
 <para>
+1998-10-30
+</para>
+<para>
 There are <emphasis>many</emphasis> new features and improvements in this release.
 Thanks to our developers and maintainers, nearly every aspect of the system
 has received some attention since the previous release.
@@ -1285,7 +1366,6 @@ previous release of <productname>Postgres</productname>.
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -1496,11 +1576,14 @@ new Makefile.shlib for shared library configuration(Tom)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>Tue Apr  7 16:53:16 EDT 1998</date>
+<date>1998-04-07</date>
 </docinfo>
 -->
 
 <para>
+1998-04-07
+</para>
+<para>
 This is a bugfix release for 6.3.x.
 Refer to the release notes for v6.3 for a more complete summary of new features.
 </para>
@@ -1535,7 +1618,6 @@ refer to the installation and migration instructions for v6.3.
 </para>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -1573,13 +1655,14 @@ ASSERT fixes(Bruce)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Mon Mar 23 10:21:52 EST 1998
-</date>
+<date>1998-03-23</date>
 </docinfo>
 -->
 
 <para>
+1998-03-23
+</para>
+<para>
 Summary:
 
 <itemizedlist>
@@ -1621,7 +1704,6 @@ refer to the installation and migration instructions for v6.3.
 </para>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -1668,13 +1750,14 @@ Better identify tcl and tk libs and includes(Bruce)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Sun Mar  1 14:57:30 EST 1998
-</date>
+<date>1998-03-01</date>
 </docinfo>
 -->
 
 <para>
+1998-03-01
+</para>
+<para>
 There are <emphasis>many</emphasis> new features and improvements in this release.
 Here is a brief, incomplete summary:
 
@@ -1805,7 +1888,6 @@ previous release of <productname>Postgres</productname>.
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -1988,13 +2070,14 @@ Remove un-needed malloc() calls and replace with palloc()(Bruce)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Fri Oct 17 00:01:27 EDT 1997
-</date>
+<date>1997-10-17</date>
 </docinfo>
 -->
 
 <para>
+1997-10-17
+</para>
+<para>
 v6.2.1 is a bug-fix and usability release on v6.2.
 </para>
 <para>
@@ -2047,12 +2130,11 @@ This will need to be done to every existing database, including template1.
 </para>
 </sect2>
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
-Changes in this release
------------------------
+Changes
+-------
 Allow TIME and TYPE column names(Thomas)
 Allow larger range of true/false as boolean values(Thomas)
 Support output of "now" and "current"(Thomas)
@@ -2079,13 +2161,15 @@ Trigger function for inserting user names for INSERT/UPDATE(Brook Milligan)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Thu Oct 02 12:53:46 EDT 1997
+<date>1997-10-02
 </date>
 </docinfo>
 -->
 
 <para>
+1997-10-02
+</para>
+<para>
 A dump/restore is required for those wishing to migrate data from
 previous releases of <productname>Postgres</productname>.
 </para>
@@ -2113,7 +2197,6 @@ because the COPY output format was improved from the 1.02 release.
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -2240,9 +2323,7 @@ SPI and Trigger programming guides (Vadim & D'Arcy)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Mon Jul 22 18:04:49 EDT 1997
-</date>
+<date>1997-07-22</date>
 </docinfo>
 -->
 
@@ -2251,6 +2332,9 @@ Mon Jul 22 18:04:49 EDT 1997
 <title>Migration from v6.1 to v6.1.1</title>
 
 <para>
+1997-07-22
+</para>
+<para>
 This is a minor bug-fix release. A dump/reload is not required from v6.1,
 but is required from any release prior to v6.1.
 Refer to the release notes for v6.1 for more details.
@@ -2258,12 +2342,11 @@ Refer to the release notes for v6.1 for more details.
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
-Changes in this release
------------------------
+Changes
+-------
 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
@@ -2296,13 +2379,14 @@ pg_dumpall now returns proper status, portability fix(Bruce)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Sun Jun  8 14:41:13 EDT 1997
-</date>
+<date>1997-06-08</date>
 </docinfo>
 -->
 
 <para>
+1997-06-08
+</para>
+<para>
   The regression tests have been adapted and extensively modified for the
   v6.1 release of <productname>Postgres</productname>.
 </para>
@@ -2362,7 +2446,6 @@ because the COPY output format was improved from the 1.02 release.
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -2475,13 +2558,14 @@ DG-UX, Ultrix, Irix, AIX portability fixes
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Wed Jan 29 00:19:54 EST 1997
-</date>
+<date>1997-01-29</date>
 </docinfo>
 -->
 
 <para>
+1997-01-29
+</para>
+<para>
 A dump/restore is required for those wishing to migrate data from
 previous releases of <productname>Postgres</productname>.
 </para>
@@ -2505,7 +2589,6 @@ because the COPY output format was improved from the 1.02 release.
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
 
 <para>
 <programlisting>
@@ -2634,6 +2717,8 @@ Unknown
 -->
 
 <para>
+
+Unknown
 Sorry, we stopped keeping track of changes from 1.02 to 1.09.  Some of
 the changes listed in 6.0 were actually included in the 1.02.1 to 1.09
 releases.
@@ -2650,9 +2735,7 @@ releases.
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Thu Aug  1 18:00:00 EDT 1996
-</date>
+<date>1996-08-01</date>
 </docinfo>
 -->
 
@@ -2660,6 +2743,9 @@ Thu Aug  1 18:00:00 EDT 1996
 <title>Migration from v1.02 to v1.02.1</title>
 
 <para>
+1996-08-01
+</para>
+<para>
 Here is a new migration file for 1.02.1.  It includes the 'copy' change
 and a script to convert old ascii files.
 </para>
@@ -2735,7 +2821,7 @@ create operator !~* (leftarg = varchar, rightarg = text, procedure = texticregex
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -2807,9 +2893,7 @@ Contributors (appologies to any missed)
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Fri Feb 23 18:20:36 PST 1996
-</date>
+<date>1996-02-23</date>
 </docinfo>
 -->
 
@@ -2817,6 +2901,9 @@ Fri Feb 23 18:20:36 PST 1996
 <title>Migration from v1.0 to v1.01</title>
 
 <para>
+1996-02-23
+</para>
+<para>
 The following notes are for the benefit of users who want to migrate
 databases from postgres95 1.0 to postgres95 1.01.  
 </para>
@@ -2955,7 +3042,7 @@ create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne)
 </sect2>
 
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
 <programlisting>
@@ -3006,16 +3093,17 @@ Bug fixes:
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Tue Sep  5 11:24:11 PDT 1995
-</date>
+<date>1995-09-05</date>
 </docinfo>
 -->
 
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
+1995-09-05
+</para>
+<para>
 <programlisting>
 Copyright change:
  * The copyright of <productname>Postgres</productname> 1.0 has been loosened to be freely modifiable
@@ -3071,16 +3159,17 @@ Bug fixes:
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Fri Jul 21 14:49:31 PDT 1995
-</date>
+<date>1995-07-21</date>
 </docinfo>
 -->
 
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
+1995-07-21
+</para>
+<para>
 <programlisting>
 Incompatible changes:
  * BETA-0.3 IS INCOMPATIBLE WITH DATABASES CREATED WITH PREVIOUS VERSIONS
@@ -3202,16 +3291,17 @@ New documentation:
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Thu May 25 16:54:46 PDT 1995
-</date>
+<date>1995-03-25</date>
 </docinfo>
 -->
 
 <sect2>
-<title>Detailed Change List</title>
+<title>Changes</title>
 
 <para>
+1995-03-25
+</para>
+<para>
 <programlisting>
 Incompatible changes:
  * The SQL statement for creating a database is 'CREATE DATABASE' instead
@@ -3261,13 +3351,14 @@ The following bugs have been fixed in postgres95-beta-0.02:
 <surname>Momjian</surname>
 </author>
 </authorgroup>
-<date>
-Mon May 1 19:03:10 PDT 1995
-</date>
+<date>1995-05-01</date>
 </docinfo>
 -->
 
 <para>
+1995-05-01
+</para>
+<para>
 Initial release.
 </para>
 </sect1>