| Type: | integer |
| Default: | 200 |
| Min: | 1 |
| Max: | 10000 |
| Context: | user |
| Restart: | false |
The accumulated cost that will cause the vacuuming process to sleep. The default value is 200.
On StackOverflow
- Tuning autovacuum for update heavy tables
- Postgresql: database is not accepting commands to avoid wraparound data loss
- PostgreSQL11 space reuse under high delete/update rate
- Postgresql 9.3 Autovacuum not keeping up despite aggressive settings
- is there any adverse effect on DB if I set autovacuum scale factor to zero for certain tables?