From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal : Parallel Merge Join |
Date: | 2017-02-25 05:59:19 |
Message-ID: | CAA4eK1Jz6fzVPBFUVY4+vvb3dvXM3Bz7PvzHB9S-7Or_um_uPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 24, 2017 at 4:49 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> On Fri, Feb 24, 2017 at 3:04 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> What advantage do you see for considering such a path when the cost of
>> innerpath is more than cheapest_total_inner? Remember the more paths
>> we try to consider, the more time we spend in the planner. By any
>> chance are you able to generate any query where it will give benefit
>> by considering costlier innerpath?
>
> Changed
>
It seems you have forgotten to change in the below check:
+ if (innerpath != NULL &&
+ innerpath->parallel_safe &&
+ (cheapest_startup_inner == NULL ||
+ cheapest_startup_inner->parallel_safe == false ||
+ compare_path_costs(innerpath, cheapest_startup_inner,
+ STARTUP_COST) < 0))
+ /* Found a cheap (or even-cheaper) sorted parallel safer path */
typo
/safer/safe
Note - Change the patch status in CF app (to Needs Review) whenever
you post a new patch. I could see that your other patch also needs a
similar update in CF app.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2017-02-25 08:40:45 | Re: Logical replication existing data copy |
Previous Message | Pavan Deolasee | 2017-02-25 05:20:57 | Re: Patch: Write Amplification Reduction Method (WARM) |