diff options
| author | Kevin Grittner <kgrittn@postgresql.org> | 2012-09-16 12:19:37 -0500 |
|---|---|---|
| committer | Kevin Grittner <kgrittn@postgresql.org> | 2012-09-16 12:19:37 -0500 |
| commit | fa41f294f6c93af78e08b3cbb976586a6804c8f4 (patch) | |
| tree | 6974f25718114b15dee01d49e83646b6b31ba076 | |
| parent | 97d8ad170f7a118ed1237b00e6140ec892c11c89 (diff) | |
Fix documentation reference to maximum allowed for autovacuum_freeze_max_age.
The documentation mentioned setting autovacuum_freeze_max_age to
"its maximum allowed value of a little less than two billion".
This led to a post asking about the exact maximum allowed value,
which is precisely two billion, not "a little less".
Based on question by Radovan Jablonovsky. Backpatch to 8.3.
| -rw-r--r-- | doc/src/sgml/maintenance.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index fb705b2cbb6..84b452d16d4 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -492,8 +492,8 @@ will take more space, because it must store the commit status of all transactions back to the <varname>autovacuum_freeze_max_age</> horizon. The commit status uses two bits per transaction, so if - <varname>autovacuum_freeze_max_age</> is set to its maximum allowed value of - a little less than two billion, <filename>pg_clog</> can be expected to + <varname>autovacuum_freeze_max_age</> is set to its maximum allowed + value of two billion, <filename>pg_clog</> can be expected to grow to about half a gigabyte. If this is trivial compared to your total database size, setting <varname>autovacuum_freeze_max_age</> to its maximum allowed value is recommended. Otherwise, set it depending |