Use the Missing Vacuum History health check in Mini DBA to review PostgreSQL configuration, metadata, and monitoring signals before they become active alerts.
This health check looks for PostgreSQL maintenance signals that keep tables healthy, plans accurate, and transaction ID wraparound risk under control.
PostgreSQL maintenance issues can degrade plans and availability gradually, then fail suddenly. This check keeps routine maintenance visible.
Review the affected objects and workload before changing indexes. Create or rebuild only where the workload justifies it, remove unused indexes carefully, and update statistics or maintenance routines so the condition does not return.
Keep a short note explaining why the check failed, what was changed, who owns the follow-up, and whether an exception was approved.
Prioritize it according to workload criticality and trend. A one-off warning may be scheduled maintenance, but repeated failures usually deserve an owner and target date.
Prevent repeat failures by assigning an owner, documenting the expected configuration, and reviewing the check after upgrades, migrations, or major application releases.
Add this page to the operational runbook for PostgreSQL environments where the check repeatedly fails. Record local thresholds, approved exceptions, escalation contacts, and the expected review interval so the next administrator can act quickly without rediscovering the same context.