Re: BUG #17245: Index corruption involving deduplicated entries
От | Kamigishi Rei |
---|---|
Тема | Re: BUG #17245: Index corruption involving deduplicated entries |
Дата | |
Msg-id | ed307eed-ef62-c33b-3b25-fcea76713417@koumakan.jp обсуждение исходный текст |
Ответ на | Re: BUG #17245: Index corruption involving deduplicated entries (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: BUG #17245: Index corruption involving deduplicated entries
|
Список | 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 по дате отправления: