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 1jdqoC-0000GX-TH for pgsql-bugs@arkaria.postgresql.org; Wed, 27 May 2020 07:49:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jdqoA-000068-E9 for pgsql-bugs@arkaria.postgresql.org; Wed, 27 May 2020 07:49:02 +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 1jdqoA-00005u-85 for pgsql-bugs@lists.postgresql.org; Wed, 27 May 2020 07:49:02 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jdqo7-0005F6-Pv for pgsql-bugs@lists.postgresql.org; Wed, 27 May 2020 07:49:01 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E96835C00A8; Wed, 27 May 2020 03:48:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 27 May 2020 03:48:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=hR2OjPkxuoqQCWcqXwAMCawwwmI MuBMGKxzsCSBsp9s=; b=ATdaDaEcbasMzk/Zfhj9jfuBNXN+vg5SjykoSbE0N40 fP8suM7bdiJ2cK0lQtK3IBP7jIHXg3vJuq9PfCtckkgo6egqFdMCSaLCogxUEbIB 9l/06X+vQaj94VW1E441/MxF4XHX8bdnEAFAsgcz699SPw3cSBDDKCt/mGh5JXQ7 FfdbmvCpYusXoslyZ30wLAzsDdtKwOn3Tel7ppBio79MRJKi6yfuBHT2UIxvFooM avURCkxC3q8evPmZfFAZPx9wl2yIlqiGCdXm9ZdqLRlMJKxp+P+vB5MnBJqQ3g0q yUea9j42wfr2ohoCR0XjQuPI3yVaWeTAf7hZ67NUZoQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=hR2OjP kxuoqQCWcqXwAMCawwwmIMuBMGKxzsCSBsp9s=; b=h/ggqO0PiWs0UXbqyWzHGY iRGbEO3IOfTvLi/bGUayHQarje63Q90nI+FbZFzPP2fU5afRzXhrE9J85s/FsUcg uQBuv9+UtAlHWYlhzN39ORJuSgHgSsSLoya+t6ajssZJs5Qn1+O5iimTC/08D1zs HMSVoNgVIaGq+0UO5zbW/8VS9KjPnCOdspaNUnr82dJmRqOmEkgftk1Sgqachf/w cW7BvZ9xfAAuLAT20hw22H1i/AvmUfDIWs0n6JVY3z6vZv+EHJ7pMaRLNh6Dkezc uEy7bGcSHE7AZHf9LyeZTYf1hcLMRLpLan3eu1/2JmFNk8D2v3tfsxONR3zx6jRw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddvfedguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enfghrlhcuvffnffculdefhedmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepffdufeeflefghfekudekkeev vddugfeiteekkeduleefvefhhffftdduffeiuedtnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucfkphepudduuddruddtvddrudektddrudekheenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprg hquhhivghrrdighiii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id F346E3280064; Wed, 27 May 2020 03:48:56 -0400 (EDT) Date: Wed, 27 May 2020 16:48:53 +0900 From: Michael Paquier To: Tom Lane Cc: Andrey Klychkov , Peter Eisentraut , pgsql-bugs@lists.postgresql.org Subject: Re: Re[2]: Message-ID: <20200527074736.GG103662@paquier.xyz> References: <1590486572.205117372@f500.i.mail.ru> <1590501239.839686286@f437.i.mail.ru> <17907.1590504619@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Bg2esWel0ueIH/G/" Content-Disposition: inline In-Reply-To: <17907.1590504619@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Bg2esWel0ueIH/G/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, May 26, 2020 at 10:50:19AM -0400, Tom Lane wrote: > 2. Is reindexdb handling the failure sanely? While I'd agree that > this behavior isn't especially desirable, it's the price of using > REINDEX CONCURRENTLY. On failure, you're expected to clean up > manually by removing the leftover invalid index. Perhaps the > documentation isn't clear enough about that, but I don't see a > bug there. There is a paragraph about the handling of invalid indexes on the reindex page: https://www.postgresql.org/docs/devel/sql-reindex.html#SQL-REINDEX-CONCURRENTLY "The recommended recovery method in such cases is to drop the invalid index and try again to perform REINDEX CONCURRENTLY. The concurrent index created during the processing has a name ending in the suffix ccnew, or ccold if it is an old index definition which we failed to drop. Invalid indexes can be dropped using DROP INDEX, including invalid toast indexes." -- Michael --Bg2esWel0ueIH/G/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl7OG2UACgkQnvQgOdby QH1x2hAAoX/yR+06NwPkiCWxq8S0mqUh7m00KUzi5A3Sb24FQei/ew3AatCN7kxn M3LEyEzfJ5+KZbEej7cWif9gqb8oh4JGtEykFZujrbrnOjD3QiphBA1i2mDtMI+S mzQ2WRfJr8JFJ1C7D/RUPAMgAIh/8H7IrHkYYqzT+/oi8GHh4imOL152KLj2bERf +r3FfKk/kSfUrXRYkA7UE2vsqpzoROdzF9J5QCMjgIdl3xIF+1OpkII2sTDnfzj2 5cfz9TVvlV5sPv8/XiZ36OKKmra2WSssajx4SP/NJBJ9IbgFGpJ9GJScfizJl/Wt g/0Yv49ulmvwXxgaxtK1rzWUTIeGOyUZIJ72v7qorLnq68uYhwhWjUXels5wwAYb XlcmpNhP9umX67mrMh2NDdaCryYewxdaMTwyjK8I/8YyKgNxQ/BqpLYgxNnP4RJ0 17wHj+r335Y/Bwdbc5+8hia11nTTk3NEmqtJl1Gu2BzWyQa0G9fm8ukqWMsoiVsN 8XFAqtsKcwJHRHMCEwxNahQf7Cb0oaf9p8eT07G/02Rn02rHRcx8bfZBZ0uL4diS 8Yio+dSwBTu3xSgE0lixZupqzDruGwCIW48xDSkhW3jxQLDCs6EfyXf4qeKZsjGI 8fEAEiLbdH0o/eo+1N/GHdEEnEepd7NTwDmfhWnhMdPtJDgAg20= =w8aG -----END PGP SIGNATURE----- --Bg2esWel0ueIH/G/--