max_parallel_maintenance_workers
No restart — settable per sessiontuned by pgconfiguratorcount (workers)
Parallel workers a single maintenance op (e.g. CREATE INDEX) may use.
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
Maintenance operations can be parallelized too — most notably building B-tree indexes. This caps how many workers one such operation may use (drawn from the same max_parallel_workers pool).
How to tune it
On multi-core servers, raising it (e.g. 4) makes large CREATE INDEX / REINDEX noticeably faster. Pair with a healthy maintenance_work_mem so each worker has room. It's bounded by max_parallel_workers like everything else.