| Type: | integer |
| Default: | 1 |
| Min: | 0 |
| Max: | 10000 |
| Context: | user |
| Restart: | false |
The estimated cost for vacuuming a buffer found in the shared buffer cache. It represents the cost to lock the buffer pool, lookup the shared hash table and scan the content of the page. The default value is one.
On StackOverflow
- vacuum_cost_page_miss set to zero
- Postgresql: database is not accepting commands to avoid wraparound data loss
- Autovacuum postgresql 11 with big tables and many updates
- 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?