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 1nw0az-0006XJ-6N for pgsql-bugs@arkaria.postgresql.org; Tue, 31 May 2022 12:03: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 1nw0ay-0004Cg-11 for pgsql-bugs@arkaria.postgresql.org; Tue, 31 May 2022 12:03:32 +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 1nw0aw-0004CX-NH for pgsql-bugs@lists.postgresql.org; Tue, 31 May 2022 12:03:31 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nw0as-0006rF-8j for pgsql-bugs@lists.postgresql.org; Tue, 31 May 2022 12:03:29 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id EE13A320090F; Tue, 31 May 2022 08:03:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 31 May 2022 08:03:24 -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=1653998603; x=1654085003; bh=5WtofFAVpY CwMWX++bW0Ze60MG0x3IQG/nw0/zmNVxo=; b=AAiMF15TzlitXSfmyeakbfo7me K6z0KkIguIips60/zJVlg5Wnwz/VYrDYsLx9ep+sSUxv0swpwflhQVp+DhK/v/7H A9y4copo4y6F15K4S8oKiT3v1+/IAfJjtxgzRT86qRSGut/cGYatn35CXVpLVye7 c74q1EJMwYwqXiLDR54QbenzeVnYs5qmA4STe44lS0KrdmHab7WVNdwBjsbMM+QJ Mg+Et+/y+W3XfG9Nnq/XvTHFyD4VyAd575RlLk9uc5ZNKRJjN4Y8JyPudXZj8INx VBcMMdNit7DZp0LwNR+W3XtaIhA1Y5iYt05AckPCza2+4dhLUE7CzVWMsvZg== 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=1653998603; x=1654085003; bh=5WtofFAVpYCwMWX++bW0Ze60MG0x 3IQG/nw0/zmNVxo=; b=UWdUG9MBIrOClIR2yhImJc9mzXdgUWcPiN9kNf3+xmE5 1Iz7nzVBO10JA8cMSd6Z+sk3FjyutvOJUXqF4bMukGLfEaDPUfviTbbmri2opsnq YryxAYSvSGMfDUOKlb+H9FqOgfHKmSnJ8//yRtRbwjJMtz8hzme3PKvoWRTUXIec gbXORlSkzQcdftduFl5W+ADVyZp6KOeFDfXv/P2lViRCqC2ulTjrsAbplFu769rH ma6/5DuiwrVA56I3+QjRQphbLzQFYxWptKnsh0yy8sb7p3msx/L8otczsYQ3FByF ZJu378Hs2JINPIDE56iIwci/e28JOV08VvBOvP3rDg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeekgdegjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetteegvddvveeuieduudevkeff veevtdduleehleelffdtvdegfeegtdejtedtkeenucffohhmrghinhepphhoshhtghhrrd gvshenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm ihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 31 May 2022 08:03:20 -0400 (EDT) Date: Tue, 31 May 2022 21:03:17 +0900 From: Michael Paquier To: Alvaro Herrera 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: References: <202205310919.ziwjdn5e36nt@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jkaXt63UgKyUttLE" Content-Disposition: inline In-Reply-To: <202205310919.ziwjdn5e36nt@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --jkaXt63UgKyUttLE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 31, 2022 at 11:19:01AM +0200, Alvaro Herrera wrote: > Hmm, I wonder if it's possible to use an index ON tab (pg_sleep(100ms)) > or something like that (perhaps even use an expresion involving an > advisory lock acquisition, which is being held by the other session), to > widen the window. I have not considered the use of expressions to enforce a lock at this stage. I'll give it a shot, even if it comes to the abuse of an immutable function with volatile internals :) > The stop events patch that A. Korotkov posted [0] would likely be very > useful here. >=20 > [0] https://postgr.es/m/CAPpHfdtSEOHX8dSk9Qp+Z++i4BGQoffKip6JDWngEA+g7Z-X= mQ@mail.gmail.com Thanks for the reference. I've wanted to resurrect this stuff, actually, after dealing with 6dced63 to be able to have a stop point in the middle of a restart point. -- Michael --jkaXt63UgKyUttLE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmKWBAUACgkQnvQgOdby QH03IxAAhVd7q1MyvA0EUReTSZHaYueVd2klqiHv7OzH/6PZ46uHdYWbZLvprx+P tuYjGMxTjwwO9F3XRNdHMqNlvztEN0bbHkS2QJ3lDptpcG0gOHzotIadSW6I79lK TTGHPOSucCur57tXHOygSNMSS1IzBF30jZzwHIsLBVcEHCw608PQccDVefZaVbbq 0ycpg4YY88XpIgasRpuDazXXMa5sTo1IGQFmkl4LSsfvF4Wd1QznoJg2zWhoZp3y xWNnAQvgZbzahw5ZuZgU06iBqMWQNJwEbJF8IvjOars9D8Brv96ezhBpQdrj52ty UrHy4NIl8x++rzQpPP4prxHzVRLmJFqm9/2zYBf0Jgc5axTTB2nwTb2MBtrMxJZb sdX3NZrxFBJkq/4p/QJehN2j/RH41tbEc/vIfZghJ+xts2Oyybtn6sB1jivYIJlU PX9dY70n0h4RnaS1eqLqhEZjyfoJyYfFWodeF5yqnZwn+HLWGLd6e/3/Db8hUduc e74VSQ3dO63WQXLW1k3RHp6K9/EMu4PoAwNkJjGP4je+v2e91PdAuA3RKL8lGekk AEZlzbfuOMErN8shoUMOpWanht0IC0jWzP3tvTh1Y7XekhaNge3DKeapJW4oymP6 HSbOdAJZScmi79GW4myvmXmKKG0rJGSDp2lVOTa/bf/DolVf+DY= =lUZ+ -----END PGP SIGNATURE----- --jkaXt63UgKyUttLE--