VacuumDelay
Its a built-in PostgreSQL mechanism for throttling autovacuum I/O to avoid excessive resource consumption that could impact normal database operations
This event appears when PostgreSQL's cost-based vacuum delay feature is active. The system intentionally pauses vacuum work whenever the estimated I/O "cost" of vacuum exceeds the limits set by the configuration parameters.
Parameters
Following parameters influence the behavior of this event:
- autovacuum_vacuum_cost_delay:Reducing this value to 2ms allows autovacuum to be more aggressive in its operations.
- autovacuum_vacuum_cost_limit:Increasing the value to 1000 is general practice to let the autovacuum do more work cycle
- vacuum_cost_delay:
- vacuum_cost_limit: