autovacuum_vacuum_insert_scale_factor
No restart — takes effect on reloadtuned by pgconfiguratorPostgreSQL 13+ratio (fraction of table)
Triggers vacuum on insert-heavy tables that have few dead rows.
What pgconfigurator would set
32 GB · 8 vCPU · NVMe · OLTP
Computing…
Tune for your exact server → /tunecomputed in your browser · nothing uploaded
What it does
Added in PostgreSQL 13, this triggers an autovacuum based on inserted (not just dead) rows, so append-mostly tables get vacuumed to set the visibility map and freeze tuples — even though they have little to clean up.
How to tune it
The default 0.2 is reasonable. On large insert-only tables (logs, events, time-series), lowering it keeps the visibility map fresh so Index Only Scans stay fast and freezing happens steadily instead of in one giant wraparound vacuum later.