rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mention that pg_dump does not dump ALTER DATABASE ... SET commands; 

backpatch to 8.3.X. Also fix markup that had just one bullet.
This commit is contained in:
Bruce Momjian 2008-08-21 22:25:44 +00:00
parent edb6a4c02a
commit 8875a16ee1
1 changed files with 16 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
doc/src/sgml/ref/pg_dump.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.103 2008/07/20 18:43:30 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.104 2008/08/21 22:25:44 momjian Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -754,22 +754,13 @@ CREATE DATABASE foo WITH TEMPLATE template0;
</para> </para>
<para> <para>
<application>pg_dump</application> has a few limitations: <application>pg_dump</application> has a limitation; when a
data-only dump is chosen and the option <option>--disable-triggers</>
<itemizedlist> is used, <application>pg_dump</application> emits commands
<listitem> to disable triggers on user tables before inserting the data
<para> and commands to re-enable them after the data has been
When a data-only dump is chosen and the option inserted. If the restore is stopped in the middle, the system
<option>--disable-triggers</> is used, catalogs might be left in the wrong state.
<application>pg_dump</application> emits commands to disable
triggers on user tables before inserting the data and commands
to re-enable them after the data has been inserted. If the
restore is stopped in the middle, the system catalogs might be
left in the wrong state.
</para>
</listitem>
</itemizedlist>
</para> </para>
<para> <para>
@ -782,11 +773,14 @@ CREATE DATABASE foo WITH TEMPLATE template0;
</para> </para>
<para> <para>
The dump file produced by <application>pg_dump</application> does The dump file produced by <application>pg_dump</application>
not contain the statistics used by the optimizer to make query does not contain the statistics used by the optimizer to make
planning decisions. Therefore, it is wise to run query planning decisions. Therefore, it is wise to run
<command>ANALYZE</command> after restoring from a dump file to <command>ANALYZE</command> after restoring from a dump file
ensure good performance. to ensure good performance. The dump file also does not
contain any <command>ALTER DATABASE ... SET</> commands;
these settings are dumped by <xref linkend="app-pg-dumpall">,
along with database users and other installation-wide settings.
</para> </para>
<para> <para>