Re: Rename max_parallel_degree?

Поиск
Список
Период
Сортировка
От Julien Rouhaud
Тема Re: Rename max_parallel_degree?
Дата
Msg-id 9b599d4c-cb80-4f1f-48ad-169469579efe@dalibo.com
обсуждение исходный текст
Ответ на Re: Rename max_parallel_degree?  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Rename max_parallel_degree?  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 13/06/2016 03:16, Robert Haas wrote:
> On Sat, Jun 11, 2016 at 6:24 PM, Julien Rouhaud
> <julien.rouhaud@dalibo.com> wrote:
>> On 11/06/2016 23:37, Julien Rouhaud wrote:
>>> On 09/06/2016 16:04, Robert Haas wrote:
>>>> There remains only the task of adding max_parallel_degree
>>>> as a system-wide limit
>>>>
>>>
>>> PFA a patch to fix this open item.  I used the GUC name provided in the
>>> 9.6 open item page (max_parallel_workers), with a default value of 4.
>>> Value 0 is another way to disable parallel query.
>>>
>>
>> Sorry I just realized I made a stupid mistake, I didn't check in all
>> slots to get the number of active parallel workers. Fixed in attached v2.
>
> I think instead of adding a "bool parallel" argument to
> RegisterDynamicBackgroundWorker, we should just define a new constant
> for bgw_flags, say BGW_IS_PARALLEL_WORKER.
>

Agreed, and fixed in attached v3.

--
Julien Rouhaud
http://dalibo.com - http://dalibo.org

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tatsuro Yamada
Дата:
Сообщение: Re: ERROR: ORDER/GROUP BY expression not found in targetlist
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Why we don't have checksums on clog files