Re: Rename max_parallel_degree? - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Rename max_parallel_degree?
Date
Msg-id CAM3SWZS_d0L3FmWghdK2a26jDzLGEq6bOUHxNBhkjpyZeu30Tw@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?  (Peter Geoghegan <pg@heroku.com>)
Re: Rename max_parallel_degree?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Tue, May 31, 2016 at 11:02 AM, Josh berkus <josh@agliodbs.com> wrote:
> I get where you're coming from, but I think Haas's query plan output is
> going to show us the confusion we're going to get.  So we need to either
> change the parameter, the explain output, or brace ourselves for endless
> repeated questions.

I get where you're coming from, too -- I think our positions are very close.

The only reason I favor defining parallel_degree = 1, rather than
doing what Tom proposes to do with that patch, is that we might as
well use the prevailing terminology used by SQL Server and Oracle (as
long as we match those semantics). Also, I think that number of cores
used is a more important consideration for users than the number of
workers used.

Users will definitely be confused about workers used vs. cores used,
but I don't think that any proposal fixes that.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rename max_parallel_degree?
Next
From: Tom Lane
Date:
Subject: Re: Logic behind parallel default? WAS: Rename max_parallel_degree?