| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rename max_parallel_degree? |
| Date: | 2016-06-01 00:51:42 |
| Message-ID: | e23ba9e4-7b92-0bf2-e0f3-194338ba7b11@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2016-06-01 01:16:59 | Re: Question and suggestion about application binary compatibility policy |
| Previous Message | Michael Paquier | 2016-06-01 00:49:07 | Re: Rename synchronous_standby_names? |