Behavior for crash recovery when it detects a corrupt WAL record - Mailing list pgsql-hackers

From Amit Kapila
Subject Behavior for crash recovery when it detects a corrupt WAL record
Date
Msg-id 00b201cda623$e8528240$b8f786c0$@kapila@huawei.com
Whole thread Raw
Responses Re: Behavior for crash recovery when it detects a corrupt WAL record  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif"">I have
observedthat currently during recovery, while it applies the WAL records even if it detects that there is a corrupt
record</span><pclass="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif"">by crc validation, it
proceeds.</span><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif"">Basically
ReadRecord(),returns NULL in such cases which makes the behavior same as it has reached end of WAL.</span><p
class="MsoNormal"><spanstyle="font-size:12.0pt;font-family:"Arial","sans-serif"">After that server get started and user
canperform operations normally. </span><p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Arial","sans-serif"">HoweverITSM that this is a problem as user might loose some
committeddata.</span><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif""> </span><p
class="MsoNormal"><spanstyle="font-size:12.0pt;font-family:"Arial","sans-serif"">Is there any particular reason for
thisbehavior?</span><p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Arial","sans-serif""> </span><p
class="MsoNormal"><spanstyle="font-size:12.0pt;font-family:"Arial","sans-serif"">With Regards,</span><p
class="MsoNormal"><spanstyle="font-size:12.0pt;font-family:"Arial","sans-serif"">Amit Kapila.</span></div> 

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown
Next
From: Tom Lane
Date:
Subject: Re: Truncate if exists