diff options
| author | Noah Misch | 2020-06-28 05:05:04 +0000 |
|---|---|---|
| committer | Noah Misch | 2020-06-28 05:05:04 +0000 |
| commit | 96879a0efb65b9cde0a688201516633aa79fd5b0 (patch) | |
| tree | ea427a54d7f8d50a6b8d0f5d396782e43faff73a | |
| parent | e1cc25f59a8a90d821aaf894e1691575ed94454e (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).
| -rw-r--r-- | doc/src/sgml/maintenance.sgml | 11 |
1 files 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 |