Autovacuum lag causes table bloat and performance degradation
warningstorageUpdated Feb 26, 2026
Technologies:
How to detect:
Default autovacuum_vacuum_scale_factor of 0.2 delays vacuum on large or high-write tables, allowing dead tuples to accumulate and cause bloat
Recommended action:
Lower autovacuum_vacuum_scale_factor to 0.05-0.1 for high-write or large tables. Increase autovacuum_max_workers to 5-10 on busy systems. Increase autovacuum_vacuum_cost_limit to 500-1000. Monitor postgresql.dead_rows, postgresql.table.dead_rows, and postgresql.vacuum.num_dead_tuples.