Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1egCtD-0001Xd-5I for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Jan 2018 17:06:39 +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 1egCtC-0001Op-0K for pgsql-bugs@arkaria.postgresql.org; Mon, 29 Jan 2018 17:06:38 +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 1egCtB-0001Of-Qk for pgsql-bugs@lists.postgresql.org; Mon, 29 Jan 2018 17:06:37 +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 1egCt9-0007mF-9g for pgsql-bugs@postgresql.org; Mon, 29 Jan 2018 17:06:37 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A0F2020CB1; Mon, 29 Jan 2018 12:06:32 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 29 Jan 2018 12:06:32 -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=CJnWJJ39C2XIIeDyZi0xsWLIhRAn6 w8OpFzLY+aMoR0=; b=pR9z30FZ+pyqMr41WU8L7EBVRtR78E1Ve5yuXGoKr0Zy8 8UBLFY5+kOMG5wiw3uzUYsb7bDCSESqnfCQpFRpWBiRRzudzbKSEhonsp3r9j83M 7OdLEpbaV7IoSEAq2vXFQwzMhZprmE5Ov72V2UKgMxhcdESipn1LWN/+QoIlkiLw I7k3j3qFeilY8YqNaq6NilEkm4dUTpBt2JPwqn/bu79IJmf9RRCXIUcTmInnGR7L MAGDsya3YLJQb/XCBkBtMY3LPFYR+A1JYqizQLUdRd2cn13EDSQpNsGa+q2m/q2O OF9i0MijicNjZgfja5iv6EwD6A68ID5REhHj5bxgw== X-ME-Sender: Received: from intern.anarazel.de (unknown [136.24.76.189]) by mail.messagingengine.com (Postfix) with ESMTPA id 5140E7E3DF; Mon, 29 Jan 2018 12:06:32 -0500 (EST) Date: Mon, 29 Jan 2018 09:06:31 -0800 From: Andres Freund To: Tomas Vondra Cc: Tom Lane , "Todd A. Cook" , Thomas Munro , PostgreSQL Bugs Subject: Re: BUG #14932: SELECT DISTINCT val FROM table gets stuck in an infinite loop Message-ID: <20180129170631.kdr2dtu5rodvovhv@alap3.anarazel.de> References: <219b37b2-d740-d04a-203a-49ae422028f7@blackducksoftware.com> <1773c302-2fb1-749f-8ccc-62b23617c5ac@blackducksoftware.com> <25629.1512580464@sss.pgh.pa.us> <20171206171923.dg7phzfh7nb4lou3@alap3.anarazel.de> <7de4b2d6-b119-7d15-04d8-4c0fcb29cbc3@2ndquadrant.com> <20180126234537.dyu6jwnqz7snpq7n@alap3.anarazel.de> <14184.1517010515@sss.pgh.pa.us> <20180129010213.rt3nu73ilff756f6@alap3.anarazel.de> <3971fa24-285b-1c57-db95-b15c513162c1@2ndquadrant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3971fa24-285b-1c57-db95-b15c513162c1@2ndquadrant.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2018-01-29 14:41:49 +0100, Tomas Vondra wrote: > Do you think repeating the performance testing is necessary? Not sure > when do you plan to push the changes, I may not have time for the tests > until after FOSDEM. Hm, it surely wouldn't hurt, but your previous result does give a lot of confidence - there's not a lot of fundamental difference leaving one more mitigation that should never reduce hashtable "quality" aside. So I think going ahead with pushing and then benchmarking if possible, is reasonable? Greetings, Andres Freund