From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: why not parallel seq scan for slow functions |
Date: | 2017-08-22 07:31:25 |
Message-ID: | CANP8+jJvk120zqF6RHtw=HZ3Ux2hA2jA2A5VXn_NqRZSJRtmuA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21 August 2017 at 11:42, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> or of 2)
>> treating cost = speed, so we actually reduce the cost of a parallel
>> plan rather than increasing it so it is more likely to be picked.
>>
>
> Yeah, this is what is being currently followed for costing of parallel
> plans and this patch also tries to follow the same.
OK, I understand this better now, thanks.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-08-22 07:32:06 | proposal: psql command \graw |
Previous Message | Simon Riggs | 2017-08-22 06:23:53 | Re: Explicit relation name in VACUUM VERBOSE log |