From: Bruce Momjian Date: Thu, 21 Aug 2008 22:25:44 +0000 (+0000) Subject: Mention that pg_dump does not dump ALTER DATABASE ... SET commands; X-Git-Tag: REL8_4_BETA1~1056 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=8875a16ee15d6bed09b8f95e813eb74cb8d22fe9;p=thirdparty%2Fpostgresql.git Mention that pg_dump does not dump ALTER DATABASE ... SET commands; backpatch to 8.3.X. Also fix markup that had just one bullet. --- diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index c8aae47b6f0..39c64af8108 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -754,22 +754,13 @@ CREATE DATABASE foo WITH TEMPLATE template0; - pg_dump has a few limitations: - - - - - When a data-only dump is chosen and the option - - - - + pg_dump has a limitation; when a + data-only dump is chosen and the option @@ -782,11 +773,14 @@ CREATE DATABASE foo WITH TEMPLATE template0; - The dump file produced by pg_dump does - not contain the statistics used by the optimizer to make query - planning decisions. Therefore, it is wise to run - ANALYZE after restoring from a dump file to - ensure good performance. + The dump file produced by pg_dump + does not contain the statistics used by the optimizer to make + query planning decisions. Therefore, it is wise to run + ANALYZE after restoring from a dump file + to ensure good performance. The dump file also does not + contain any ALTER DATABASE ... SET commands; + these settings are dumped by , + along with database users and other installation-wide settings.