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

On 2022-May-31, Alvaro Herrera wrote:

> At this point, I'm clear that d9d076222f5b needs to be reverted because
> of the interactions with HOT prune, but it's not at all clear to me what
> is the relationship of the other two commits to bugs.  I am going to
> revert that one now, so that we can continue to diagnose any lingering
> problem that may be related to the other two commits -- but perhaps it
> is something else.

Reverted.  (This is the same commit that Michaël found to blame at the
start of the thread.)

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/