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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nFj7r-000321-4d
	for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 20:54:43 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nFj7p-0006lk-Bv
	for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Feb 2022 20:54:41 +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 <tgl@sss.pgh.pa.us>)
	id 1nFj7p-0006lb-3h
	for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 20:54:41 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nFj7k-0005ds-MW
	for pgsql-bugs@lists.postgresql.org; Thu, 03 Feb 2022 20:54:40 +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 213KsSw2294530;
	Thu, 3 Feb 2022 15:54:29 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Peter Geoghegan <pg@bowt.ie>, Dmitry Dolgov <9erthalion6@gmail.com>,
        Alexander Lakhin <exclusion@gmail.com>,
        Matthias van de Meent <boekewurm+postgres@gmail.com>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17255: Server crashes in index_delete_sort_cmp() due to race
 condition with vacuum
In-reply-to: <20220114021549.m6ugihzjmsunv3jd@alap3.anarazel.de>
References: <20211111030821.2xxl75qfkynaga4j@alap3.anarazel.de>
 <20211116023918.5g6d6izevronx76m@alap3.anarazel.de>
 <CAH2-Wz=w6wVbat4B=HQTzim5ki=NyPhT6FxWPST=tN2+BjHrpw@mail.gmail.com>
 <20211122175914.ayk6gg6nvdwuhrzb@alap3.anarazel.de>
 <CAH2-Wzk+=kCS5SMMQ++s5vX9NmWKxJmOBfU2wqR-n78cOYFgfA@mail.gmail.com>
 <20211122223436.ov3qa27pakxay6z7@alap3.anarazel.de>
 <20211211045710.ljtuu4gfloh754rs@alap3.anarazel.de>
 <CAH2-WzkNr0t2e9Vr8T8QZNzA1Vze9C7s5-=61nhz2gHAooW05Q@mail.gmail.com>
 <20220112192508.vibr6o64h7sy7mbw@alap3.anarazel.de>
 <CAH2-WzkuGdm6-7euVQaGBK=BD6sOZJckgnkx3XWwYNB_ysjGbQ@mail.gmail.com>
 <20220114021549.m6ugihzjmsunv3jd@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 13 Jan 2022 18:15:49 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <294528.1643921668.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 03 Feb 2022 15:54:28 -0500
Message-ID: <294529.1643921668@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/294529.1643921668%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
>>> I'm just struggling with / procrastinating on the commit message, tbh.=
 The
>>> whole issue is kinda complicated to explain... :/

> After struggling some more, I *finally* pushed the fix and the new asser=
tions.

I'm writing release notes and wondering what I can tell users about
how to detect or recover from this bug.  Is a REINDEX sufficient,
or is the presence of the bogus redirect item going to cause
persistent problems?  If the latter, can we provide some amelioration?
"Your data is broken and there is nothing you can do about it"
is not nice to be writing in release notes.

			regards, tom lane