Skip to content
Snippets Groups Projects
Commit fa41f294 authored by Kevin Grittner's avatar Kevin Grittner
Browse files

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.
parent 97d8ad17
No related branches found
No related tags found
No related merge requests found
...@@ -492,8 +492,8 @@ ...@@ -492,8 +492,8 @@
will take more space, because it must store the commit status of all will take more space, because it must store the commit status of all
transactions back to the <varname>autovacuum_freeze_max_age</> horizon. transactions back to the <varname>autovacuum_freeze_max_age</> horizon.
The commit status uses two bits per transaction, so if The commit status uses two bits per transaction, so if
<varname>autovacuum_freeze_max_age</> is set to its maximum allowed value of <varname>autovacuum_freeze_max_age</> is set to its maximum allowed
a little less than two billion, <filename>pg_clog</> can be expected to value of two billion, <filename>pg_clog</> can be expected to
grow to about half a gigabyte. If this is trivial compared to your grow to about half a gigabyte. If this is trivial compared to your
total database size, setting <varname>autovacuum_freeze_max_age</> to total database size, setting <varname>autovacuum_freeze_max_age</> to
its maximum allowed value is recommended. Otherwise, set it depending its maximum allowed value is recommended. Otherwise, set it depending
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment