Re: BUG #17245: Index corruption involving deduplicated entries - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #17245: Index corruption involving deduplicated entries
Date
Msg-id CAH2-WznGy=DYLWqRZP5eGBn+9JkNeNx3Xg9G==ZXs+OakTqdfQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17245: Index corruption involving deduplicated entries  (Pavel Borisov <pashkin.elfe@gmail.com>)
Responses Re: BUG #17245: Index corruption involving deduplicated entries  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
On Thu, Oct 28, 2021 at 2:40 PM Pavel Borisov <pashkin.elfe@gmail.com> wrote:
> One hypothesis just out-of-the air:
> If heap page visibility map bit is wrongly set to all_visible, index-only scan can give duplicates (in effect new and
oldversions of the same row), with no apparent corruption of neither index nor heap relation.
 

That can't be it, because affected physical index pages directly
contain duplicate heap TIDs (and plenty of them). That's never allowed
to happen, no matter what.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Next
From: Thomas Munro
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries