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-hackers-owner+archive@lists.postgresql.org>)
	id 1nGlz5-0006Vv-SH
	for pgsql-hackers@arkaria.postgresql.org; Sun, 06 Feb 2022 18:09:59 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nGlz4-000488-EU
	for pgsql-hackers@arkaria.postgresql.org; Sun, 06 Feb 2022 18:09:58 +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 <tgl@sss.pgh.pa.us>)
	id 1nGlz4-00047t-5O
	for pgsql-hackers@lists.postgresql.org; Sun, 06 Feb 2022 18:09:58 +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 <tgl@sss.pgh.pa.us>)
	id 1nGlz0-0007TK-FC
	for pgsql-hackers@lists.postgresql.org; Sun, 06 Feb 2022 18:09:57 +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 216I9ftt734658;
	Sun, 6 Feb 2022 13:09:41 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@lists.postgresql.org,
        Michael Banck <michael.banck@credativ.de>
Subject: Re: Release notes for February minor releases
In-reply-to: <20220205225859.yru3hvcww7dnorbr@alap3.anarazel.de>
References: <425850.1644004739@sss.pgh.pa.us> <20220205225859.yru3hvcww7dnorbr@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Sat, 05 Feb 2022 14:58:59 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <734656.1644170981.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 06 Feb 2022 13:09:41 -0500
Message-ID: <734657.1644170981@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/734657.1644170981%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> That's obviously to complicated for the release notes. Trying to make it=
 more
> understandable I came up with the following, which still does not seem g=
reat:
> ...

How do you like this wording?

     <para>
      Fix corruption of HOT chains when a RECENTLY_DEAD tuple changes
      state to fully DEAD during page pruning (Andres Freund)
     </para>

     <para>
      It was possible for <command>VACUUM</command> to remove a
      recently-dead tuple while leaving behind a redirect item that
      pointed to it.  When the tuple's item slot is later re-used by
      some new tuple, that tuple would be seen as part of the
      pre-existing HOT chain, creating a form of index corruption.
      If this has happened, reindexing the table should repair the
      damage.  However, this is an extremely low-probability scenario,
      so we do not recommend reindexing just on the chance that it might
      have happened.
     </para>

I'm also going to swap the order of this item and the TOAST locking
item, since that one is seeming like it's much more relevant to
most people.

			regards, tom lane