Re: 12.3 replicas falling over during WAL redo

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: alvherre(at)2ndquadrant(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: 12.3 replicas falling over during WAL redo
Date: 2020-08-03 14:41:44
Message-ID: 81a54016-2399-3f1c-0abd-05d5522907ff@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kyotaro Horiguchi wrote on 8/2/20 9:39 PM:
> At Sat, 1 Aug 2020 09:58:05 -0700, Ben Chobot <bench(at)silentmedia(dot)com> wrote in
> 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.)
>
> regards.

We have always had full_page_writes enabled.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message alex m 2020-08-03 15:14:35 Re: How to get the name of the current database in C function/extention inside a trigger?
Previous Message John Ashmead 2020-08-03 14:38:42 How can you find out what point logical replication is at?