Find tables autovacuum keeps skipping
A table with autovacuum_enabled=false is never cleaned, no matter how much it bloats. A catalog query surfaces the ones with dead tuples and autovacuum disabled, here audit_trail, quietly turned off.
Problem
What you're actually looking at
The symptom as it shows up on a real server.
Someone disables autovacuum on a table (for a bulk load, a migration, a misguided tuning attempt) and never re-enables it. The table then bloats without limit because autovacuum simply skips it, and nothing warns you.
Meridian's audit_trail is bloating and never shows a last_autovacuum time. A catalog query reveals its reloptions carry autovacuum_enabled=false, cleanup was turned off and forgotten.
Simple terms
Sometimes autovacuum gets switched off on a single table, for a bulk load or a migration, and then nobody turns it back on. That table quietly bloats forever, because autovacuum simply skips it and nothing warns you. A quick catalog query lists any table that has dead rows and autovacuum disabled, so you can spot the one that was turned off and forgotten.
Full runbook for this incident
- The full identify checklist, the exact signals that tell you it's this incident
- Every diagnostic query; lab output is attached only to the steps we actually captured
- The resolution path and the pitfalls that make it worse
- Mitigation steps to stop it recurring, plus a verify-you're-done query
Card required. Cancel before day 7 and you are not charged.
More in this category
Other Vacuum & bloat runbooks
Neighbouring incidents that share the same diagnostic surface.
Connected
How this connects to the rest of the library
A live view of this page's real cross-references, what explains it, what fixes it, what to tune, and where to go next. Every link is an authored relationship, not a guess.
Fixes these errors
Need the full procedure?
Pro runbooks finish the incident path
Free runbooks teach the shape. Pro opens the full step transcript, edge cases, and prevention depth.