Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIgEF-00085R-KJ for pgsql-committers@arkaria.postgresql.org; Sun, 29 Mar 2020 22:16:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jIgDh-0001AF-O8 for pgsql-committers@arkaria.postgresql.org; Sun, 29 Mar 2020 22:15:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jIgDg-00019Y-Ji for pgsql-committers@lists.postgresql.org; Sun, 29 Mar 2020 22:15:53 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jIgDd-0006Xm-Fd for pgsql-committers@lists.postgresql.org; Sun, 29 Mar 2020 22:15:51 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 7580D6E6; Sun, 29 Mar 2020 18:15:47 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 29 Mar 2020 18:15:47 -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=wB6iALZw1mE3jfAgKPqBcdbeQ/e 7/r8JlLDUhu5aai8=; b=hbWY9Q2yflSybem24tmPcsw8Bw+Nfu5eLT326UQhAv/ jyIb04R6MzZBefWrSF69nsRWpWKHhS/lJYehDIxU19t0T0JAlOZ556ncS+iIiMiI /vRj4ZKCbFTkNDksBR3Jp0nV+jyik1rhBK1fRaKK4sOsqw3worrBy/vDpd6dWEzb h2OHvgqexlu8zE3TQP7dmO3JAh+3FQE70rfLEzfeo+tXMs3s/fzVjYvF330/Hjcg wtMAK0Z4aj1LWiAql26IkgRMZZ0p9Q/B/hjvu1ktCRi56oZGLoDpo39AqgvCgoca Y16FYUpIciE5/YMd2QBcuqa0uxd0d3Uj3raW9PcKbZw== 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=wB6iAL Zw1mE3jfAgKPqBcdbeQ/e7/r8JlLDUhu5aai8=; b=w2MoCEbZTLTKYuptQEc8X8 DWEzyPE+Cahe1ECK2UDvnNmZcdjukfLhbjTaLAuDeuDbItpRfUO9QBFuM3qDPDyr /vErULwwhp2EnYa1OgWrLs3FSJTTCuyl6OLcHpeD1qMhjNSmchd1rxDgG9P9ki4c m00q8puZdjksVpBZQXVURG5fSYe5ccS9lrCY+fbRFsDnZDPZvwWY1urcU11xuVVq AqrMShJITx8lH2/1yRLTbMtt/JecIVDDMPnI2oolbI30L1Eevcti0iRSDuuceuH4 60TKEua2UU+5iV7DkPTPSVBAKkX4o1+BkKC41mAWVHhvs30GKc3/urtI4qZFwD7Q == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudeigedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucfkphepie ejrdduiedtrddvudejrddvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: from intern.anarazel.de (c-67-160-217-250.hsd1.ca.comcast.net [67.160.217.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 11541306C8E8; Sun, 29 Mar 2020 18:15:46 -0400 (EDT) Date: Sun, 29 Mar 2020 15:15:44 -0700 From: Andres Freund To: Peter Geoghegan Cc: Tom Lane , pgsql-committers Subject: Re: pgsql: Add deduplication to nbtree. Message-ID: <20200329221544.w2ihd7u3qdztnbr2@alap3.anarazel.de> References: <27003.1583087095@sss.pgh.pa.us> <29676.1583090977@sss.pgh.pa.us> <5838.1583100843@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 2020-03-01 16:09:37 -0800, Peter Geoghegan wrote: > On Sun, Mar 1, 2020 at 3:01 PM Peter Geoghegan wrote: > > I am happy to add parallel-to-_bt_form_posting() assertions about > > alignment to _bt_form_posting(), to nail it down completely. Plus I'll > > add the assertion I suggested already. Once I commit a patch with > > these two new assertions, I think that we can consider the matter > > resolved. Does that seem reasonable to you? > > I was thinking of the approach taken in the attached patch. It more or > less copies over the assertions from _bt_form_posting() that did not > appear in _bt_update_posting(). It seems, based on discussion on this thread and private inquiry to PG that we're going to silence the warning, as there's not a good resolution? I've for now marked the issue as a false positive, and added a reference to this thread. But I think we should just mark it as ignored in that case? Is it perhaps possible to silence the warnign with somethign along the lines of Assert(nhtids + vacposting->ndeletedtids == BTreeTupleGetNPosting(origtuple)) I don't know this code, but it looks like that'd have to be true? Perhaps that'd be enough to silence coverity too? - Andres