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 1ntfND-00088E-3G for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 00:59:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ntfNB-0007ZL-R5 for pgsql-bugs@arkaria.postgresql.org; Wed, 25 May 2022 00:59:37 +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 1ntfNA-0007ZC-R7 for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 00:59:37 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ntfN8-0005zq-6p for pgsql-bugs@lists.postgresql.org; Wed, 25 May 2022 00:59:36 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1B4025C018F; Tue, 24 May 2022 20:59:33 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 24 May 2022 20:59:33 -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=1653440373; x=1653526773; bh=qZZb31W+YU Ou3V3zZaQxIHCzUXD0RebNLZu81YMGrCk=; b=MXXkC++n2hAbCnr4n0ewiWnraj Z4+GrRsxzJgSl6gbEmRMpqDQ6OoMoFTNWOA4toZovOnA903QjaAITGa3fn9lsnLY ccg+TzCzyUJOqFNCZvGF0jcX/OEn23IXq4ZpD0lsJuCJeOLfLwisRo1ENFY4MfwT AHGLLeDRhcVDMp+HY9rGhBeBtCj7Ctae/oX+wqEH5Jd7lEv9HWKq+LL2GVN1FAIz sjBgc5F/9sSn6ZDIZb6/iOtZmices9oTh3GhX59vTOnzylrbzK5zxZLVBFL8Bs8q kaTjMRFGh5d39QoiUD6z/KArRtbI7LTsI+9t2KIAx28MHUa2iNEuz6FDn4yA== 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=1653440373; x=1653526773; bh=qZZb31W+YUOu3V3zZaQxIHCzUXD0 RebNLZu81YMGrCk=; b=opziOwzvNSC9HXsoM+JwCQgCcURnDcl6wH3aDt8TTVS/ vdGZGExn0R9LkM8/kUWcVP9GYyPcb5svSnr8yBbACV403e9yxhlnfvMwQLEu8lpv Jl6nKawzq5t0ThqIVfHY3IyXuDxKN2b7v/1pAaWhnjxqF2QF2R0O6KAoH9YkoGpB PJDtJNuaWcwlzG1GUxpPJt0xglDDx5iMvpZs/fOxT7qvHMob2Y49Uu2nQUVRxipP ZaO3v3dzZjfoTr/sB9VAD+C2oVUSDsFjaPSnnvZLu2zenSO7+1OO1gz5r0zhvd8+ TGXvJkH3+zHzx2DixqXUGXUGOYAPF40r6ktk1Q4/mA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrjeeggdegudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteelgeeg geffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 May 2022 20:59:30 -0400 (EDT) Date: Wed, 25 May 2022 09:59:27 +0900 From: Michael Paquier To: Andres Freund Cc: Greg Stark , Andrey Borodin , Alvaro Herrera , 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: References: <202205240902.bhkvu4lgljn3@alvherre.pgsql> <20220524163702.y2ct2gxk32zysxuf@alap3.anarazel.de> <20220524181542.cmec7rcv3vvvtze4@alap3.anarazel.de> <04B2AE56-C737-4F1E-ABEF-F88DA2280C5D@yandex-team.ru> <20220524190133.j6ee7zh4f5edt5je@alap3.anarazel.de> <20220524222433.ibl6dgkc6jrriska@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ff3T7Y8HXtaSB33C" Content-Disposition: inline In-Reply-To: <20220524222433.ibl6dgkc6jrriska@alap3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --ff3T7Y8HXtaSB33C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 24, 2022 at 03:24:33PM -0700, Andres Freund wrote: > On 2022-05-24 17:11:12 -0400, Greg Stark wrote: >> Aside from amcheck I wonder if we can come up with any way for users >> to tell whether their index is affected or at risk. Like, is there a >> way to tell from catalog entries if an index was created with CIC? >=20 > Not reliably, afaik. indcheckxmin won't ever be set for a CIC index IIRC,= but > it's not reliably set for a non-CIC index. When it comes to REINDEX, we recreate entirely a new relation for the concurrent flavor, dropping the old one. Hence its OID changes, while all the data from the old relation gets copied over. That's not much and you cannot use that for a CIC, still.. -- Michael --ff3T7Y8HXtaSB33C Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmKNf28ACgkQnvQgOdby QH1IxA//e/O7sGAxeTK6yrtjnbXVnORvfbKvAGWWjzWYsGaXw3Y0dlp2ex684FdM e9sZSTV1pjEYTvvUIO8tGLiHs8vGdwOWR7/hU7O3h62oVpAYoeWM3nqn0PUlvF+S tECpuP461kfZdBxM8iUSrJ6lI4xYKzNK3h16Y0KczxTwVflP+8jOwB437aFN+/wF i8gVfF9KMCltdyEyP6O8t0G3Oh2YvV7xRDitLQVldw/BthrZNgUjjMVQ5Hk4p9ND 4+W9qF202hvog9+qItk2b7uwzUSSkgrroI4W2vKBwlFPgyZPYlB2MgyX5atOwjid mTkYendtdx4LDUx/Ishk+U7c9MagTih03eafX4whUBaAUTGhehtCIzezG+5v6AMd //gZNu1fJfRFMFJPU9f7wP6yFB12h3gg+PGMaEOmJP96L9795WgLYi/cJqo4L+Lb TmkzdNd1dcsSmtQ9fycKEjFGb9HjAteiKQ6inm1PzTXA9p4raoFqIU5rMXMoXjJK GO44L6JSb2YU/RnlD5oFrNzm68Ldr7U13Q207FUdkLu2noJ2R1OHwNLP/g08Az8/ ik9KbrA9aU42L77/QnyDg1BKHBQgBo1O3IzLKgGT4TXb1OG5+RZYFh0c6zKkjeDQ KUejg9iD9ATktfWhF7OHv8D++itw11o/oKQcXJv0aAcZScKKGZQ= =pX6r -----END PGP SIGNATURE----- --ff3T7Y8HXtaSB33C--