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 1nu4LV-0005Al-QH for pgsql-bugs@arkaria.postgresql.org; Thu, 26 May 2022 03:39:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nu4LT-0001TG-J9 for pgsql-bugs@arkaria.postgresql.org; Thu, 26 May 2022 03:39:31 +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 1nu4LT-0001PR-AI for pgsql-bugs@lists.postgresql.org; Thu, 26 May 2022 03:39:31 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nu4LQ-0006W0-9L for pgsql-bugs@lists.postgresql.org; Thu, 26 May 2022 03:39:30 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3506A5C01F0; Wed, 25 May 2022 23:39:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 25 May 2022 23:39:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1653536367; x=1653622767; bh=fdUimDdEMj maQCNMNVBAvnfZeYS6A5BKcOR0vHSdM4s=; b=hwh5KXUx+zprkxXHsWvIB1FmQ1 PL+arHNgCsQI60+KJ17c5m+HqKNmGPiud30iyNyE2EB+kjph1sFQ40bL8POLMWnB JeSAm/xqTkIPy0B/OSEqF2p7bNkefIMxBeY06h4mg1fWTX4XoIrVo4NdkNDZ4biN WTikzpL5vF+3dAtJLrlIL2f07+rA8kdC4XGrRowDpqd1mnvfINetABqHePXDXybm w/XQPlwzUADO4h4BDVGeKcPCz+2vxTExX1Gz9gP7rpteqo/dqJk892BGl8wGY+vG swunvv3Jl1RWLKLIrsY+WSr1czEYHauFxk9T4B5AaS1LYomUWxT5buFYMT4w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references: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=1653536367; x=1653622767; bh=fdUimDdEMjmaQCNMNVBAvnfZeYS6 A5BKcOR0vHSdM4s=; b=uMWxu2JHsl53Ek0V1TIQo/ru3RVwEBI4bDk8SyHPAr7I ztFZU4ZxiDupDXlmyHPQApIgfnDErdfMGeCd9sSLeMLuOLpZfQ5z3j8YtVfsEfJP 1QrZ3LNt94DM/gt+ePRuMeH3qNpUxDRurJE1kHz+QtBT0PZcj8OrwtL1PVMPkino jgOyLYUcqWB0ua89awpAfo74IagYhk+xZLGVC8l8N/5m+g9/ZIQ8+zG2fhFZulkQ FZ9dg0BtU7mYy2ShVfqHzwIuwN9QfWZi8vDq4p3dRDJ+ng+dNg355q/niNf9iDoC mbTndViZJtgWHrNKLsrfO0lil/nj/qHQifpw8KVZJg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeeigdejfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteelgeeg geffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 25 May 2022 23:39:24 -0400 (EDT) Date: Thu, 26 May 2022 12:39:20 +0900 From: Michael Paquier To: Bruce Momjian 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: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bq6lvTW57VVLlmtO" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --bq6lvTW57VVLlmtO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. -- Michael --bq6lvTW57VVLlmtO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmKO9mgACgkQnvQgOdby QH1Ffg/+NedEjxgYP/YamWN+JqaGlMK0V3VRfN8qkD4u3ea1EC9NqU1qjr28h+rC OMRCYNw5xAPGXO4mfh1CmHqFyfeUpvgtY2Emn56/82ug/rVzImQVNMkzjowEs/nA np6PlzkodPntfC/X+Su7yXBrINixET1pO6WBKAczqlht9jAW1g4h2rkC2N+Fx87H mHDjOabHbMfuCE6HcVcdgEnd2tb8ejRb+gBpklYnj8vqH3u/9uKTigaEF1fITgtw sUWIB58PETw8xWQanc5L5Pdjk9kOg9tF7Ztlla2NhcegGHkO0cTKlsS2etsNBybx Q3yJFvkmEiKyPneZPssInfWGQCf7fgKZDYGN8JmdxuNUvfB+bMOSHa8Mq0K2qWhA d1rblFk0dqd1+OJEbqlWp/BqpOaIgzCcTL6mbfJpyzoNO0Qlpnx/hYNrQm3So5X9 FvUuuRN8lRpaz3T5pb2gThsPSK3Hlxu/8sNHk8+MXt6Om3nS1B1C021cY0G6/H4K acsQxgENxUg8SPxB9JjrU9F6SlzLq4/jvJFzXsBXfK3WPypu6ODGlMFUTmMturBB WtS56Po+CliTeJmJGngTppUoOjPCAQeWiad8mG8d1PnmPTeTMC+ElXAjhPztG1eO OeBzEahVv4saQ/KtQxMImhp0gV+V3y9884+NK5uuQjSxnJcNRIw= =gGMn -----END PGP SIGNATURE----- --bq6lvTW57VVLlmtO--