Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a slave database that is being replicated from a Master DB.

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.

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?

Looking up research online doesn't give me much confidence, so that's why I'm posting here.

share|improve this question
You might want to also try posting this question to the Postgresql mailing lists, where most of the core developers regularly answer questions. I suggest the pgsql-general list. See for directions on how to sign up (if you haven't already). – bma Nov 10 '13 at 22:37
Or for a (potentially) more immediate response, you could try the folks in the #postgresql IRC channel: – bma Nov 10 '13 at 22:44
I see Andres Freund has delivered an answer . FWIW, it appears to be related to an earlier thread that mentions the commit where the bug was patched: – bma Nov 10 '13 at 22:53
I just experienced this in 9.2.6 on ubuntu 12.04.4 - is there a known solution for this besides "restart the replica"? – Geesu Jan 26 '14 at 4:39
@Geesu A question first: Is your slave database in the same network as the master? Same data center? – Henley Chiu Jan 26 '14 at 18:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.