Re: 12.3 replicas falling over during WAL redo - Mailing list pgsql-general

From Ben Chobot
Subject Re: 12.3 replicas falling over during WAL redo
Date
Msg-id f0990521-9839-5317-a91a-66bd919f5202@silentmedia.com
Whole thread Raw
In response to Re: 12.3 replicas falling over during WAL redo  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: 12.3 replicas falling over during WAL redo
List pgsql-general
Alvaro Herrera wrote on 8/3/20 12:34 PM:
> On 2020-Aug-03, Ben Chobot wrote:
>
> Yep. Looking at the ones in block 6501,
>
>> rmgr: Btree       len (rec/tot):     72/    72, tx:   76393394, lsn:
>> A0A/AB2C43D0, prev A0A/AB2C4378, desc: INSERT_LEAF off 41, blkref #0: rel
>> 16605/16613/60529051 blk 6501
>> rmgr: Btree       len (rec/tot):     72/    72, tx:   76396065, lsn:
>> A0A/AC4204A0, prev A0A/AC420450, desc: INSERT_LEAF off 48, blkref #0: rel
>> 16605/16613/60529051 blk 6501
> My question was whether the block has received the update that added the
> item in offset 41; that is, is the LSN in the crashed copy of the page
> equal to A0A/AB2C43D0?  If it's an older value, then the write above was
> lost for some reason.

How do I tell?



pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: 12.3 replicas falling over during WAL redo
Next
From: Shankar Bhaskaran
Date:
Subject: Configuring only SSL in postgres docker image