From 6d1a0eb207cca2e70516fdffb60be7689ba4b8d7 Mon Sep 17 00:00:00 2001 From: "masao.fujii" Date: Sat, 20 Jun 2026 19:50:03 +0900 Subject: [PATCH v2 2/2] doc: Update wraparound examples to say transaction IDs Commit edee0c621de changed the runtime XID wraparound messages to use "transaction IDs" terminology, but the corresponding examples and text in maintenance.sgml still used the older XID wording. Update those documentation examples into line with the current runtime messages. Backpatch to v17, where the runtime messages were changed. --- doc/src/sgml/maintenance.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index a5a779e2e62..8043fb36625 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -675,18 +675,18 @@ SELECT datname, age(datfrozenxid) FROM pg_database; WARNING: database "mydb" must be vacuumed within 99985967 transactions DETAIL: Approximately 4.66% of transaction ID space remains before wraparound. -HINT: To avoid XID assignment failures, execute a database-wide VACUUM in that database. +HINT: To avoid transaction ID assignment failures, execute a database-wide VACUUM in that database. (A manual VACUUM should fix the problem, as suggested by the hint; but note that the VACUUM should be performed by a superuser, else it will fail to process system catalogs, which prevent it from being able to advance the database's datfrozenxid.) - If these warnings are ignored, the system will refuse to assign new XIDs once + If these warnings are ignored, the system will refuse to assign new transaction IDs once there are fewer than three million transactions left until wraparound: -ERROR: database is not accepting commands that assign new XIDs to avoid wraparound data loss in database "mydb" +ERROR: database is not accepting commands that assign new transaction IDs to avoid wraparound data loss in database "mydb" HINT: Execute a database-wide VACUUM in that database. -- 2.53.0