Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eeSbi-0003Ns-Nd for pgsql-committers@arkaria.postgresql.org; Wed, 24 Jan 2018 21:29:22 +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 1eeSbi-0001N2-6M for pgsql-committers@arkaria.postgresql.org; Wed, 24 Jan 2018 21:29:22 +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 1eeSbi-0001Ms-1b for pgsql-committers@lists.postgresql.org; Wed, 24 Jan 2018 21:29:22 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eeSbf-0001rQ-Em for pgsql-committers@postgresql.org; Wed, 24 Jan 2018 21:29:21 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id C2269222FC; Wed, 24 Jan 2018 16:29:17 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 24 Jan 2018 16:29:17 -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=v5nb5LI1Ug0YR5BJSievUlRmeRh9U EsELrXCKvWz4Xo=; b=V0TUTPPSdgDKk+5HyoOstEgVvh172at8aQb0clyvADfSc mqlnH2MQzafiYaRNc+Q9fwLVcoqFGDhWFa+rzIejlOVekVEpTMGNbR0dV+4CLjY4 wIO3qoz6E+xfy4YCz3ruLjXZLhEDTkSf5ITxGeiQ6q6pBosFVy7rH0LjQGhfxFIB TeEU6U4RFDx7NiWKuou428gIl8D07JMsgJ1MtBWxYp4ME+TRyghpoaYCza7veKws HCvB+3m6bic8XbiKMxOLbqrE8+0dmc3mEF9dNvfXkqdTndUtr/Q66jllqnLZDdQH KtjI9FLXEEwBGRgnpx/Evct1ERnsqidrRKF+rMm0g== X-ME-Sender: Received: from intern.anarazel.de (unknown [136.24.76.189]) by mail.messagingengine.com (Postfix) with ESMTPA id 87D0A24785; Wed, 24 Jan 2018 16:29:17 -0500 (EST) Date: Wed, 24 Jan 2018 13:29:16 -0800 From: Andres Freund To: Thomas Munro Cc: Tom Lane , pgsql-committers Subject: Re: pgsql: Add parallel-aware hash joins. Message-ID: <20180124212916.aufzppm5bzg3oxav@alap3.anarazel.de> References: <20171221092940.gbxcszbzsr5khsfr@alap3.anarazel.de> <20171221095550.d3e7xhoakcowhu5b@alap3.anarazel.de> <20171222082203.fl6rpzlqnm4h7h6h@alap3.anarazel.de> <30219.1514428346@sss.pgh.pa.us> <4503.1514435195@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2018-01-22 23:17:47 +1300, Thomas Munro wrote: > On Thu, Dec 28, 2017 at 5:26 PM, Tom Lane wrote: > Here is a patch that halves the size of the test tables used. I don't > want them to be too small because I want some some real parallel > processing at least sometimes. On my slowest system with assertions > enabled this brings "time make check" from ~37.5s to ~36.9s. I'm a > bit worried about choosing parameters that lead to instability across > the buildfarm, until I make the size estimation code a bit smarter[1], > so I tested a few variations that affect the alignment and size of > things (-m32, -malign-double, --disable-atomics, --disable-spinlocks) > and didn't see failures. Does this pass repeatedly on gaur? I'd say, let's just commit it and see? Will do so soon if nobody protests. Greetings, Andres Freund