Re: Rename max_parallel_degree? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Rename max_parallel_degree?
Date
Msg-id CAM3SWZQTmjE+O-NnGthzLd61RtXkNfitWrZU6zJHHHZSB3YmEg@mail.gmail.com
Whole thread Raw
In response to Re: Rename max_parallel_degree?  (Josh berkus <josh@agliodbs.com>)
Responses Re: Rename max_parallel_degree?
List pgsql-hackers
On Tue, May 31, 2016 at 10:46 AM, Josh berkus <josh@agliodbs.com> wrote:
> In parallel seq scan and join, do the "masters" behave as workers as well?

It depends. They will if they can. If the parallel seq scan leader
isn't getting enough work to do from workers (enough tuples to process
from the shared memory queue), it will start acting as a worker fairly quickly.
With parallel aggregate, and some other cases, that will always happen.

Even when the leader is consuming input from workers, that's still perhaps
pegging one CPU core. So, it doesn't really invalidate what I said about
the number of cores being the primary consideration.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Rename synchronous_standby_names?
Next
From: Tom Lane
Date:
Subject: Re: Rename max_parallel_degree?