| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | James Sewell <james(dot)sewell(at)lisasoft(dot)com> |
| Cc: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel Aggregate |
| Date: | 2016-03-14 22:32:11 |
| Message-ID: | CA+TgmoY2CiFhJYt-p9xbfYvQZBAf3tb=zvNHTKotqG+4QAn+Nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 14, 2016 at 6:24 PM, James Sewell <james(dot)sewell(at)lisasoft(dot)com> wrote:
> Any chance of getting a GUC (say min_parallel_degree) added to allow setting
> the initial value of parallel_degree, then changing the small relation check
> to also pass if parallel_degree > 1?
>
> That way you could set min_parallel_degree on a query by query basis if you
> are running aggregates which you know will take a lot of CPU.
>
> I suppose it wouldn't make much sense at all to set globally though, so it
> could just confuse matters.
I kind of doubt this would work well, but somebody could write a patch
for it and try it out.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-03-14 22:39:36 | Re: Parallel Aggregate |
| Previous Message | James Sewell | 2016-03-14 22:24:41 | Re: Parallel Aggregate |