From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parallel joins, and better parallel explain |
Date: | 2015-12-01 12:28:21 |
Message-ID: | CAA4eK1KURNE0oEs9R6-yUnLieo4FFDvirc=zfju1xfLSs8uwZw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 1, 2015 at 5:51 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Thu, Nov 26, 2015 at 8:11 AM, Robert Haas <robertmhaas(at)gmail(dot)com>
wrote:
> >
> > Attached find a patch that does (mostly) two things.
> >
>
> I have started looking into this and would like to share few findings
> with you:
>
>
> - There seems to be some inconsistency in Explain's output when
> multiple workers are used.
>
Forgot to mention that I have changed code of cost_seqscan() by adding
below line, so that it can select parallel plan. This is just a temporary
change to verify Explain's output.
cost_seqscan()
{
..
run_cost = run_cost / (path->parallel_degree + 0.5);
..
}
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2015-12-01 12:30:47 | Re: Some questions about the array. |
Previous Message | Amit Kapila | 2015-12-01 12:21:19 | Re: parallel joins, and better parallel explain |