Dead-row pressure
Maintenance audit
Postgres table bloat and autovacuum signal check
Database Optimization Tool highlights table-health signals that small teams can review before changing autovacuum settings or scheduling maintenance.
Autovacuum timestamps
Relation size
Human-reviewed maintenance plan
Dead-row and table-size signals
The collector reviews estimated live rows, estimated dead rows, table size, index size, and scan behavior to find maintenance candidates.
Autovacuum drift
Missing or stale autovacuum/analyze timestamps can indicate tables that need closer inspection before they become query latency problems.
Review-first operations
The report avoids automatic VACUUM or configuration changes. It proposes diagnostics and scheduling notes so humans decide the production plan.
Related topics
RelatedLinks for neighboring audit problems
Use these focused guides to compare query pressure, index decisions, and maintenance signals before you change production.
FAQ
Frequently asked questions
These answers stay inside the current Database Optimization Tool product boundary: read-only collection, evidence-gated findings, and human-reviewed next steps.
Is this a live bloat monitor?
No. The page describes a read-only audit workflow that reviews exported signals, not a continuously running monitoring agent.
Can the report tell me to run VACUUM FULL immediately?
No. The workflow is review-first and prefers maintenance history, workload validation, and safer scheduling before disruptive operations.
How does autovacuum drift show up?
Stale or missing autovacuum and analyze timestamps, combined with dead-row pressure, are treated as warning signals that need human review.
Which guide should I read next if dead rows are rising?
Read the autovacuum health page first, then compare it with the slow query and temp write guides if latency is also rising.