Re: max_parallel_workers can't actually be set?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: max_parallel_workers can't actually be set?
Date: 2019-08-17 20:23:44
Message-ID: 24418.1566073424@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sergei Kornilov <sk(at)zsrv(dot)org> writes:
>> which should certainly not happen for a PGC_POSTMASTER parameter.

> But max_parallel_workers is PGC_USERSET and this behavior seems be documented:

Argh! I was looking at max_worker_processes in one window and
max_parallel_workers in another, and failed to see the discrepancy.

Those GUCs are too confusingly named :-(.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-08-17 20:28:19 Re: max_parallel_workers can't actually be set?
Previous Message Ibrar Ahmed 2019-08-17 18:12:45 Re: max_parallel_workers can't actually be set?