Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gTyFp-0003K8-NT for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Dec 2018 00:07:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gTyFm-00060a-3H for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Dec 2018 00:07:54 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1gTyFl-0005vq-1t for pgsql-hackers@lists.postgresql.org; Tue, 04 Dec 2018 00:07:53 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gTyFc-0000sg-Fo for pgsql-hackers@postgresql.org; Tue, 04 Dec 2018 00:07:52 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 98DBA210F2; Mon, 3 Dec 2018 19:07:42 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 03 Dec 2018 19:07:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:subject:message-id:mime-version:content-type; s= fm3; bh=pxVnhEDGsCl+AVy5yB8kj+AInMSoC+ICqSUQAuONhTI=; b=qUSy1Yec 4ObYXDdDDz53twrGWD/X5RMAtfMkZRaYx4YzC5W8paUd0SxIcY5/BjIGOXV1Wxuu ECxqT8O7uNvUA79A4odESWrX3O+wcea/bnGkHUHdLktzFOsso26QujlM1lI3lQXF kPst+8ObmmgOp7aMAgr3yVxXMWfcHSij0s1OQUhQIp/kS/N2hZ8+lPzr99ukrkRm SptMot/zDZ6xPhgxEUMt0MixjavOsaBpqBkAL+tw3VbWDyfOXVgiAZNc9v1sFJhi 5jR+tLTJo0kmDDGALmUy+NI6jf3CZOsZxvgLThJtNaMH6024cFciDWVJp3eVEtu6 QvSS9QmXdq96RQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=pxVnhEDGsCl+AVy5yB8kj+AInMSoC +ICqSUQAuONhTI=; b=oF8CGBSh714m9arcqiLWTOmjhoH0KKIFSKhnzj/OdmNRi LpoPUUSY9D+1sIHA8MDZ/pqOK1SVQ9vPzA6mbevnlJT6ZZTVvyJMrNKyfloufEe4 xUJAKafOk18Z/YTHrgpQQeQdJscX2ApeqWwMsxzotVkHN4YS8FlI98khMVXLDiP7 UmI/PUqB6YGbaaok4hoMI2t+LYVMfOVVUGFrCy3fA1Ga4gUO6r2AAFRta/kb+c1D Wp08Djl8wmGGgZ7T2EYCm97gvwFnjAtBj4464f4vCLiH+KL17yFoigVt3TLKU15I 8O1pJD014oPcmeekn2h60KTg9OLJn0O1EFCAlrksA== X-ME-Sender: X-ME-Proxy: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DC7E10392; Mon, 3 Dec 2018 19:07:41 -0500 (EST) Date: Mon, 3 Dec 2018 16:07:40 -0800 From: Andres Freund To: pgsql-hackers@postgresql.org, Teodor Sigaev , Shubham Barai , Alexander Korotkov , Dmitry Ivanov Subject: GIN predicate locking slows down valgrind isolationtests tremendously Message-ID: <20181204000740.ok2q53nvkftwu43a@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2018-03-31%2014%3A40%3A02 isolation-check (02:19:36) https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2018-03-28%2010%3A40%3A02 isolation-check (00:18:44) As far as I can tell that increase comes laregely from the new GIN tests. Could one of you please look at keeping the test time increase to something more reasonable? Greetings, Andres Freund