Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC.
Date
Msg-id F9847DA0-DC8E-45EA-9252-7F7DFC7604DA@gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Dec 2, 2016, at 5:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jim Nasby <Jim.Nasby@BlueTreble.com> writes:
>>> On 12/2/16 2:34 PM, Robert Haas wrote:
>>> Signs point to "no".  It seemed like a good idea to leave some daylight between max_parallel_workers and
max_worker_processes,but evidently this wasn't the way to get there. Or else we should just give up on that thought. 
>
>> Could the defaults be scaled based on max_connections, with a max on the
>> default?
>
> Might work.  We've had very bad luck with GUC variables with
> interdependent defaults, but maybe the user-visible knob could be a
> percentage of max_connections or something like that.

Seems like overkill. Let's just reduce the values a bit.

...Robert


pgsql-hackers by date:

Previous
From: Christian Convey
Date:
Subject: Re: Tackling JsonPath support
Next
From: Amit Kapila
Date:
Subject: Re: [sqlsmith] Failed assertion in _hash_splitbucket_guts