Re: [GENERAL] requested timeline doesn't contain minimum recovery point - Mailing list pgsql-general

From Michael Paquier
Subject Re: [GENERAL] requested timeline doesn't contain minimum recovery point
Date
Msg-id CAB7nPqSwBBOHYvu6zmbJ4haDkWen_9OqF2GYHGvCsaDLdgbb8g@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] requested timeline doesn't contain minimum recovery point  (Tom DalPozzo <t.dalpozzo@gmail.com>)
Responses Re: [GENERAL] requested timeline doesn't contain minimum recovery point  (Tom DalPozzo <t.dalpozzo@gmail.com>)
List pgsql-general
On Tue, Jan 10, 2017 at 10:35 PM, Tom DalPozzo <t.dalpozzo@gmail.com> wrote:
> I redid the tests following your suggestion to issue a checkpoint manually.
> IT WORKS!
> Just a question: when the standby server starts, I see the log error
> messages (ex.: "invalid record length...")  when WAL end is reached. I know
> that it's normal.
> But I'm wondering if the system, in order to detect the end of the WAL,
> controls only the validity of the records in the WAL.

You may want to look at xlogreader.c and track report_invalid_record()
to see what are the error checks being done. No full checks are done
depending on the record types, but there are some checks for the
backup blocks, the size record, etc.

> I mean, could random bytes appear as a valid record (very unlikely, but
> possible)?

Yes, that could be possible if some memory or disk is broken. That's
why, while it is important to take backups, it is more important to
make sure that they are able to restore correctly before deploying
them.
--
Michael


pgsql-general by date:

Previous
From: Israel Brewster
Date:
Subject: Re: [GENERAL] Improve PostGIS performance with 62 million rows?
Next
From: Guyren Howe
Date:
Subject: [GENERAL] Are new connection/security features in order, given connectionpooling?