summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2020-06-27 22:05:04 -0700
committerNoah Misch <noah@leadboat.com>2020-06-27 22:05:08 -0700
commit52b0f8875c14f17c5c95767ae9ad7f4e32cb865d (patch)
tree527b3431a4e2047275be1e679526d6e74965ecff /doc/src
parent441d4b5a3779ce4b7302d2a05b97e4fb01cc7fb7 (diff)
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).
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/maintenance.sgml11
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 63ddcae5829..198b217ecf3 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</> should fix the problem, as suggested by the