From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Erik Rijkers <er(at)xs4all(dot)nl> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parallel documentation improvements |
Date: | 2017-08-01 19:32:22 |
Message-ID: | CA+TgmoaXojXNzEJ57fHWRCF1GkMhERstC8XQQ3rvH2wwf4BZhQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 1, 2017 at 3:15 PM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> On 2017-08-01 20:43, Robert Haas wrote:
>> In commit 054637d2e08cda6a096f48cc99696136a06f4ef5, I updated the
>> parallel query documentation to reflect recently-committed parallel
>>
>> Barring objections, I'd like to commit this in the next couple of days
>
> I think that in this bit:
>
> occurrence is frequent, considering increasing
> <varname>max_worker_processes</> and <varname>max_parallel_workers</>
> so that more workers can be run simultaneously or alternatively
> reducing
> - <xref linkend="guc-max-parallel-workers-per-gather"> so that the
> planner
> + <varname>max_parallel_workers_per_gather</varname> so that the planner
> requests fewer workers.
>
>
> 'considering increasing' should be
> 'consider increasing'
Thanks, you are right.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-08-01 19:33:08 | Re: Remove 1MB size limit in tsvector |
Previous Message | Erik Rijkers | 2017-08-01 19:15:14 | Re: parallel documentation improvements |