From: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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:08:25 |
Message-ID: | ed307eed-ef62-c33b-3b25-fcea76713417@koumakan.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2021-10-29 21:16:06 | Re: BUG #17258: Unexpected results in CHAR(1) data type |
Previous Message | David G. Johnston | 2021-10-29 21:08:09 | Re: FW: BUG #17258: Unexpected results in CHAR(1) data type |