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: Andres Freund <andres@anarazel.de>

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-28T06:26:55Z

Lists: pgsql-bugs

Attachments

v2-0001-Add-TAP-test-for-REINDEX-CONCURRENTLY-with-HOT-up.patch (application/octet-stream) patch v2-0001

> On 28 May 2022, at 04:13, Andres Freund <andres@anarazel.de> wrote:
> 
> Seems like we should add a test for HOT vs CONCURRENTLY?

This test fails on my machine with 35K transactions. And fails in ~50% of cases with 30K transactions.
And this seems like a lot of work, ~10 CPU seconds. How can we reduce the time to reproduce?

Best regards, Andrey Borodin.

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