Re: Release notes for February minor releases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Banck <michael(dot)banck(at)credativ(dot)de>
Subject: Re: Release notes for February minor releases
Date: 2022-02-06 18:09:41
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)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?

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

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.

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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-02-06 18:39:36 Re: [RFC] building postgres with meson
Previous Message Tom Lane 2022-02-06 17:24:50 Re: [PATCH v2] use has_privs_for_role for predefined roles