| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
| 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-28 22:01:24 |
| Message-ID: | 20211028220124.n4vulzxp6i6fsq4t@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2021-10-29 00:46:29 +0300, Kamigishi Rei wrote:
> The issue manifested again earlier today *after* a REINDEX followed by
> enabling WAL replica logging on the 24th of October. I saved a snapshot of
> the filesystem holding the data directory. Would that be useful for further
> analysis?
Yes, that's *quite* useful. I assume you can't just share that snapshot?
Once we identified an affected heap and index page with the corruption, we
should use pg_waldump to scan for all chanes to that table.
Do you have the log file(s) from between the 24th and now? That might give us
a good starting point for the LSN range to scan.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-10-28 22:23:38 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Andres Freund | 2021-10-28 21:47:10 | Re: ERROR: posting list tuple with 20 items cannot be split at offset 168 |