Allow pg_dumpall to work with previous releases again. Don't pass the -c

option down to pg_dump, where it's useless, and clarify the meaning of -c
in the documentation.

2 files changed, 27 insertions, 22 deletions

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 5b5759a1d43..ae1bb7b4ea5 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.50 2002/09/06 21:58:36 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.51 2002/09/07 16:14:33 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -289,14 +289,17 @@ PostgreSQL documentation
       <term><option>--ignore-version</></term>
       <listitem>
        <para>
-        Ignore version mismatch between <command>pg_dump</command>
-	and the database server.  Since <command>pg_dump</command>
-	knows a great deal about system catalogs, any given version of
-	<command>pg_dump</command> is only intended to work with
-	the corresponding release of the database server.  Use this option
-	if you need to override the version check (and if
-	<command>pg_dump</command> then fails, don't
-	say you weren't warned).
+        Ignore version mismatch between
+        <application>pg_dump</application> and the database server.
+       </para>
+
+       <para>
+        <application>pg_dump</application> can handle databases from
+        previous releases of PostgreSQL, but very old versions are not
+        supported anymore (currently prior to 7.0).  Use this option
+        if you need to override the version check (and if
+        <application>pg_dump</application> then fails, don't say you
+        weren't warned).
        </para>
       </listitem>
      </varlistentry>
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index e6f156dcc6e..2439d040866 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.33 2002/09/05 22:05:50 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.34 2002/09/07 16:14:33 petere Exp $
 PostgreSQL documentation
 -->
 
@@ -79,13 +79,12 @@ PostgreSQL documentation
 
     <variablelist>
      <varlistentry>
-      <term>-c, --clean</term>
+      <term><option>-c</option></term>
+      <term><option>--clean</option></term>
       <listitem>
        <para>
-	Include SQL commands to clean (drop) database objects before
-	recreating them.  (This option is fairly useless, since the
-	output script expects to create the databases themselves;
-	they would always be empty upon creation.)
+	Include SQL commands to clean (drop) the databases before
+	recreating them.
        </para>
       </listitem>
      </varlistentry>
@@ -120,10 +119,11 @@ PostgreSQL documentation
      </varlistentry>
 
      <varlistentry>
-      <term>-g, --globals-only</term>
+      <term><option>-g</option></term>
+      <term><option>--globals-only</option></term>
       <listitem>
        <para>
-	Only dump global objects (users and groups), no databases.
+	Dump only global objects (users and groups), no databases.
        </para>
       </listitem>
      </varlistentry>
@@ -135,11 +135,13 @@ PostgreSQL documentation
        <para>
         Ignore version mismatch between
         <application>pg_dumpall</application> and the database server.
-        Since <application>pg_dumpall</application> knows a great deal
-        about system catalogs, any given version of
-        <application>pg_dumpall</application> is only intended to work
-        with the corresponding release of the database server.  Use
-        this option if you need to override the version check (and if
+       </para>
+
+       <para>
+        <application>pg_dumpall</application> can handle databases
+        from previous releases of PostgreSQL, but very old versions
+        are not supported anymore (currently prior to 7.0).  Use this
+        option if you need to override the version check (and if
         <application>pg_dumpall</application> then fails, don't say
         you weren't warned).
        </para>