Horton

Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY

Christophe Pettus <xof@thebuild.com>

View thread View on postgr.es
From: Christophe Pettus <xof@thebuild.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Michael Paquier <michael@paquier.xyz>, Peter Geoghegan <pg@bowt.ie>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Andres Freund <andres@anarazel.de>, Andrey Borodin <x4mmm@yandex-team.ru>, Петър Славов <pet.slavov@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-26T14:41:28Z
Lists: pgsql-bugs 

> On May 26, 2022, at 07:40, Bruce Momjian <bruce@momjian.us> wrote:
> 
> Uh, if people don't know if they have used CREATE/REINDEX CONCURRENTLY
> in PG 14.0+, they are going to need to run amcheck on all btree indexes
> and reindex all non-btree indexes?  That is going to be a painful
> message to deliver, and hear.  :-(

Unless we are 100% sure that amcheck will never return a false negative in this situation, we may have to recommend reindexing everything.  Ouch.

Commits

  1. Revert changes to CONCURRENTLY that "sped up" Xmin advance

  2. Fix possible HOT corruption when RECENTLY_DEAD changes to DEAD while pruning.