| Type: | real |
| Default: | 2 (2ms) |
| Min: | -1 (-1) |
| Max: | 100 (100ms) |
| Unit: | milliseconds (ms) |
| Context: | sighup |
| Restart: | false |
Specifies the cost delay value that will be used in automatic VACUUM operations. If -1 is specified, the regular vacuum_cost_delay value will be used. If this value is specified without units, it is taken as milliseconds. The default value is 2 milliseconds. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters.
Recommendations
If autovacuum is having too much of a performance impact on running queries, you might want to increase this setting to 50ms. However, this will also cause individual vacuum tasks to take longer.
On StackOverflow
On pgsql-hackers
- Re: Track the amount of time waiting due to cost_delay
- Re: bgwrite process is too lazy
- A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a explosive replication lag. Oh my.
- Re: Allow non-superuser to cancel superuser tasks.
- Re: Eagerly scan all-visible pages to amortize aggressive vacuum