VACUUM PARALLEL option vs. max_parallel_maintenance_workers

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Date: 2020-09-19 08:28:59
Message-ID: 36aa8aea-61b7-eb3c-263b-648e0cb117b7@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-09-19 09:37:47 Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Previous Message Amit Kapila 2020-09-19 08:18:40 Re: Resetting spilled txn statistics in pg_stat_replication