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

From Kamigishi Rei
Subject Re: BUG #17245: Index corruption involving deduplicated entries
Date
Msg-id ed307eed-ef62-c33b-3b25-fcea76713417@koumakan.jp
Whole thread Raw
In response to Re: BUG #17245: Index corruption involving deduplicated entries  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #17245: Index corruption involving deduplicated entries
List pgsql-bugs
On 29.10.2021 23:18, Andres Freund wrote:
> Could you search for btree WAL records before the following records? Most
> importantly for the corrupted page in the corrupted index, but other ones
> might be interesting as well
> 
>> rmgr: Heap2       len (rec/tot):     53/  7937, tx:          0, lsn:
>> 2/90CEF528, prev 2/90CEF4E8, desc: VACUUM nunused 3, blkref #0: rel
>> 1663/19243/19560 blk 540 FPW
>> rmgr: Heap2       len (rec/tot):     53/  8109, tx:          0, lsn:
>> 2/97ED2598, prev 2/97ED2558, desc: VACUUM nunused 1, blkref #0: rel
>> 1663/19243/19560 blk 540 FPW

These are daily vacuum runs (on the 27th and on the 28th) with dozens of 
preceding VACUUM lines for other tables. Should I try to filter out those?

-- 
K. R.



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: FW: BUG #17258: Unexpected results in CHAR(1) data type
Next
From: Mark Dilger
Date:
Subject: Re: BUG #17258: Unexpected results in CHAR(1) data type