VACUUM PARALLEL option vs. max_parallel_maintenance_workers - Mailing list pgsql-hackers

From Peter Eisentraut
Subject VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Date
Msg-id 36aa8aea-61b7-eb3c-263b-648e0cb117b7@2ndquadrant.com
Whole thread Raw
Responses Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
List pgsql-hackers
If I read the code correctly, the VACUUM PARALLEL option is capped by 
the active max_parallel_maintenance_workers setting.  So if I write 
VACUUM (PARALLEL 5), it will still only do 2 by default.  Is that 
correct?  The documentation (VACUUM man page) seems to indicate a 
different behavior.

I haven't been able to set up something to test or verify this either way.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Resetting spilled txn statistics in pg_stat_replication
Next
From: Amit Kapila
Date:
Subject: Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers