postgres.git / summary / log / commit / refs

commit    17ddb7d65b49422a6b6bc153896b4e2350dbda75
Author:   Kevin Grittner <kgrittn@postgresql.org>
Date:     Sun Sep 16 17:21:12 2012 +0000
First released in: 9.3.0, 8.3.21, 8.4.14, 9.0.10, 9.1.6, 9.2.1

    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 caf968ad06f..d7ca37c5f36 100644
--- 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 <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


[parent: 3d3218aa3d4a]