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 1nDgWA-0002KE-UJ for pgsql-bugs@arkaria.postgresql.org; Sat, 29 Jan 2022 05:43:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nDgW9-0003Gs-HT for pgsql-bugs@arkaria.postgresql.org; Sat, 29 Jan 2022 05:43:21 +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 1nDgW9-0003Gi-9X for pgsql-bugs@lists.postgresql.org; Sat, 29 Jan 2022 05:43:21 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nDgW4-0005RT-Hr for pgsql-bugs@lists.postgresql.org; Sat, 29 Jan 2022 05:43:20 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 170EF3201591; Sat, 29 Jan 2022 00:43:14 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sat, 29 Jan 2022 00:43:14 -0500 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=fm3; bh=ZLPhZyuArRwbIzZA3p6GWxKunnpaI6YdmADRsd gO4N8=; b=Yhnxvo/dxg/YjEgRCEU2vecYH7FCHTXD7ndUZYIYfDH+YWZrLzLSPI lL3nG4ZMBqnJcKsMpeIhyexnStj+vmmSoMw4j8cPKUC4TnEBI0C26DveyI2e7PkK H2nGJfbvJNVY/CEF+c9un/0qNL3oIL4Ckeixx/6f40cfcDCFbVa9KyUhMPJ8rIAs RqEPea9N3hwXfktL5AZZmh6fWOpMBXNGlo3QtN9RjsH9+5xV8TRt9lDYtehAvSQL V7PCjE2rl4epXv45ltl8SSxTzGTwnQ+PfH3o+/q2RrFaE8LsASrS0F2OhF6lMVUR 4S8hoDQ5QNOia34Nc2Q4YntvKnlUHhzA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; 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:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ZLPhZyuArRwbIzZA3 p6GWxKunnpaI6YdmADRsdgO4N8=; b=R2bWUc5Ti9iyHboqn1qejSb2TDFpe8MGb HsjtoNMLpR71FjuV7bN1NS0MrEs3a03L9qoKrIb1BrWt1Nc9kOB/mRlLNdwefn4d sm1TnVgWU7cFtGt20As/l3WkxL+EEjMCxMoBOI3tp9cCm8yIkvmXDVpG5hjRtzNC DCYLZTblv2ybRjQ5GxtrbeZlHQJIq9h59bCFEN8Upxf5MHGakltE3sKgYZdsSJqR bm5+0uYPyPM5dP0NdX67xP7In5OtqTdGKJuTb8TnaOHVwhtcMiE/uUal7jiveNIJ 7Hl1TWxXYFXekyfV0Vo3p66bWEhRAmCzPNhDPLSORpsncgs1W42XA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrfeeigdekiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepvdegudeuhfdtueeltedtveejheeh ieevueeigeelteegleejleeiueeiheegvefhnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 29 Jan 2022 00:43:11 -0500 (EST) Date: Sat, 29 Jan 2022 14:43:08 +0900 From: Michael Paquier To: Peter Geoghegan Cc: Noah Misch , Maxim Boguk , PostgreSQL mailing lists Subject: Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table Message-ID: References: <17386-2227568627fb44ce@postgresql.org> <20220129023418.GA2452893@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DfEoysDLhbIT8VXn" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --DfEoysDLhbIT8VXn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 28, 2022 at 07:00:31PM -0800, Peter Geoghegan wrote: > If I had to guess, then I'd guess that this has something to do with > orphaned HOT chains, like those we saw in the bug report that led to > bugfix commit 18b87b20 (which is in 14.2 but not 14.1). I could easily > be wrong about that, so take it with a grain of salt. I find it a > little suspicious that we're hearing about a REINDEX CONCURRENTLY > problem in Postgres 14, which is much less mature than Postgres 12 > (where REINDEX CONCURRENTLY first appeared). Possible, but hard to say without an actual proof. Maxim, if the problem is reproducible easily on your end, could you give a try to v12 and v13 and see if it happens as well there? -- Michael --DfEoysDLhbIT8VXn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmH00+wACgkQnvQgOdby QH0Elw//boAX/DUWBW/C1t+wywMzUk4pcm3TdAiZDK8o+zUIbcTl+3sB+V4OhH4Y OntW1klTG1vwnwq99FusEfzdy6UGmgTAQAd46Oi5QBdJ62fCk3KcTg2okUZPPTiN i6m+gxUMGy2DUvCClB4NxnLqXcGI6xh4QHZMaUqdUkkvjCB0qPQ48L/lLmIopvn5 RgE1tJOiCKkE2fYK8EaXMjIOzJrhC4YgfjNbTpzmk5EVkOAtouNw4hAQ7oOzU1Xy vGwS5QDokq8aQeGOoc4k2wZ4uwEYIOE571PdBQo7bdYpbg1+bcSdusmGCcm8Dcw6 xHYb7IBW2Q1OreHRfeRb2dHrj7GeNrBtLJvAMfXa8bcAFvEAoz0m2nV24CPh96xE Uzd/WR/FajYM0SpEm0kC3U2dYF/cPllCfX6UVow/HSIlGCP/CJV3nNbLH7f1DJVR 1Z0Qx+ciAojtu4XTNTGaddWNx9HPLSQEXGpCKgrgh8F4yZInRbyfBPDwFYqqF4wr cKevEset73QsaVpkhSqMxnZG7YPxzMpuoaAb80b4qK9HwAwBbGY4Ou0og0NL9mJ6 vQpiCoDave5/d6OJGblHQ9uMsvv8NpsClNHrd4RVcnsejexmNNa/w/4a80JYLBtG /Fx5gSjW7uZTlyRlUTkVLr5fA+NVoPjLma3A7Pzpgq28AnJwYU4= =qX7n -----END PGP SIGNATURE----- --DfEoysDLhbIT8VXn--