| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 12.3 replicas falling over during WAL redo |
| Date: | 2020-08-03 19:55:34 |
| Message-ID: | f0990521-9839-5317-a91a-66bd919f5202@silentmedia.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shankar Bhaskaran | 2020-08-03 20:01:42 | Configuring only SSL in postgres docker image |
| Previous Message | Alvaro Herrera | 2020-08-03 19:34:04 | Re: 12.3 replicas falling over during WAL redo |