From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: max_parallel_degree > 0 for 9.6 beta |
Date: | 2016-04-21 20:01:10 |
Message-ID: | 57193186.7090209@archidevsys.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 22/04/16 06:07, Robert Haas wrote:
> On Thu, Apr 21, 2016 at 1:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Wed, Apr 20, 2016 at 2:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>>> Andres Freund <andres(at)anarazel(dot)de> writes:
>>>>> max_parallel_degree currently defaults to 0. I think we should enable
>>>>> it by default for at least the beta period. Otherwise we're primarily
>>>>> going to get reports back after the release.
>>> So, I suggest that the only sensible non-zero values here are probably
>>> "1" or "2", given a default pool of 8 worker processes system-wide.
>>> Andres told me yesterday he'd vote for "2". Any other opinions?
>> It has to be at least 2 for beta purposes, else you are not testing
>> situations with more than one worker process at all, which would be
>> rather a large omission no?
> That's what Andres, thought, too. From my point of view, the big
> thing is to be using workers at all. It is of course possible that
> there could be some bugs where a single worker is not enough, but
> there's a lot of types of bug where even one worker would probably
> find the problem. But I'm OK with changing the default to 2.
>
I'm curious.
Why not 4? As most processors now have at least 4 physical cores, &
surely it be more likely to flush out race conditions.
Cheers,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-04-21 20:18:01 | Re: Should XLogInsert() be done only inside a critical section? |
Previous Message | Christian Ullrich | 2016-04-21 19:56:01 | Re: VS 2015 support in src/tools/msvc |