Re: Parallel Seq Scan - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Parallel Seq Scan
Date
Msg-id CAFj8pRBDaL87CVy8i1iO21szV5yKvBFd7wo7PS8LB8D6fZX5Nw@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers


2015-11-16 14:17 GMT+01:00 Amit Kapila <amit.kapila16@gmail.com>:
On Mon, Nov 16, 2015 at 4:35 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Fri, Nov 13, 2015 at 10:46 AM, Thom Brown <thom@linux.com> wrote:
> >>> And perhaps associated PIDs?
> >>
> >> Yeah, that can be useful, if others also feel like it is important, I can
> >> look into preparing a patch for the same.
> >
> > Thanks.
>
> Thom, what do you think the EXPLAIN output should look like,
> specifically?  Or anyone else who feels like answering.
>
> I don't think it would be very useful to repeat the entire EXPLAIN
> output n times, once per worker.  That sounds like a loser.
>

Yes, it doesn't seem good idea to repeat the information, but what
about the cases when different workers perform scan on different
relations (partitions in case of Append node) or may be performs a
different operation in Sort or join node parallelism.

+1

Pavel
 


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

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Parallel Seq Scan
Next
From: Michael Paquier
Date:
Subject: Re: Default Roles (was: Additional role attributes)