Re: Rename max_parallel_degree? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Rename max_parallel_degree?
Date
Msg-id e23ba9e4-7b92-0bf2-e0f3-194338ba7b11@2ndquadrant.com
Whole thread Raw
In response to Re: Rename max_parallel_degree?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Rename max_parallel_degree?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 5/31/16 4:04 PM, Tom Lane wrote:
> The name should be closely related to what we use for #3.  I could go for
> max_total_parallel_workers for #2 and max_parallel_workers for #3.
> Or maybe max_parallel_workers_total?

Most cluster-wide settings like this are named max_something 
(max_connections, max_wal_senders, max_replication_slots), whereas 
things that apply on a lower level are named max_something_per_something 
(max_files_per_process, max_locks_per_transations).

So let's leave max_worker_processes mostly alone and not add any 
_total_, _absolute_, _altogether_. ;-)

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Rename synchronous_standby_names?
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: Re: Question and suggestion about application binary compatibility policy