From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Hubert Lubaczewski <depesz(at)depesz(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: explain analyze output with parallel workers - question about meaning of information for explain.depesz.com |
Date: | 2017-12-09 10:30:08 |
Message-ID: | CAA4eK1L6EZ+OFnWRmV+i=zA+36to3Y5CGVcAj-ADb9T9riXpYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 9, 2017 at 1:24 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Dec 8, 2017 at 5:11 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>>> Okay, I have adjusted the patch accordingly. I have also added a
>>> regression test which should produce the same result across different
>>> runs, see if that looks okay to you, then it is better to add such a
>>> test as well.
>>
>> The regression test added by patch needs cleanup at the end which I
>> have added in the attached patch.
>
> Hmm. If we're going this way, then shouldn't we revert the changes
> commit 2c09a5c12a66087218c7f8cba269cd3de51b9b82 made to
> ExecParallelRetrieveInstrumentation?
>
Yeah, it is better to revert it as ideally that is not required after
this patch and that is what I have tried to convey above ("Ideally, it
would have obviated the need for my previous patch which
got committed as 778e78ae." (The commit id is for branch 10,
otherwise, it is same as what you mention.)). I have locally reverted
that patch and then rebased it on top of that.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
fix_accum_instr_parallel_workers_v8.patch | application/octet-stream | 9.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-12-09 10:41:04 | Re: Typo in recent commit |
Previous Message | Pavel Stehule | 2017-12-09 06:47:29 | Re: plpgsql fails to reinitialize record variables at block re-entry |