| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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:45:11 |
| Message-ID: | 989.1480718711@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> 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?
Might work. We've had very bad luck with GUC variables with
interdependent defaults, but maybe the user-visible knob could be a
percentage of max_connections or something like that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-12-03 02:15:01 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| Previous Message | Jim Nasby | 2016-12-02 22:37:13 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-12-02 22:50:48 | Re: PSQL commands: \quit_if, \quit_unless |
| Previous Message | Jim Nasby | 2016-12-02 22:37:13 | Re: [COMMITTERS] pgsql: Add max_parallel_workers GUC. |