From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Date: Sat, 19 Sep 2020 10:28:59 +0200
Message-ID: <36aa8aea-61b7-eb3c-263b-648e0cb117b7@2ndquadrant.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com
Subject: Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
In-Reply-To: <36aa8aea-61b7-eb3c-263b-648e0cb117b7@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox