| From: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | 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 21:46:29 |
| Message-ID: | 125603c4-4403-dcbb-221e-fd1d4ef6ed83@koumakan.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 29.10.2021 0:42, Andres Freund wrote:
>> Unfortunately there's no WAL archiving, and no available WAL files from
>> before the state was known to be corrupt. We'll look into enabling
>> archiving in case the problem recurs or can be reproduced.
>
> Any chance autovacuum logging was enabled and that those logs still exist? Not
> quite as good as still having the WAL, but it still might allow us to
> reconstruct the index / vacuum scans, and the horizons used.
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?
(The daily vacuum runs have not been disabled so there have been at
least 3 since.)
--
K. R.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-10-28 21:47:10 | Re: ERROR: posting list tuple with 20 items cannot be split at offset 168 |
| Previous Message | Andres Freund | 2021-10-28 21:42:09 | Re: BUG #17245: Index corruption involving deduplicated entries |