Update obsolete comments about COPY vs INSERT options, per Uwe Schroeder.

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 35e46fd65839b7332c5dfcada87fac13f5bf8b32..646682c3af3ad45d488a01984cf38fe09d27f87a 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -175,9 +175,11 @@ PostgreSQL documentation
       <listitem>
        <para>
        Dump data as <command>INSERT</command> commands (rather
-       than <command>COPY</command>). This will make restoration very
-       slow, but it makes the archives more portable to other SQL database
-       management systems.
+       than <command>COPY</command>).  This will make restoration very slow;
+       it is mainly useful for making dumps that can be loaded into
+       non-<productname>PostgreSQL</productname> databases.  Note that
+       the restore may fail altogether if you have rearranged column order.
+       The <option>-D</option> option is safer, though even slower.
        </para>
       </listitem>
      </varlistentry>
@@ -192,8 +194,9 @@ PostgreSQL documentation
        column names (<literal>INSERT INTO
        <replaceable>table</replaceable>
        (<replaceable>column</replaceable>, ...) VALUES
-       ...</literal>).  This will make restoration very slow,
-       but it is necessary if you desire to rearrange the column ordering.
+       ...</literal>).  This will make restoration very slow; it is mainly
+       useful for making dumps that can be loaded into
+       non-<productname>PostgreSQL</productname> databases.
        </para>
       </listitem>
      </varlistentry>