From fa41f294f6c93af78e08b3cbb976586a6804c8f4 Mon Sep 17 00:00:00 2001
From: Kevin Grittner <kgrittn@postgresql.org>
Date: Sun, 16 Sep 2012 12:19:37 -0500
Subject: [PATCH] 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.
---
doc/src/sgml/maintenance.sgml | 4 ++--
1 file 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
--
GitLab