From 9eff02f5ac374466e37d63ed4361496a4aeef0d6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 21 Oct 2004 22:48:54 +0000 Subject: [PATCH] Update obsolete comments about COPY vs INSERT options, per Uwe Schroeder. --- doc/src/sgml/ref/pg_dump.sgml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 72ec981fcc..a35fb49146 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.