Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
x4mmm@yandex-team.ru
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: pet.slavov@gmail.com,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-05-19T04:22:44Z
Lists: pgsql-bugs
> 18 мая 2022 г., в 15:42, PG Bug reporting form <noreply@postgresql.org> написал(а): > I was able to reproduce this on PostgreSQL 14.1/2/3 locally on > docker instance and on AWS EC2. 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? Thanks! Best regards, Andrey Borodin. [0] https://github.com/postgres/postgres/blob/REL_14_STABLE/contrib/amcheck/t/002_cic.pl
Commits
-
Revert changes to CONCURRENTLY that "sped up" Xmin advance
- e28bb8851969 15.0 landed
- 042b584c7f7d 14.4 landed
-
Fix possible HOT corruption when RECENTLY_DEAD changes to DEAD while pruning.
- 18b87b201f73 15.0 cited