Monitor PostgreSQL transaction age even on quiet tables

Review transaction age as well as space when supervising PostgreSQL vacuum work.

Source facts

PostgreSQL 17 vacuuming protects against transaction-ID and multixact-ID wraparound as well as reclaiming dead-row space. A table can therefore need vacuuming even when it receives few updates or deletes. Aggressive vacuuming freezes eligible old row versions, including pages a normal vacuum may skip. Anti-wraparound autovacuum work can be triggered even when ordinary autovacuum is disabled. The documented age queries measure transactions since the relevant cutoff, rather than elapsed calendar days.

Source: PostgreSQL 17 — Routine Vacuuming.

Applicability

This applies to PostgreSQL 17 maintenance monitoring. It addresses transaction-age protection and does not establish universal alert thresholds or a safe reason to cancel a running vacuum.

DSE recommendation

DSE recommends showing transaction age alongside space and workload indicators in the maintenance review. Assign an owner to investigate old relations, long-lived work, and unsuccessful vacuum progress. Treat a quiet or mostly static table as part of that review rather than excluding it because its file size is stable. Have a qualified administrator evaluate interventions and application impact before changing freeze settings or terminating maintenance. Record the reason for any temporary autovacuum configuration exception.

Verification

Use a representative test database to inspect database and relation age, then observe how suitable vacuum work advances the recorded cutoff. Confirm the monitoring explains its units and identifies the oldest objects. Keep maintenance logs and unresolved blockers attached to the operational review.

Official reference

PostgreSQL 17 — Routine Vacuuming. Reviewed October 15, 2026.