mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Tom Lane 2004-10-21 22:48:54 +00:00
parent 12a47c6aca
commit 9eff02f5ac
1 changed files with 9 additions and 6 deletions

15
doc/src/sgml/ref/pg_dump.sgml

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.73 2004/07/13 02:59:49 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.74 2004/10/21 22:48:54 tgl Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -175,9 +175,11 @@ PostgreSQL documentation
<listitem> <listitem>
<para> <para>
Dump data as <command>INSERT</command> commands (rather Dump data as <command>INSERT</command> commands (rather
than <command>COPY</command>). This will make restoration very than <command>COPY</command>). This will make restoration very slow;
slow, but it makes the archives more portable to other SQL database it is mainly useful for making dumps that can be loaded into
management systems. 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> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -192,8 +194,9 @@ PostgreSQL documentation
column names (<literal>INSERT INTO column names (<literal>INSERT INTO
<replaceable>table</replaceable> <replaceable>table</replaceable>
(<replaceable>column</replaceable>, ...) VALUES (<replaceable>column</replaceable>, ...) VALUES
...</literal>). This will make restoration very slow, ...</literal>). This will make restoration very slow; it is mainly
but it is necessary if you desire to rearrange the column ordering. useful for making dumps that can be loaded into
non-<productname>PostgreSQL</productname> databases.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>