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 1nvmF0-0001s8-S4 for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 20:43:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nvmEz-0003Uo-Kv for pgsql-bugs@arkaria.postgresql.org; Mon, 30 May 2022 20:43:53 +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 1nvmEz-0003UE-3Q for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 20:43:53 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nvmEr-00085e-Mk for pgsql-bugs@lists.postgresql.org; Mon, 30 May 2022 20:43:52 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 260015C0144; Mon, 30 May 2022 16:43:44 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 30 May 2022 16:43: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=1653943424; x=1654029824; bh=T 2rkza/TSx3qHULNVzwwiiil3yCtF9Ai3hS+2uujA00=; b=CCBGJm68Tk8EIXZwP w3eiY1GDMk21PeOw39TgNv9RV+0na72YTahZycZmcnUEjQo0uFWDQ0zgXCLtKe4B Saq8aqbei0tz+DDJZ45J1tgXfBGcHHuUgM+prn2X/kQbeGgqDlgJbirnMWaidZ6K gbS/GtyE8TNRFclfZ762Ydp5u5HQvBXWs+uae7LAvCENFpNsyJeBITa0+8s8O6hh mv+AdrA8rqO3mxFsn7xbPo3+CBKH8Njhhm91cPKZdROiKpiK5DDZFSP66EOHuWjK EIupqwuMTKrMM4uxoNT6W6AVKlqx8ZdNGXh1YRCpAAz6qcSLlkFD/RdbIXpDe4qn ytTzQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeeigddugeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesmhekreertddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepudelkeekgfdttdettdekgfduvdeiffelteegjeeihfet heekveeftedtuddvhfeunecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 May 2022 16:43:43 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 052822A0331; Mon, 30 May 2022 22:43:41 +0200 (CEST) Date: Mon, 30 May 2022 22:43:41 +0200 From: Alvaro Herrera To: Andres Freund Cc: Michael Paquier , 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: <202205302043.36u46jg7fyhs@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="47cl72nybveaxqc3" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202205302040.wsrcd745yrhb@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --47cl72nybveaxqc3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On 2022-May-30, Alvaro Herrera wrote: > I'm not sure I understand what you're saying here. I understood that > both RIC and CIC are affected, so the reversal is of the following > commits: > > c98763bf51bf Avoid spurious waits in concurrent indexing > f9900df5f949 Avoid spurious wait in concurrent reindex > d9d076222f5b VACUUM: ignore indexing operations with CONCURRENTLY This is the full reversal in branch master. I'm unable to reproduce a problem with the v3 patch Andrey last provided, however. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Tiene valor aquel que admite que es un cobarde" (Fernandel) --47cl72nybveaxqc3 Content-Type: text/x-diff; charset=utf-8 Content-Disposition: attachment; filename="0001-Revert-concurrent-indexing-changes.patch"