From dd8d1b1fbdb2a9fa6bf867ea38e877b0ca136059 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 15 Apr 2006 18:11:48 +0000
Subject: [PATCH] Document that pg_dump -d/-D prevents invalid data from
 canceling the entire table load.

---
 doc/src/sgml/ref/pg_dump.sgml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 998dc670c26..7ee043d9ef7 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.81 2005/11/01 21:09:50 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.81.2.1 2006/04/15 18:11:48 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -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>