postgres.git / summary / log / commit / refs

commit    b86be844a40c439e44ea6fc974df37b7c2c9c832
Author:   Noah Misch <noah@leadboat.com>
Date:     Sun Jun 28 05:05:04 2020 +0000
First released in: 14.0, 9.5.23, 9.6.19, 10.14, 11.9, 12.4, 13.0

    Fix documentation of "must be vacuumed within" warning.
    
    Warnings start 10M transactions before xidStopLimit, which is 11M
    transactions before wraparound.  The sample WARNING output showed a
    value greater than 11M, and its HINT message predated commit
    25ec228ef760eb91c094cc3b6dea7257cc22ffb5.  Hence, the sample was
    impossible.  Back-patch to 9.5 (all supported versions).


 doc/src/sgml/maintenance.sgml | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 39075ea8f33..612e4cb2008 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -606,14 +606,13 @@ SELECT datname, age(datfrozenxid) FROM pg_database;
    </para>
 
    <para>
-    If for some reason autovacuum fails to clear old XIDs from a table,
-    the system will begin to emit warning messages like this when the
-    database's oldest XIDs reach ten million transactions from the wraparound
-    point:
+    If for some reason autovacuum fails to clear old XIDs from a table, the
+    system will begin to emit warning messages like this when the database's
+    oldest XIDs reach eleven million transactions from the wraparound point:
 
 <programlisting>
-WARNING:  database "mydb" must be vacuumed within 177009986 transactions
-HINT:  To avoid a database shutdown, execute a database-wide VACUUM in "mydb".
+WARNING:  database "mydb" must be vacuumed within 10985967 transactions
+HINT:  To avoid a database shutdown, execute a database-wide VACUUM in that database.
 </programlisting>
 
     (A manual <command>VACUUM</command> should fix the problem, as suggested by the


[parent: e5f63db99551]