Hi, I'm using PostgreSQL 9.3.2 with WAL-E 0.6.6.
I'm experimenting with WAL-E PITR recovery. I was successful with a few small databases, and now I'm trying a production-size database (about 76GB). Base backup and subsequent log archival go well. I'm also able to restore the base backup onto a slave. When I then place a recovery.conf in the slave's cluster data directory and start the server, it starts fetching WAL from the archive using WAL-E but then terminates with a message like this: 2014-01-29 13:51:39 GMT::@:[29748] LOG: restored log file "000000010000003600000060" from archive 2014-01-29 13:51:39 GMT::@:[29748] FATAL: could not access status of transaction 0 2014-01-29 13:51:39 GMT::@:[29748] DETAIL: Could not open file "pg_subtrans/0083": No such file or directory. 2014-01-29 13:51:39 GMT::@:[29748] CONTEXT: xlog redo insert: rel 1663/223023/225552; tid 2895/4 2014-01-29 13:51:39 GMT::@:[29747] LOG: startup process (PID 29748) exited with exit code 1 2014-01-29 13:51:39 GMT::@:[29747] LOG: terminating any other active server processes 2014-01-29 13:52:00 GMT::@:[29987] LOG: database system was interrupted while in recovery at log time 2014-01-29 04:00:01 GMT 2014-01-29 13:52:00 GMT::@:[29987] HINT: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target. Googling seems to suggest a data corruption issue (as does the error message of course!). I'm taking a fresh base backup now to see if it's a one-off problem, but I was interested to see if anyone else has seen this. Cheers, Dan -- Dan Fairs | [email protected] | @danfairs | secondsync.com -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
