Re: BUG #18343: Incorrect description in postgresql.conf for max_parallel_workers_per_gather

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: kline(dot)christopher(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18343: Incorrect description in postgresql.conf for max_parallel_workers_per_gather
Date: 2024-02-15 15:55:10
Message-ID: 3258900.1708012510@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> In the default postgresql.conf that is generated, there are the following
> lines:

> #max_worker_processes = 8 # (change requires restart)
> #max_parallel_workers_per_gather = 2 # taken from max_parallel_workers
> <<<<<<<<<<<<<<<<<<<<<<<< THIS
> #max_parallel_maintenance_workers = 2 # taken from max_parallel_workers
> max_parallel_workers = 8 # maximum number of max_worker_processes that
> # can be used in parallel operations

> it indicates that the default value is taken from whatever
> max_parallel_workers is.

No, you're misreading it. There's no magic connection between these
two settings. What the comment means to say is that the per-gather
worker processes come out of a pool of at most max_parallel_workers
processes. Perhaps another wording would be better, but we don't have
a lot of space here --- any thoughts?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2024-02-15 16:10:00 Re: BUG #18343: Incorrect description in postgresql.conf for max_parallel_workers_per_gather
Previous Message David G. Johnston 2024-02-15 13:22:58 Re: BUG #18345: Specifying index parameters for a PRIMARY KEY column constraint is a syntax error