Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWuFY-0008Mz-2Q for pgsql-committers@arkaria.postgresql.org; Thu, 04 Jan 2018 01:23:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWuFX-0002BD-A9 for pgsql-committers@arkaria.postgresql.org; Thu, 04 Jan 2018 01:23:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eWuFW-0002B3-Tn for pgsql-committers@lists.postgresql.org; Thu, 04 Jan 2018 01:23:15 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eWuFQ-0005JS-Bz for pgsql-committers@postgresql.org; Thu, 04 Jan 2018 01:23:14 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 5718D20940; Wed, 3 Jan 2018 20:23:06 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 03 Jan 2018 20:23:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=mMkFbayHyLim5CuMYJg93nOYsXqDt jcM28Zyux4RKIE=; b=W+znMcU4KMtvA1fr93EzYKEOnoXzug+anfcsDQBlMBQ1F rLfRLvXbZMfHfESie5aLivkMXsVjZHowUqDMCj46oSP3SoJxkqW4+KjpMN4ITcyC aMzRw3lKuWEzIJQ7DbFUPXNBmRKUfsZhwtl+51kYW8nnpFmCooWiSlNYSBu3kEZe Cm/TRTmqpfg8UqnoJMp5fblsfAuVOvOxNFcRc0JZ3vnI465QfYV+DfZJXlR8McmQ jsPLJ4WAk4aP+xh6NwIAzoQoBug3PBzXaEbXlKgyI0TPyZKLs+eR5AOJwZO/lj8T iw3D39wKCIwZdJbkeL7gDmF0EgGfKVkmhFjSdX0CQ== X-ME-Sender: Received: from intern.anarazel.de (unknown [136.24.76.189]) by mail.messagingengine.com (Postfix) with ESMTPA id 10C367E0ED; Wed, 3 Jan 2018 20:23:06 -0500 (EST) Date: Wed, 3 Jan 2018 17:23:05 -0800 From: Andres Freund To: Tom Lane Cc: Thomas Munro , pgsql-committers Subject: Re: pgsql: Add parallel-aware hash joins. Message-ID: <20180104012305.hi2sxh6572okbc5y@alap3.anarazel.de> References: <30655.1514673257@sss.pgh.pa.us> <4001.1514678419@sss.pgh.pa.us> <18190.1514943510@sss.pgh.pa.us> <18804.1515002619@sss.pgh.!pa.us> <5187.1515028624@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5187.1515028624@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2018-01-03 20:17:04 -0500, Tom Lane wrote: > So this patch has been in place for two weeks, the buildfarm has still > got the measles, and we're entering the January commitfest with a lot > of other work to get done. I realize that the two weeks were mostly > holiday time, but it's time to have some urgency about clearing the > buildfarm failures. Agreed. > As best I understand, the remaining failures simply arise from > an unstable regression test case and aren't teaching us anything > of value. I think that's the correct interpretation. > I propose that for the moment, we simply remove the > failing query from join.sql. We can put it back when there's > reason to think it will pass everywhere. Alternatively we could temporarily push an alternative output. It doesn't seem inconceivable we missed an actual bug due to the noise. Don't have a strong opinion on which of the two to choose. Unless somebody does something first, I'll disable the test tomorrow pacific morning. But perhaps Thomas can up with an approach till then that seems likely to pass on the different architectures. Seems quite possible to just adjust the thresholds carefully? Greetings, Andres Freund