From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A GUC to prevent leader processes from running subplans? |
Date: | 2017-10-20 19:09:53 |
Message-ID: | CA+TgmoZ9aamZq25MngYFEReADDWFJu2mGiASrg4+-8k65vY3DA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 17, 2017 at 7:27 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> While testing parallelism work I've wanted to be able to prevent
> gather nodes from running the plan in the leader process, and I've
> heard others say the same. One way would be to add a GUC
> "multiplex_gather", like in the attached patch. If you set it to off,
> Gather and Gather Merge won't run the subplan unless they have to
> because no workers could be launched. I thought about adding a new
> value for force_parallel_mode instead, but someone mentioned they
> might want to do this on a production system too and
> force_parallel_mode is not really for end users. Better ideas?
I don't think overloading force_parallel_mode is a good idea, but
having some other GUC for this seems OK to me. Not sure I like
multiplex_gather, though.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-10-21 00:34:18 | Re: A design for amcheck heapam verification |
Previous Message | Tom Lane | 2017-10-20 16:52:10 | Useless(?) asymmetry in parse_func.c |