| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| Date: | 2016-12-02 22:37:13 |
| Message-ID: | afd34a76-c902-7439-94e5-a7a77bb93a47@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 12/2/16 2:34 PM, Robert Haas wrote:
> Signs point to "no". It seemed like a good idea to leave some daylight between max_parallel_workers and max_worker_processes, but evidently this wasn't the way to get there. Or else we should just give up on that thought.
Could the defaults be scaled based on max_connections, with a max on the
default?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-02 22:45:11 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| Previous Message | Robert Haas | 2016-12-02 22:34:59 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-02 22:45:11 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| Previous Message | Robert Haas | 2016-12-02 22:34:59 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |