| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | bench(at)silentmedia(dot)com, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 12.3 replicas falling over during WAL redo |
| Date: | 2020-08-03 18:25:08 |
| Message-ID: | CAH2-WzkoAWLFM_vinLFOFWHS6J5wWALm02zaSJniVzEVRbux6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Aug 2, 2020 at 9:39 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> All of the cited log lines seem suggesting relation with deleted btree
> page items. As a possibility I can guess, that can happen if the pages
> were flushed out during a vacuum after the last checkpoint and
> full-page-writes didn't restored the page to the state before the
> index-item deletion happened(that is, if full_page_writes were set to
> off.). (If it found to be the cause, I'm not sure why that didn't
> happen on 9.5.)
There is also a Heap/HOT_UPDATE log line with similar errors.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Chobot | 2020-08-03 19:11:05 | Re: 12.3 replicas falling over during WAL redo |
| Previous Message | Michael Lewis | 2020-08-03 18:14:20 | Re: How to rebuild index efficiently |