Re: Release notes for February minor releases

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 great:
> ...

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