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 1ml65y-0006wq-Kc for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Nov 2021 09:10:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ml65x-0000AK-Gv for pgsql-bugs@arkaria.postgresql.org; Thu, 11 Nov 2021 09:10:09 +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 1ml65w-00006p-2B for pgsql-bugs@lists.postgresql.org; Thu, 11 Nov 2021 09:10:09 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ml65s-00088k-1A for pgsql-bugs@lists.postgresql.org; Thu, 11 Nov 2021 09:10:07 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 847CA5C014B; Thu, 11 Nov 2021 04:10:01 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 11 Nov 2021 04:10:01 -0500 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=fm3; bh=k5GIrHjuWGZ4Xm9QnxSJU5917g6 BtW7YIsirXeSApDs=; b=c37hRN0hVY/iU6+ZhRTpedeiM+CGJAHxWD2VB8jIXUU LIvEZ5bFeEDf3yBtpfgMTA8Fu42Op1d4vJdkALjXMwztx4otWwBiK8SizKjC4f5K n+fQC626fCEv6nR3yA0bCFFTqRoTd4Z6Xs63ozegGwvUGBlbGwCd8K1otvR4R2BT xee+tdccWLna+CIu4FF4rzSeTMaoOb8hbYvZ4wgTDxlfjK11HC0YujEUn6vYXTjC +p1SwEfvNSpUgYY5C5CWu/AHmr4DVQV78wnhjCQIu+79a0uAs8DS0FgwGirthjG0 5Hu1D7SfDJOGKXXcb/pvcUECHk745/oo7YHJG3qzQ/g== 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=fm1; bh=k5GIrH juWGZ4Xm9QnxSJU5917g6BtW7YIsirXeSApDs=; b=FqHddCfvLdwzQsiK4LYU86 EzuX8xFI0ZfLfulDtX3F09cj8BdWyJ/hRvYPt4D6TdfES4Zrc2BkYcw3OExT+1CS mtHz+fgJM8U5rxRGAI36BpX0h9eYcEnkx8XIU3PBvDVn1ef6gGEH9GwVDCNr1ssC 10NLvQe/Fs3W1tHGmA6ZT0XejD4yIzmMRfuxSN2un2xphMX9yJilKBr0uGWGtgZa 1ljmyxjjaGq3hlrD8gPQWLR2K8hzT6SCTyVRdMFClUdKER+b00q8HWHUf91r8wCe lqOCcc4bgGuEx+uHMeGxXR3dVK+tIGRPHq6lkhVkZw82JTAzCn+V1Uc5XPm/oPMg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrvddugddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepvdegudeuhfdtueeltedtveejheeh ieevueeigeelteegleejleeiueeiheegvefhnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 11 Nov 2021 04:09:57 -0500 (EST) Date: Thu, 11 Nov 2021 18:09:49 +0900 From: Michael Paquier To: Noah Misch Cc: Andres Freund , Alexey Ermakov , Robert Haas , Maxim Boguk , PostgreSQL mailing lists , Peter Geoghegan Subject: Re: BUG #17268: Possible corruption in toast index after reindex index concurrently Message-ID: References: <20211108183646.r3y6pldylxngxwl4@alap3.anarazel.de> <20211108185317.fz42txmnkqdkpix6@alap3.anarazel.de> <20211108203641.whpia3pzjofellf4@alap3.anarazel.de> <20211109035624.GA940092@rfd.leadboat.com> <20211109050848.oe3u6mhtomkaoxrx@alap3.anarazel.de> <20211109054625.GB940092@rfd.leadboat.com> <20211109063119.ukcvdk7uvz7ks3pa@alap3.anarazel.de> <20211109064217.GC940092@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="X0cj1khhPiSlTbg5" Content-Disposition: inline In-Reply-To: <20211109064217.GC940092@rfd.leadboat.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --X0cj1khhPiSlTbg5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 08, 2021 at 10:42:17PM -0800, Noah Misch wrote: > On Mon, Nov 08, 2021 at 10:31:19PM -0800, Andres Freund wrote: >> On 2021-11-08 21:46:25 -0800, Noah Misch wrote: >>> Doing both sounds harmless. Regarding REINDEX CONCURRENTLY on a system >>> catalog, I bet that can still reach bugs even if we do both, considerin= g this: >>=20 >> Normal catalog aren't REINDEX CONCURRENTLY. It's just toast tables that = are >> kind of system-y, but also kind of not, that can be reindexed concurrent= ly. >=20 > Oh, okay. To be clear on this point, users cannot reindex concurrently catalog indexes and toast indexes associated to catalog tables, just toast indexes of normal tables. I don't know if any of you have been working on a patch, but I was cooking something. It would be worth checking if an isolation test could be written. -- Michael --X0cj1khhPiSlTbg5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmGM3d0ACgkQnvQgOdby QH1/qw/+OCMztP5vK/ePaEmiAnS0y3qvsMIfvTb7vnzb13gDACw3lErr8r043aHL lJ7r/ThMflgpml3WHwfR1hOnkLgy63/+SKmj9A4N47/KlDHVDtcIF5okKPBDFOSJ 1jIGegCX8mARP7mpMRl6bK8PSdeYDELRIAqE30ZNCCdkPtaRyxjGyUym/xRFRb1E GvtuTkv+11BTCtyOpSLYIo29LqEruspIg4yLn+owUYmCv+ctUzl1c09GHA/8HVaV 2ZziduBseL4KQ9idsQegojPqYOqlwTcSVyi5TASissAIWNstNK00xf+AoboAJJ7e Rc8UGzjDSCz2uxxL5GWyQfNt8HCR2ED4tf86yy6TzDlVYTayaYlnJ0U6aCNxO5JZ KUKU297tDxxmwQzMEkPmkxOfeMo3Rg2csutgUPDEhr2mjI1QW/WrkixG2oAytxRN +aaxmWo+30sE2pSEipvkvl6HXZV84LezGBm50AN5/S/zQDPKZE6o16nTS2emQffD Nk2obq0dZ3PZHGxiV1o0ewa5QUcsgKHEM7GzIlyOgonjaFOMjhdF7GgA2jgXc6F1 Yzq47QeIzKuanb5zATMAos5LWOTqtYYohBgY5CAw1bj5vRgNiRA2Qy14hMrYnkIl 9z/E69BwSODnR8dnPeg3wLj5R0TKrRhTuOcnad8gvYUnAByVnX8= =CBGQ -----END PGP SIGNATURE----- --X0cj1khhPiSlTbg5--