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

Петър Славов <pet.slavov@gmail.com>

From: Петър Славов <pet.slavov@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-19T05:24:27Z
Lists: pgsql-bugs
На чт, 19.05.2022 г. в 7:32 ч. Michael Paquier <michael@paquier.xyz> написа:

> On Thu, May 19, 2022 at 09:22:44AM +0500, Andrey Borodin wrote:
> > Uhm, that's very...interesting. I'll look closely next week. Though I
> didn't have a chance to reproduce yet.
> > We have fixed similar problem in 14.1. And now we have very similar
> > TAP test to you reproduction [0]. How do you think, what's the key
> > difference between TAP test and your repro?
>
> Interesting, indeed.  Another question I have: is this limited to v14
> or are you able to see it in older versions?  REINDEX CONCURRENTLY has
> been introduced in v12.
> --
> Michael
>

Hi Michael,
Yes I have made the same test on PostgreSQL 13.7, but the reindex works as
expected there (no issues).
I haven't  tested on older versions.

Peter

Commits

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

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