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-Wzm1uEyGTHfoWfJ1GKFdjiR9XvTt2_zZ1av-BZDR078vzw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17245: Index corruption involving deduplicated entries  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
On Fri, Oct 29, 2021 at 11:52 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Bah, of course.  Sorry for the noise.

It would be nice if users could follow what's going on in the index by
looking at pg_waldump. Theoretically you could compensate for every
individual change to the page (i.e. track the current page offset
number for each tuple dynamically), but that's just too tedious to
ever really work.

It would be nice if pg_waldump printed the contents of index tuples, a
little like pg_filedump can. That would actually offer Kamigishi Rei a
practical way of following what's going on at a low level. It's a pity
that we don't have some kind of generic facility for dumping a random
index tuple, that doesn't require knowledge of the structure of the
index, which isn't easy to get into a tool like pg_waldump. It's
usually possible to see what's in the index without needing to apply
metadata about the "shape" of tuples -- the generic tuple headers show
a lot.

-- 
Peter Geoghegan



pgsql-bugs by date:

Previous
From: Mark Dilger
Date:
Subject: Re: BUG #17258: Unexpected results in CHAR(1) data type
Next
From: Peter Geoghegan
Date:
Subject: Re: BUG #17245: Index corruption involving deduplicated entries