| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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 01:50:04 |
| Message-ID: | CAH2-Wz=69Eoh8hWV6K-BzsrVnEzD61Jkaw=MGM_ecS3F4vWRLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Oct 28, 2021 at 2:46 PM Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp> 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?
Access to the WAL archive would be great. Now might be a good time to
set "log_min_autovacuum_duration=0" in postgresql.conf -- that
information might be very helpful later on. This will appear in the
system logs for PostgreSQL. We'll be particularly interested in the
"page" table, for the obvious reason.
Also, can you please post output of the following on your server:
"select * from pg_settings where setting != boot_val;"
Thanks
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-10-29 02:35:59 | Re: BUG #17245: Index corruption involving deduplicated entries |
| Previous Message | Peter Geoghegan | 2021-10-29 01:43:54 | Re: BUG #17245: Index corruption involving deduplicated entries |