c8h4/postgresql
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add note about pg_autovacuum settings not being saved on a dump, per

Browse source 
Robert Treat.
This commit is contained in:
Alvaro Herrera 2005-09-16 03:12:32 +00:00
parent dc06734a72
commit 3e579cf3c0
1 changed files with 13 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/src/sgml/maintenance.sgml
View file

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.46 2005/09/13 01:51:18 alvherre Exp $
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.47 2005/09/16 03:12:32 alvherre Exp $
-->
<chapter id="maintenance">
@ -542,10 +542,20 @@ vacuum threshold = vacuum base threshold + vacuum scale factor * number of tuple
values, the <varname>vacuum_cost_limit</varname> and
<varname>vacuum_cost_delay</varname> values will be used instead.
The other parameter, <structname>pg_autovacuum</>.<structfield>enabled</>,
can be used to instruct the autovacuum daemon to skip any particular table
by setting it to <literal>false</literal>.
can be used to instruct the autovacuum daemon to skip any particular table
by setting it to <literal>false</literal>.
</para>
<note>
<para>
The contents of the <structname>pg_autovacuum</structname> system
catalog are currently not saved in database dumps created by
the tools <command>pg_dump</command> and <command>pg_dumpall</command>.
If you need to preserve them across a dump/reload cycle, make sure you
dump the catalog manually.
</para>
</note>
</sect2>
</sect1>