Re: Parallel Seq Scan

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel Seq Scan
Date: 2015-03-13 13:22:24
Message-ID: CA+TgmobVBFB7nsZdpX5iSwFzJF7CCfwHEdxb6gRLL3ZcDO=GyA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 13, 2015 at 9:01 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Thu, Mar 12, 2015 at 3:44 AM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
> wrote:
>> In create_parallelscan_paths() function the funnel path is added once
>> the partial seq scan
>> path is generated. I feel the funnel path can be added once on top of
>> the total possible
>> parallel path in the entire query path.
>>
>> Is this the right patch to add such support also?
>
> This seems to be an optimization for parallel paths which can be
> done later as well.

+1. Let's keep it simple for now.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-03-13 13:23:15 Re: Proposal : REINDEX xxx VERBOSE
Previous Message Robert Haas 2015-03-13 13:21:46 Re: CATUPDATE confusion?