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.

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index caf968ad06fcbc447b988d196870477972229bcd..d7ca37c5f36c4e8ccbfce8d529a01220a9dbf62d 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -450,8 +450,8 @@
     will take more space, because it must store the commit status of all
     transactions back to the autovacuum_freeze_max_age horizon.
     The commit status uses two bits per transaction, so if
-    autovacuum_freeze_max_age is set to its maximum allowed value of
-    a little less than two billion, pg_clog can be expected to
+    autovacuum_freeze_max_age is set to its maximum allowed
+    value of two billion, pg_clog can be expected to
     grow to about half a gigabyte.  If this is trivial compared to your
     total database size, setting autovacuum_freeze_max_age to
     its maximum allowed value is recommended.  Otherwise, set it depending