Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information. - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.
Date
Msg-id CAA4eK1LpROHFRXiuekewRjphRGq4_vvPgJgxmsH1iY8jEZLiYQ@mail.gmail.com
Whole thread Raw
In response to Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Jul 7, 2016 at 7:37 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Kapila <amit.kapila16@gmail.com> writes:
>> On Thu, Jul 7, 2016 at 1:23 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>>> I found $SUBJECT while trying to test parallel queries. Is this a bug?
>
> Presumably the instrumentation data needed for that is not getting
> returned from the worker to the leader.  I would bet there's a lot
> of other plan-node-specific data that doesn't work either.
>
>> I think this can never happen for force_parallel_mode TO off, because
>> we don't generate a gather on top of sort node.  The reason why we are
>> able to push Sort below gather, because it is marked as parallel_safe
>> (create_sort_path).  I think we should not mark it as parallel_safe.
>
> That seems rather ridiculous.  An oversight in managing EXPLAIN data
> is not a sufficient reason to cripple parallel query.
>

I am analyzing that point only and you seems to be right that we have
missed to propagate some information.  We have taken care of
instrumentation information to be propagated back to leader, but it
seems there are other things that needs to be taken care in that area.



-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.
Next
From: Robert Haas
Date:
Subject: Re: EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information.