Re: max_parallel_workers question - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: max_parallel_workers question
Date
Msg-id ZUv6ad4X3AxVRece@momjian.us
Whole thread Raw
In response to Re: max_parallel_workers question  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Sat, Sep 28, 2019 at 12:10:53AM -0400, Robert Haas wrote:
> On Fri, Sep 27, 2019 at 8:07 PM Jeff Davis <pgsql@j-davis.com> wrote:
> > The current docs for max_parallel_workers start out:
> >
> > "Sets the maximum number of workers that the system can support for
> > parallel operations..."
> >
> > In my interpretation, "the system" means the entire cluster, but the
> > max_parallel_workers setting is PGC_USERSET. That's a bit confusing,
> > because two different backends can have different settings for "the
> > maximum number ... the system can support".
> 
> Oops.
> 
> I intended it to mean "the entire cluster." Basically, how many
> workers out of max_worker_processes are you willing to use for
> parallel query, as opposed to other things. I agree that PGC_USERSET
> doesn't make any sense.

I found two places there "custer" was better than "system", so I applied
the attached patch to master.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: XID-wraparound hazards in LISTEN/NOTIFY
Next
From: Andres Freund
Date:
Subject: Re: Syncrep and improving latency due to WAL throttling