Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvg7h-0005yf-F2 for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 14:11:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nvg7g-0008RV-8y for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 14:11:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvg7f-0008QM-9S for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 14:11:56 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvg7X-0005bd-HN for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 14:11:54 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 804F63200488; Mon, 30 May 2022 10:11:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 30 May 2022 10:11:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1653919903; x=1654006303; bh=4 L66gcmIlIiFuyoWRq2gIO84a5OsoXtUlkcXeQlt42I=; b=A03PvnKkxNbSZhb9b +Be7lN9DqNwpIwcf3P5QSLDXZyU83RPQix3zWB3GLCayCHjOFEItcam5yvUmYrJz kao83VMwXRL74LBt8ZqnO6Ia+pDsq/JHBoJK1x/DRk8mJHQxMOTdg95dVThEqcyk M4mMI6MlPxUsV+HIM2cvrx8k7Tz2v39U+59Ci+/SoWMT74ZAp0Y6xvJ3q4AvE7ra +6I5pvtD54Cgd49vhhow4IBjnlZprdd2CTQbAz1lyAfwlLQByleroctjxOmJZLyC 6dtvxPKYtlBZSBi4egwql6/hb4UPH8uPez2u+neWn4OC3kdIQQCVEh+mD+xlyw2r luwRQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeeigdeilecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 May 2022 10:11:42 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 9B09B2A019A; Mon, 30 May 2022 16:11:39 +0200 (CEST) Date: Mon, 30 May 2022 16:11:39 +0200 From: Alvaro Herrera To: Michael Paquier Cc: Andres Freund , Andrey Borodin , Robert Haas , Peter Geoghegan , =?utf-8?B?0J/QtdGC0YrRgCDQodC70LDQstC+0LI=?= , PostgreSQL mailing lists Subject: Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY Message-ID: <202205301411.ltoz4mf6nfmq@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-May-30, Michael Paquier wrote: > > Was there anything else running on the system? c98763bf51bf also needs to > > reverted, of course. > > Yeah, I agree that we'd better revert c98763bf for the time being. > And f9900df on top of that? Yeah, both commits need to be reverted, since the latter depends critically on the former. I'll get the revert pushed soon. > I was trying to think of ways to get an isolation test out of that, > but that proves to be sort of tricky as we need to manipulate the HOT > chains after the validation phase has begun with the snapshot from the > build phase. It is easy to block before the validation transaction > starts, like in WaitForLockersMultiple() beforehand, though. Hmm. I suppose for the next try of implementing a feature like this, we'll definitely want to incorporate some tests that can catch problems of this sort. But I don't think we need to come up with something right now. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/