Re: BUG #13822: Slave terminated - WAL contains references to invalid page

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Marek(dot)Petr(at)tieto(dot)com
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13822: Slave terminated - WAL contains references to invalid page
Date: 2016-01-05 07:52:49
Message-ID: CAB7nPqR9htMoqe7dvQzg7+DXARFTVNSJ+HvY+CEdyUxSeaXVFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Dec 31, 2015 at 5:20 AM, <Marek(dot)Petr(at)tieto(dot)com> wrote:
> To be honest I don't understand why this second PITR finished without PANIC when previous attempt from the same base backup and archived wals failed.

I have no clue here either as the first PITR failed while the second
completed correctly, replaying the same content. It seems that this
relation block got corrupted in some way because of an issue with
memory and/or disk, or presumably in the WAL segment itself. I would
discard the possibility of a bug in the WAL replay based on this
evidence... Is there actually something different in the way you ran
the replay in both cases? Like on different servers?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Christoph Berg 2016-01-05 09:41:16 Re: BUG #13842: deb-Package configuration hangs at password promt
Previous Message Tom Lane 2016-01-05 04:20:55 Re: BUG #13843: Problem with output of an index definition by "pg_restore"