autovacuum_max_workers
No restart — takes effect on reloadtuned by pgconfiguratorcount (worker processes)
How many tables autovacuum can clean at the same time.
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
autovacuum_max_workers caps how many autovacuum worker processes run concurrently, i.e. how many tables can be vacuumed or analyzed in parallel. The shared cost budget is split among the active workers, so more workers each go slower.
How to tune it
The default 3 is fine for small servers. On systems with many busy tables that fall behind, raise it (e.g. 4–8) — but also raise the overall cost limit, otherwise the same budget just spreads thinner across more workers. Current PostgreSQL applies a change on reload; older versions required a restart.