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 1h6fet-0002QZ-Ky for pgsql-committers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:09:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6fes-0007p7-8h for pgsql-committers@arkaria.postgresql.org; Wed, 20 Mar 2019 18:09:46 +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 1h6feq-0007ma-KM for pgsql-committers@lists.postgresql.org; Wed, 20 Mar 2019 18:09:46 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6fem-0004Pm-FR for pgsql-committers@lists.postgresql.org; Wed, 20 Mar 2019 18:09:44 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id CDC39233EC; Wed, 20 Mar 2019 14:09:37 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 20 Mar 2019 14:09:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=iqrTLMjlY+j7MbUIYmV5wsnOGdN PJCeJE0rKx1LRIwU=; b=QeqHlguSfU1DSg6q3XPcaTd5pjmZAeb6Lt8neceDNaR hzZ6KBmeUiteX5ySllynHYDw6R83kR4/1lLr/xWezndQap/kvqW+1l5FpqR945GO rbCE3qzkDHjeG0hIHhh+K0P+6z9JhQJgbSdAKKvJcnr3RooyGahuglOf8qa+0Nev 24SHkqSCsVjY1S+lGOo0+2Dh+u0jqjd49cSldsTDHOqRAKSYsIreezSK3/GeHIQJ onQH2VnvYDqibG3aHoY1yrY/qUL0KgaPBVS0KJUgCMEcxURi02HB4yDpR8d9k+WJ mVr4OK3sugCuBYunSKunGHt/+2a/9145PQ28zvh4XJw== 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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iqrTLM jlY+j7MbUIYmV5wsnOGdNPJCeJE0rKx1LRIwU=; b=FFLWt+psMOe3EZsaLh5c+A riSNhWC+N1JRF/DiJjvD4uDjtQmhcEXvCDd8F37Q3Zfq9JW7M2rsR2VOBWOLj/fr OkE1jGrsGympo17+2994RGnybzLipZnh7R2b/Q1z9sozMYVxH08cgn3OO4KwDmbP tWWqY1f08jegBgcrDjzXuD2sYt0VoCvaasls1jnDxVJ11DsPh9wS/pEg9YIidPWX IWGPKKjK5kYLGe4we+PjFpPZ1dwW6WB5G02mLx6wX+x9aFgIGCwdBHlqeM+95Ijc fNOlibR4jjQOBM2TdUOkfO7gXXNYDd+aap6kCsIeB9Vbe2OeZiVYbtXCxONTaW8Q == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrieeigddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucfkpheple eirdekiedrudejgedrledunecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshes rghnrghrrgiivghlrdguvgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from intern.anarazel.de (96-86-174-91-static.hfc.comcastbusiness.net [96.86.174.91]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A4A510312; Wed, 20 Mar 2019 14:09:36 -0400 (EDT) Date: Wed, 20 Mar 2019 11:09:34 -0700 From: Andres Freund To: Peter Geoghegan Cc: pgsql-committers Subject: Re: pgsql: Make heap TID a tiebreaker nbtree index column. Message-ID: <20190320180934.kkvnmpsa7my47ffd@alap3.anarazel.de> References: 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 2019-03-20 11:00:06 -0700, Peter Geoghegan wrote: > On Wed, Mar 20, 2019 at 10:05 AM Peter Geoghegan wrote: > > Make heap TID a tiebreaker nbtree index column. > > I see that this has caused SELinux test failures on rhinoceros (the > ddl test fails). It looks like the output order is affected by the > implementation details of nbtree, likely for some system catalog > index. This is something that I've had to deal with in other places > (with a lot of help from Tom). > > It's not easy for me to set up SELinux to fix the issue. Is there > somebody comfortable with that area that could confirm I have it > right, and provide me with the actual test output? Or push a fix > themselves? FWIW, I just fix up the tests using the regression output from rhinoceros when that happens. Sometimes takes more than a single round, but it builds frequently enough... Greetings, Andres Freund