Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dmPGl-0003LS-18 for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Aug 2017 19:00:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dmPGk-0001G9-07 for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Aug 2017 19:00:18 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dmPGh-0001Ez-S1; Mon, 28 Aug 2017 19:00:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dmPGa-0006N3-SG; Mon, 28 Aug 2017 19:00:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v7SJ02Hq016979; Mon, 28 Aug 2017 15:00:02 -0400 From: Tom Lane To: Robert Haas cc: Amit Kapila , Noah Misch , "Adam, Etienne (Nokia-TECH/Issy Les Moulineaux)" , PostgreSQL Bugs , "Duquesne, Pierre (Nokia-TECH/Issy Les Moulineaux)" , pgsql-hackers Subject: Re: [HACKERS] [postgresql 10 beta3] unrecognized node type: 90 In-reply-to: References: <11673.1502467154@sss.pgh.pa.us> <20170815025243.GA3986579@rfd.leadboat.com> <26053.1502804769@sss.pgh.pa.us> <2941.1502979564@sss.pgh.pa.us> <28782.1502992247@sss.pgh.pa.us> <29467.1502993219@sss.pgh.pa.us> <18650.1502995942@sss.pgh.pa.us> <1105.1503008416@sss.pgh.pa.us> <24667.1503865781@sss.pgh.pa.us> <3924.1503923486@sss.pgh.pa.us> <13540.1503931678@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 28 Aug 2017 13:43:22 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16977.1503946802.1@sss.pgh.pa.us> Date: Mon, 28 Aug 2017 15:00:02 -0400 Message-ID: <16978.1503946802@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org Robert Haas writes: > On Mon, Aug 28, 2017 at 10:47 AM, Tom Lane wrote: > - fuller description. Academic literature on parallel query suggests that > + fuller description. The academic literature on parallel query suggests > That sentence isn't wrong as written. Count the "that"s (you're failing to notice the next line). > I don't really understand the part about depending on a parallel-aware > node. I mean, there should always be one, except in the > single-copy-Gather case, but why is it right to depend on that rather > than anything else? What happens when the Parallel Hash patch goes in > and we have multiple parallel-aware scan nodes (plus a parallel-aware > Hash node) under the same Gather? Well, that's what I'm asking. AFAICS we only really need the scan node(s) to be marked as depending on the Gather's rescan parameter. It would not, however, hurt anything for nodes above them to be so marked as well --- and even if we didn't explicitly mark them, those nodes would end up depending on the parameter anyway because of the way that parameter dependency propagation works. I think the question boils down to whether a "parallel_aware" node would ever not be underneath a related Gather. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs