The length of time, in milliseconds, that the process will sleep when the cost limit has been exceeded. The default value is zero, which disables the cost-based vacuum delay feature. Positive values enable cost-based vacuuming. Note that on many systems, the effective resolution of sleep delays is 10 milliseconds; setting
vacuum_cost_delay to a value that is not a multiple of 10 might have the same results as setting it to the next higher multiple of 10.
When using cost-based vacuuming, appropriate values for
vacuum_cost_delay are usually quite small, perhaps 10 or 20 milliseconds. Adjusting vacuum's resource consumption is best done by changing the other vacuum cost parameters.
- Postgresql: database is not accepting commands to avoid wraparound data loss
- PostgreSQL11 space reuse under high delete/update rate
- is there any adverse effect on DB if I set autovacuum scale factor to zero for certain tables?
- Postgresql 9.3 Autovacuum not keeping up despite aggressive settings
- postgresql autovacuum not working although process is running