Horton

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

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Michael Paquier <michael@paquier.xyz>, Петър Славов <pet.slavov@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-30T19:08:04Z
Lists: pgsql-bugs 
Hi,

On 2022-05-29 09:15:15 +0500, Andrey Borodin wrote:
> > On 29 May 2022, at 00:34, Andres Freund <andres@anarazel.de> wrote:
> > 
> > c98763bf51bf also needs to
> > reverted, of course.
> Reverting c98763bf51bf fixed both tests. I did not understand that we are going to revert it too.

We're going to need to revert both, but I don't understand why c98763bf51bf
would affect this your tests. Afaics it should just affect CIC, not RIC. Could
you make sure you can reproduce the issue without c98763bf51bf reverted?

Greetings,

Andres Freund

Commits

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

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