Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY - Mailing list pgsql-bugs

From Петър Славов
Subject Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
Date
Msg-id CAC5T6EDJF5NJh_tdiddaxt8vnvB3ViAR6iS9VzAy1Fd-ubRsZA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs


On Thu, May 26, 2022 at 6:17 AM Bruce Momjian <bruce@momjian.us> wrote:
What do we currently know?

*  Caused by CREATE/REINDEX CONCURRENTLY
*  No way to detect which indexes were created concurrently
*  amcheck will be required to find corrupt indexes (options?)
Actually in the initial bug report I posted an SQL that is testing sequential scan VS index scan to find the missing records in the index.
This is how we initially found the problem.
I am not sure how these missing records are related to the `amcheck` problems because the `ctid`s does not match exactly.


--
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson

pgsql-bugs by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: BUG #17485: Records missing from Primary Key index when doing REINDEX INDEX CONCURRENTLY
Next
From: David Rowley
Date:
Subject: Re: BUG #17495: Regression in 15beta1 when filtering subquery including row_number window function