Re: requested timeline doesn't contain minimum recovery point

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: requested timeline doesn't contain minimum recovery point
Date: 2017-01-11 00:06:31
Message-ID: CAB7nPqSwBBOHYvu6zmbJ4haDkWen_9OqF2GYHGvCsaDLdgbb8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jan 10, 2017 at 10:35 PM, Tom DalPozzo <t(dot)dalpozzo(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2017-01-11 07:32:02 Are new connection/security features in order, given connection pooling?
Previous Message Israel Brewster 2017-01-10 23:12:59 Re: Improve PostGIS performance with 62 million rows?