Re: corruption of WAL page header is never reported - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: corruption of WAL page header is never reported
Date
Msg-id aedbb4bb-9349-a980-438b-a7aae6c4be48@oss.nttdata.com
Whole thread Raw
In response to Re: corruption of WAL page header is never reported  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: corruption of WAL page header is never reported
List pgsql-hackers

On 2021/09/13 11:00, Kyotaro Horiguchi wrote:
> The point here is "retry this page, not this record", so "we don't need
> to retry immediately" looks a bit ambiguous. So how about something
> like this?
> 
> Note that we don't do this while not in standby mode because we don't
> need to avoid retrying this entire record even if the page header is
> not valid. Instead, ReadPageInternal() is responsible for validating
> the page header in that case.

You mean that, while not in standby mode, we need to retry reading
the entire record if the page head is invalid? I was thinking that
we basically give up replaying further records in that case becase
we're not in standby mode.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PG Docs - CREATE SUBSCRIPTION option list order
Next
From: Corey Huinker
Date:
Subject: Re: SQL:2011 application time