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 1h6i6y-0001Xp-49 for pgsql-committers@arkaria.postgresql.org; Wed, 20 Mar 2019 20:46:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6i6w-0001cu-Sx for pgsql-committers@arkaria.postgresql.org; Wed, 20 Mar 2019 20:46:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6i6w-0001cm-Js for pgsql-committers@lists.postgresql.org; Wed, 20 Mar 2019 20:46:54 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6i6u-00089q-8A for pgsql-committers@lists.postgresql.org; Wed, 20 Mar 2019 20:46:53 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x2KKkoGE024278; Wed, 20 Mar 2019 16:46:50 -0400 From: Tom Lane To: Peter Geoghegan cc: pgsql-committers Subject: Re: pgsql: Make heap TID a tiebreaker nbtree index column. In-reply-to: References: <13999.1553105283@sss.pgh.pa.us> Comments: In-reply-to Peter Geoghegan message dated "Wed, 20 Mar 2019 12:12:07 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24276.1553114810.1@sss.pgh.pa.us> Date: Wed, 20 Mar 2019 16:46:50 -0400 Message-ID: <24277.1553114810@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Peter Geoghegan writes: > On Wed, Mar 20, 2019 at 11:30 AM Peter Geoghegan wrote: >> Your work on test stability probably eliminated 98% of the problems. >> It's still early, but the buildfarm is mostly fine. > batfish just had a similar failure, this time in foreign_data -- two > lines of "DETAIL" output appear in opposite-of-expected order. > Obviously that's unstable in a way that it wasn't before now, since > every other animal doesn't have that problem. Yeah. My opinion is that we should just qsort the list of targets during DROP OWNED and be done with this. I'll post a patch shortly. In the meantime, would you mind cleaning this up: nbtxlog.c: In function 'btree_xlog_split': nbtxlog.c:269: warning: 'newitem' may be used uninitialized in this function nbtxlog.c:269: note: 'newitem' was declared here nbtxlog.c:271: warning: 'newitemsz' may be used uninitialized in this function nbtxlog.c:271: note: 'newitemsz' was declared here regards, tom lane