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 1l2FMS-00031R-51 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Jan 2021 15:25:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2FMQ-0004Y4-Co for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Jan 2021 15:25:30 +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 1l2FMQ-0004Xx-6f for pgsql-bugs@lists.postgresql.org; Wed, 20 Jan 2021 15:25:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2FMM-00063W-Dd for pgsql-bugs@lists.postgresql.org; Wed, 20 Jan 2021 15:25:29 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 10KFPAuT594959; Wed, 20 Jan 2021 10:25:11 -0500 From: Tom Lane To: Heikki Linnakangas cc: Duncan Sands , Andrey Borodin , pgsql-bugs@lists.postgresql.org Subject: Re: Reproducible GIST index corruption under concurrent updates In-reply-to: References: <28663562-8489-4680-BC26-CAEADEB258D1@yandex-team.ru> <132baf64-3764-0351-750e-0443e74f1052@iki.fi> <907491b3-87c7-aadd-3fb1-be3c542b7fb7@iki.fi> <55ea6133-f2d1-0cc5-8ce5-333e373164ba@deepbluecap.com> Comments: In-reply-to Heikki Linnakangas message dated "Wed, 20 Jan 2021 12:04:23 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <594957.1611156310.1@sss.pgh.pa.us> Date: Wed, 20 Jan 2021 10:25:10 -0500 Message-ID: <594958.1611156310@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Heikki Linnakangas writes: > Pushed as commit 6b4d3046f4, and backpatched down to version 12, where > this bug was introduced. It will appear in the next minor release. I see you noted that REINDEX is required to repair any corrupted indexes. For the purposes of the release notes, can we characterize which indexes might be affected, or do we just have to say "better reindex all GIST indexes"? regards, tom lane