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

From Peter Eisentraut
Subject Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Date
Msg-id 5a8b1b58-30b6-cd9a-5a37-75f1da063429@2ndquadrant.com
Whole thread Raw
In response to Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2020-09-19 11:37, Amit Kapila wrote:
> I think we can change the documentation for parallel option to explain
> it better. How about: "Perform index vacuum and index cleanup phases
> of VACUUM in parallel using integer background workers (for the
> details of each vacuum phase, please refer to Table 27.37). The number
> of workers is determined based on the number of indexes on the
> relation that support parallel vacuum operation which is limited by
> number of workers specified with PARALLEL option if any which is
> further limited by max_parallel_maintenance_workers." instead of what
> is currently there?

I think the implemented behavior is wrong.  The VACUUM PARALLEL option 
should override the max_parallel_maintenance_worker setting.

Otherwise, what's the point of the command option?

-- 
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: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Next
From: Amit Kapila
Date:
Subject: Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers