Commit 96879a0e authored by Noah Misch's avatar Noah Misch

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
25ec228e.  Hence, the sample was
impossible.  Back-patch to 9.5 (all supported versions).
parent e1cc25f5
...@@ -606,14 +606,13 @@ SELECT datname, age(datfrozenxid) FROM pg_database; ...@@ -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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment