Re: Postgres: PANIC: WAL contains references to invalid pages - Mailing list pgsql-bugs

From Andres Freund
Subject Re: Postgres: PANIC: WAL contains references to invalid pages
Date
Msg-id 20131110224956.GE32665@awork2.anarazel.de
Whole thread Raw
In response to Postgres: PANIC: WAL contains references to invalid pages  (Henley Wing <henley.chiu@gmail.com>)
List pgsql-bugs
Hello,

On 2013-11-10 17:43:50 -0500, Henley Wing wrote:
> I have a slave database that is being replicated from a Master DB (through
> rsync).
>
> All of a sudden, my slave DB just exited and wasn't able to restart. Here
> are the error messages when it exits. Similar ones appear when I restart:
>
> WARNING:  page 21561636 of relation base/16384/54391 is uninitialized
> CONTEXT:  xlog redo visible: rel 1663/16384/54391; blk 21561636
> PANIC:  WAL contains references to invalid pages
> CONTEXT:  xlog redo visible: rel 1663/16384/54391; blk 21561636
> LOG:  startup process (PID 1573) was terminated by signal 6: Aborted
> LOG:  terminating any other active server processes
>
> Both slave and master are using *Postgres 9.2.3* in a *Centos 5* quad-core
> server with 32 GB of RAM each.

> When I try to restart the slave, with "zero_damaged_pages=true", the server
> still refuses to start with lines like the ones above. The master is still
> running and isn't corrupt at all.

You unfortunately have to reclone the standby :(

> At this point, I don't care if the slave ever starts as I can start from
> scratch. But is this an issue with Postgres? Has anyone encountered this
> and is it fixed in future versions?

This hopefully is fixed in 17fa4c321ccf9693de406faffe6b235e949aa25f -
9.2.5.
For some reason it's not contained in the release notes, sorry for that.

Greetings,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-bugs by date:

Previous
From: Henley Wing
Date:
Subject: Postgres: PANIC: WAL contains references to invalid pages
Next
From: Tom Lane
Date:
Subject: Re: BUG #8532: postgres fails to start with timezone-data >=2013e