11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.73 2004/07/13 02:59:49 momjian Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.74 2004/10/21 22:48:54 tgl Exp $
33PostgreSQL documentation
44-->
55
@@ -175,9 +175,11 @@ PostgreSQL documentation
175175 <listitem>
176176 <para>
177177Dump data as <command>INSERT</command> commands (rather
178- than <command>COPY</command>). This will make restoration very
179- slow, but it makes the archives more portable to other SQL database
180- management systems.
178+ than <command>COPY</command>). This will make restoration very slow;
179+ it is mainly useful for making dumps that can be loaded into
180+ non-<productname>PostgreSQL</productname> databases. Note that
181+ the restore may fail altogether if you have rearranged column order.
182+ The <option>-D</option> option is safer, though even slower.
181183 </para>
182184 </listitem>
183185 </varlistentry>
@@ -192,8 +194,9 @@ PostgreSQL documentation
192194column names (<literal>INSERT INTO
193195<replaceable>table</replaceable>
194196(<replaceable>column</replaceable>, ...) VALUES
195- ...</literal>). This will make restoration very slow,
196- but it is necessary if you desire to rearrange the column ordering.
197+ ...</literal>). This will make restoration very slow; it is mainly
198+ useful for making dumps that can be loaded into
199+ non-<productname>PostgreSQL</productname> databases.
197200 </para>
198201 </listitem>
199202 </varlistentry>