Skip to content

Commit 3275426

Browse files
committed
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.
1 parent 2899e3d commit 3275426

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/maintenance.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -492,8 +492,8 @@
492492
will take more space, because it must store the commit status of all
493493
transactions back to the <varname>autovacuum_freeze_max_age</> horizon.
494494
The commit status uses two bits per transaction, so if
495-
<varname>autovacuum_freeze_max_age</> is set to its maximum allowed value of
496-
a little less than two billion, <filename>pg_clog</> can be expected to
495+
<varname>autovacuum_freeze_max_age</> is set to its maximum allowed
496+
value of two billion, <filename>pg_clog</> can be expected to
497497
grow to about half a gigabyte. If this is trivial compared to your
498498
total database size, setting <varname>autovacuum_freeze_max_age</> to
499499
its maximum allowed value is recommended. Otherwise, set it depending

0 commit comments

Comments
 (0)