Re: Small fix to postgresql.conf.sample's comment on max_parallel_workers

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: 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 02:32:24
Message-ID: CAKJS1f95JmN6aH4vbjOBNms3F3NaeHRg370QFpHCgbU2Kq_98A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. You can't "take" more than what's there,
so perhaps the extra text is not required.

Patch attached.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
postgresql.conf.sample_fix_v2.patch application/octet-stream 896 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2017-03-07 02:33:27 Re: Re: check failure with -DRELCACHE_FORCE_RELEASE -DCLOBBER_FREED_MEMORY
Previous Message Andreas Karlsson 2017-03-07 02:21:42 Re: adding an immutable variant of to_date