Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Small fix to postgresql.conf.sample's comment on max_parallel_workers - Mailing list pgsql-hackers

From David Rowley
Subject Re: [HACKERS] Small fix to postgresql.conf.sample's comment on max_parallel_workers
Date
Msg-id CAKJS1f95JmN6aH4vbjOBNms3F3NaeHRg370QFpHCgbU2Kq_98A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Small fix to postgresql.conf.sample's comment on max_parallel_workers  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [HACKERS] Small fix to postgresql.conf.sample's comment on max_parallel_workers  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
On 7 March 2017 at 15:21, Amit Kapila <amit.kapila16@gmail.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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Attachment

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: [HACKERS] adding an immutable variant of to_date
Next
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] Re: check failure with -DRELCACHE_FORCE_RELEASE-DCLOBBER_FREED_MEMORY