| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | hkanchu(at)apple(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Any way to understand state after data corruption failures during startup. |
| Date: | 2022-06-17 05:03:43 |
| Message-ID: | 20220617.140343.794518949016832455.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At Thu, 16 Jun 2022 19:46:25 -0700, Harinath Kanchu <hkanchu(at)apple(dot)com> wrote in
>
> Hello,
>
> If postgres fail when it is starting as standby due to WAL file corruption, can we get the status through any exit code or by parsing pg_control file ?
>
> I can see the “XX001” code is emitted in logs but parsing logs doesn’t seem to be a good option. Please suggest.
I'm not sure exactly what is what you want to achieve here, but there
is a negative evidence for the reliability of detecting WAL corruption
failure without searching server logs.
[64923:startup] [XX000] 2022-06-17 13:30:52.493 JST PANIC: incorrect resource manager data checksum in record at 0/3000060
At least in this case, there's no trace of a server-stop due to WAL
corruption left behind other than in server log.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mahendrakar, Prabhakar - Dell Team | 2022-06-17 06:35:39 | Postgresql error : PANIC: could not locate a valid checkpoint record |
| Previous Message | David G. Johnston | 2022-06-17 04:01:03 | Re: ERROR: failed to find conversion function from key_vals_nn to record[] |