OSSForks/postgres
1
0
Fork 0
mirror of https://github.com/zebrajr/postgres.git synced 2025-12-07 00:20:24 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix documentation of "must be vacuumed within" warning.

Browse Source 
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
25ec228ef7.  Hence, the sample was
impossible.  Back-patch to 9.5 (all supported versions).
This commit is contained in:
Noah Misch 2020-06-27 22:05:04 -07:00
parent e1cc25f59a
commit 96879a0efb
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/sgml/maintenance.sgml
View File

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