From 3986d713ac2da9b99ab2655a76171f94e6c7018c Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 21 Feb 2007 16:08:05 +0000
Subject: [PATCH] Update minor release text.

---
 doc/FAQ              | 19 ++++++++++---------
 doc/src/FAQ/FAQ.html | 20 ++++++++++----------
 2 files changed, 20 insertions(+), 19 deletions(-)

diff --git a/doc/FAQ b/doc/FAQ
index 5b3c66eb3d..f144254a89 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Wed Feb 21 10:07:25 EST 2007
+   Last updated: Wed Feb 21 11:07:59 EST 2007
    
    Current maintainer: Bruce Momjian (bruce@momjian.us)
    
@@ -430,15 +430,16 @@
    
   3.6) What is the upgrade process for PostgreSQL?
   
-   The PostgreSQL team makes only bug fixes in minor releases, so, for
-   example, upgrading from 7.4.8 to 7.4.9 does not require a dump and
-   restore; merely stop the database server, install the updated
-   binaries, and restart the server.
+   The PostgreSQL team adds only bug fixes to minor releases. All users
+   should upgrade to the most recent minor release as soon as it is
+   available. While upgrades always have some risk, PostgreSQL minor
+   releases fix only frequently-encountered bugs to reduce the risk of
+   upgrading. The community considers not upgrading more risky that
+   upgrading.
    
-   All users should upgrade to the most recent minor release as soon as
-   it is available. While upgrades always have some risk, PostgreSQL
-   minor releases fix only common bugs to reduce the risk of upgrading.
-   The community considers not upgrading more risky that upgrading.
+   Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not
+   require a dump and restore; merely stop the database server, install
+   the updated binaries, and restart the server.
    
    Major releases (e.g. from 7.3 to 7.4) often change the internal format
    of system tables and data files. These changes are often complex, so
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 8a5b24a789..0a00edb209 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
   alink="#0000ff">
     <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
 
-    <P>Last updated: Wed Feb 21 10:07:25 EST 2007</P>
+    <P>Last updated: Wed Feb 21 11:07:59 EST 2007</P>
 
     <P>Current maintainer: Bruce Momjian (<A href=
     "mailto:bruce@momjian.us">bruce@momjian.us</A>)
@@ -584,16 +584,16 @@
 
     <H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>
 
-    <P>The PostgreSQL team makes only bug fixes in minor releases,
-    so, for example, upgrading from 7.4.8 to 7.4.9 does not require
-    a dump and restore;  merely stop the database server, install
-    the updated binaries, and restart the server.</P>
+    <P>The PostgreSQL team adds only bug fixes to minor releases.  All
+    users should upgrade to the most recent minor release as soon as it
+    is available.  While upgrades always have some risk, PostgreSQL minor
+    releases fix only frequently-encountered bugs to reduce the risk of
+    upgrading.  The community considers <i>not</i> upgrading more risky
+    that upgrading.</P>
 
-    <P>All users should upgrade to the most recent minor release as soon
-    as it is available.  While upgrades always have some risk, PostgreSQL
-    minor releases fix only common bugs to reduce the risk of upgrading.
-    The community considers <i>not</i> upgrading more risky that
-    upgrading.</P>
+    <P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does
+    not require a dump and restore; merely stop the database server,
+    install the updated binaries, and restart the server.</P>
 
     <P>Major releases (e.g. from 7.3 to 7.4) often change the internal
     format of system tables and data files. These changes are often complex,
-- 
2.40.0