Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers
Date
Msg-id CA+TgmoZyNu1orkCkG8us=spULFOdLn6MiPGngw+ZK-VVZU6SrQ@mail.gmail.com
Whole thread Raw
In response to Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
On Sat, Oct 3, 2020 at 7:03 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> But the same is true for the 'Create Index' operation as well where we
> follow the same thing. We will use the number of workers as specified
> in reloption (parallel_workers) which is then limited by
> max_parallel_maintenance_workers.

Well, that seems pretty weird to me too, but surely we want them both
to be consistent.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: enable_incremental_sort changes query behavior
Next
From: Robert Haas
Date:
Subject: Re: VACUUM PARALLEL option vs. max_parallel_maintenance_workers