From: Tom Lane Date: Thu, 21 Oct 2004 22:49:04 +0000 (+0000) Subject: Update obsolete comments about COPY vs INSERT options, per Uwe Schroeder. X-Git-Tag: REL7_4_6~2 X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=25d1755a29ec77facafff42920403df13f218c96;p=users%2Fkgrittn%2Fpostgres.git 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 986a571b80..06d9c68ae0 100644 --- 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 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.