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 1nuEex-0006AJ-HE for pgsql-bugs@arkaria.postgresql.org; Thu, 26 May 2022 14:40:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nuEew-0007ML-BN for pgsql-bugs@arkaria.postgresql.org; Thu, 26 May 2022 14:40:18 +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 1nuEew-0007MC-3P for pgsql-bugs@lists.postgresql.org; Thu, 26 May 2022 14:40:18 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nuEet-0008NP-IG for pgsql-bugs@lists.postgresql.org; Thu, 26 May 2022 14:40:17 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1nuEeh-00DZCM-Sh; Thu, 26 May 2022 10:40:03 -0400 Date: Thu, 26 May 2022 10:40:03 -0400 From: Bruce Momjian To: Michael Paquier Cc: Peter Geoghegan , Robert Haas , Alvaro Herrera , Andres Freund , Andrey Borodin , =?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: References: <202205251643.2py5jjpaw7wy@alvherre.pgsql> 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: Archived-At: Precedence: bulk On Thu, May 26, 2022 at 12:39:20PM +0900, Michael Paquier wrote: > On Wed, May 25, 2022 at 11:17:33PM -0400, Bruce Momjian wrote: > > * Caused by CREATE/REINDEX CONCURRENTLY > > Yes. > > > * No way to detect which indexes were created concurrently > > * amcheck will be required to find corrupt indexes (options?) > > amcheck would help for btree, not the other AMs. I am not sure but > there could be other symptoms that may not be detected by amcheck? > > > * Heap is fine, only index is corrupt > > Yes. > > > * Bug since PG 14 > > 14.0, yes. > > > * Not known why reports are only appearing now > > * Feature will likely need to be removed rather than fixed > > Trends go in this direction. It does not seem like there is a > complete conclusion on this point, either. Uh, if people don't know if they have used CREATE/REINDEX CONCURRENTLY in PG 14.0+, they are going to need to run amcheck on all btree indexes and reindex all non-btree indexes? That is going to be a painful message to deliver, and hear. :-( -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson