Add mention that everyone should upgrade to minor releases.

diff --git a/doc/FAQ b/doc/FAQ
index 1494975cbfadf12b25739d325321143927691d5b..4a35166c14c90e7f38330eccbef3549714dbe412 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
 
                 Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Thu May 18 23:52:32 EDT 2006
+   Last updated: Tue May 23 11:22:06 EDT 2006
    
    Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
    
@@ -19,7 +19,7 @@
    1.3) What is the copyright of PostgreSQL?
    1.4) What platforms does PostgreSQL support?
    1.5) Where can I get PostgreSQL?
-   1.6) What is the latest release?
+   1.6) What is the most recent release?
    1.7) Where can I get support?
    1.8) How do I submit a bug report?
    1.9) How do I find out about known bugs or missing features?
@@ -168,7 +168,7 @@
    Via web browser, use http://www.postgresql.org/ftp/, and via ftp, use
    ftp://ftp.PostgreSQL.org/pub/.
    
-  1.6) What is the latest release?
+  1.6) What is the most recent release?
   
    The latest release of PostgreSQL is version 8.1.4.
    
@@ -416,13 +416,20 @@
   3.6) Why do I need to do a dump and restore to upgrade between major
   PostgreSQL releases?
   
-   The PostgreSQL team makes only small changes between minor releases,
-   so upgrading from 7.4.0 to 7.4.1 does not require a dump and restore.
-   However, 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 we don't maintain backward compatibility for data
-   files. A dump outputs data in a generic format that can then be loaded
-   in using the new internal format.
+   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.
+   
+   All users should upgrade to the most recent minor release as soon as
+   it is available. While every upgrade has some risk, PostgreSQL minor
+   releases are designed to fix only common bugs with the least risk. The
+   community considers not upgrading more risky that upgrading.
+   
+   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
+   we don't maintain backward compatibility for data files. A dump/reload
+   of the database is required for major upgrades.
    
   3.7) What computer hardware should I use?
   

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 35a33e9fdf4a7f56ec496f3410b9946ec54ca498..c255e51919c0010f1273722cc368d4d45144a955 100644 (file)
--- 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: Thu May 18 23:52:32 EDT 2006</P>
+    <P>Last updated: Tue May 23 11:22:06 EDT 2006</P>
 
     <P>Current maintainer: Bruce Momjian (<A href=
     "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -31,7 +31,7 @@
      <A href="#item1.3">1.3</A>) What is the copyright of PostgreSQL?<BR>
      <A href="#item1.4">1.4</A>) What platforms does PostgreSQL support?<BR>
      <A href="#item1.5">1.5</A>) Where can I get PostgreSQL?<BR>
-     <A href="#item1.6">1.6</A>) What is the latest release?<BR>
+     <A href="#item1.6">1.6</A>) What is the most recent release?<BR>
      <A href="#item1.7">1.7</A>) Where can I get support?<BR>
      <A href="#item1.8">1.8</A>) How do I submit a bug report?<BR>
      <A href="#item1.9">1.9</A>) How do I find out about known bugs or
@@ -218,7 +218,7 @@
     <A href="ftp://ftp.PostgreSQL.org/pub/">
     ftp://ftp.PostgreSQL.org/pub/</A>.</P>
 
-    <H3 id="item1.6">1.6) What is the latest release?</H3>
+    <H3 id="item1.6">1.6) What is the most recent release?</H3>
 
     <P>The latest release of PostgreSQL is version 8.1.4.</P>
 
@@ -573,13 +573,21 @@
     <H3 id="item3.6">3.6) Why do I need to do a dump and restore
     to upgrade between major PostgreSQL releases?</H3>
 
-    <P>The PostgreSQL team makes only small changes between minor releases,
-    so upgrading from 7.4.0 to 7.4.1 does not require a dump and restore.
-    However, major releases (e.g. from 7.3 to 7.4) often change the internal
+    <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>All users should upgrade to the most recent minor release as
+    soon as it is available.  While every upgrade has some risk,
+    PostgreSQL minor releases are designed to fix only common bugs
+    with the least risk.  The community considers <i>not</i> upgrading
+    more risky that upgrading.</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,
-    so we don't maintain backward compatibility for data files. A dump outputs
-    data in a generic format that can then be loaded in using the new internal
-    format.</P>
+    so we don't maintain backward compatibility for data files. A dump/reload
+    of the database is required for major upgrades.</P>
 
     <H3 id="item3.7">3.7) What computer hardware should I use?</H3>