Re: BUG #17245: Index corruption involving deduplicated entries

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp>, David Rowley <dgrowley(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Date: 2021-10-28 21:36:12
Message-ID: 20211028213612.vv2q4rcd5lcosubv@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2021-10-28 14:18:32 -0700, Peter Geoghegan wrote:
> Note that the other people that had similar complaints about Postgres 14 all
> used foreign keys on affected tables.

Do you have links to the other reports?

> * The transaction ID 365637 is very over-represented, appearing in
> several corrupt heap tuple headers, located across several heap pages.
>
> * Its "neighbor" transaction ID is 365638, which appears once more. To
> me this suggests some kind of confusion with an OldestXmin style
> cutoff during VACUUM.

I'm not quite following this bit, could you expand on that?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2021-10-28 21:39:37 Re: BUG #17245: Index corruption involving deduplicated entries
Previous Message Andres Freund 2021-10-28 21:31:03 Re: BUG #17245: Index corruption involving deduplicated entries