From c107c35df3ae62444497dbba1d60e591c8d0d436 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 24 Aug 2010 13:32:25 +0000 Subject: [PATCH] Update autovacuum_freeze_max_age documentation to mention that the default is low because of pg_clog file removal. Backpatch to 9.0.X. --- doc/src/sgml/config.sgml | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 06ff79a417..d1ad1af6af 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -4150,12 +4150,16 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the maximum age (in transactions) that a table's pg_class.relfrozenxid field can - attain before a VACUUM operation is forced to allow removal - of old files from the pg_clog subdirectory and prevent - transaction ID wraparound within the table. Note that the system - will launch autovacuum processes to prevent wraparound even when - autovacuum is otherwise disabled. - The default is 200 million transactions. + attain before a VACUUM operation is forced + to prevent transaction ID wraparound within the table. + Note that the system will launch autovacuum processes to + prevent wraparound even when autovacuum is otherwise disabled. + + + + Vacuum also allows removal of old files from the + pg_clog subdirectory, which is why the default + is a relatively low 200 million transactions. This parameter can only be set at server start, but the setting can be reduced for individual tables by changing storage parameters.