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 72ec981fcc505e97deb786f85da4736a9011340f..a35fb491466e634a7b15754eab2d428f71706aec 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
 
 
@@ -175,9 +175,11 @@ PostgreSQL documentation
       
        
    Dump data as INSERT commands (rather
-   than COPY). This will make restoration very
-   slow, but it makes the archives more portable to other SQL database
-   management systems.
+   than COPY).  This will make restoration very slow;
+   it is mainly useful for making dumps that can be loaded into
+   non-PostgreSQL databases.  Note that
+   the restore may fail altogether if you have rearranged column order.
+   The -D option is safer, though even slower.
        
       
      
@@ -192,8 +194,9 @@ PostgreSQL documentation
    column names (INSERT INTO
    table
    (column, ...) VALUES
-   ...).  This will make restoration very slow,
-   but it is necessary if you desire to rearrange the column ordering.
+   ...).  This will make restoration very slow; it is mainly
+   useful for making dumps that can be loaded into
+   non-PostgreSQL databases.