| From: | "Arnaud L(dot)" <arnaud(dot)listes(at)codata(dot)eu> |
|---|---|
| To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Slow statement using parallelism after 9.6>11 upgrade |
| Date: | 2019-09-03 15:04:50 |
| Message-ID: | 3ba3bd1d-161a-3ef1-f04f-03a9664e7b9c@codata.eu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 03/09/2019 à 16:39, Paul Ramsey a écrit :
>> On Sep 3, 2019, at 7:06 AM, Arnaud L. <arnaud(dot)listes(at)codata(dot)eu> wrote:
>> I've setup parallel_tuple_cost to 1.0 parallel_setup_cost to 5000.0 for the time being which solves this specific problem. These value don't look very sensible though, they are very high compared to the default ones.
>
> You can also leave that setting unchanged and just change the behaviour on your one table:
>
> ALTER TABLE nodes SET ( parallel_workers = 0);
Nice, this will fix this precise query and leave parallelism in place
for the other ones. Thanks !
--
Arnaud
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arnaud L. | 2019-09-03 15:09:29 | Re: Slow statement using parallelism after 9.6>11 upgrade |
| Previous Message | Imre Samu | 2019-09-03 15:02:41 | Re: Slow statement using parallelism after 9.6>11 upgrade |