Re: corruption of WAL page header is never reported

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: alvherre(at)alvh(dot)no-ip(dot)org, nagata(at)sraoss(dot)co(dot)jp, ranier(dot)vf(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: corruption of WAL page header is never reported
Date: 2021-09-13 05:56:11
Message-ID: aedbb4bb-9349-a980-438b-a7aae6c4be48@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2021-09-13 06:05:41 Re: SQL:2011 application time
Previous Message Amit Kapila 2021-09-13 05:34:58 Re: PG Docs - CREATE SUBSCRIPTION option list order