Document that pg_dump -d/-D prevents invalid data from canceling the

entire table load.

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index b2c6f6b30164e1ecaac2f7555f28d29aeaeea578..99afb5cc4c8d05e209046b4dc1e8a8780dec9726 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -173,6 +173,9 @@ PostgreSQL documentation
         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.
+        Also, while this option generates errors for invalid data, 
+        it allows other <command>INSERT</command>s to continue loading
+        data into the table.
        </para>
       </listitem>
      </varlistentry>
@@ -190,6 +193,9 @@ PostgreSQL documentation
         ...</literal>).  This will make restoration very slow; it is mainly
         useful for making dumps that can be loaded into
         non-<productname>PostgreSQL</productname> databases.
+        Also, while this option generates errors for invalid data, 
+        it allows other <command>INSERT</command>s to continue loading
+        data into the table.
        </para>
       </listitem>
      </varlistentry>