Re: BUG #17245: Index corruption involving deduplicated entries

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: BUG #17245: Index corruption involving deduplicated entries
Date: 2021-10-29 21:47:32
Message-ID: CAH2-WzkhmPA-S3ODoCNkU0r3aAdiXOPnghfPEcD_LwdXgbCOFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Oct 29, 2021 at 1:59 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I'm considering writing a patch that
> 1) displays the number of tuples marked unused in HEAP2_PRUNE. This might only
> be possible if no FPW was used
> 2) if a HEAP2_PRUNE or HEAP2_VACUUM isn't an FPW, display the offsets

> For 15 I think it might be worth to explicitly store the number of offets
> marked unused, rather than inferring that. It's hard to believe that the 16
> bit for that would be a relevant overhead, and having that more readily
> available seems like a significant improvement in debuggability.

I like that idea.

Attached is output from pg_filedump for heap page 540, with the page
header LSN reading 2/A019DC60. I have output, with and without the -i
option.

This doesn't have any of the real user data, which won't matter to you.

--
Peter Geoghegan

Attachment Content-Type Size
pg_filedump.waldump.mediawiki.page.block540.page application/octet-stream 18.3 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David M. Calascibetta 2021-10-29 21:52:46 RE: BUG #17258: Unexpected results in CHAR(1) data type
Previous Message Mark Dilger 2021-10-29 21:36:08 Re: BUG #17258: Unexpected results in CHAR(1) data type