| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Small fix to postgresql.conf.sample's comment on max_parallel_workers |
| Date: | 2017-03-07 20:32:16 |
| Message-ID: | CA+TgmobRNn90-ahJL=sHkxRf5nw8+wVrqL0f4sCFfuBXhE4SWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 7, 2017 at 7:42 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Tue, Mar 7, 2017 at 8:02 AM, David Rowley
> <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
>> On 7 March 2017 at 15:21, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>>> +1. How about changing the description of
>>> max_parallel_workers_per_gather to "taken from max_worker_processes,
>>> limited by max_parallel_workers"?
>>
>> Thanks for looking.
>>
>> Seems more accurate to say that it's "taken from
>> max_parallel_workers", maybe.
>>
>
> I thought of saying similar to what we have in docs, however the way
> you have written works for me.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-07 20:45:13 | Re: Allow interrupts on waiting standby |
| Previous Message | Robert Haas | 2017-03-07 20:27:36 | Re: ANALYZE command progress checker |