Re: unexpected pageaddr in the log of a standby server

On 08/27/2012 05:17 AM, Viacheslav N Tararin wrote:
> Good day.
> I have got next log file after restart a standby server. The master
> server all of the time was up and properly works.
> It the message "unexpected pageaddr" and non exists log files indicates
> about standby databases corrupted.
>
> LOG: database system was interrupted while in recovery at log time
> 2012-08-27 14:50:29 EEST
> HINT: If this has occurred more than once some data might be corrupted
> and you might need to choose an earlier recovery target.
> LOG: entering standby mode
> FATAL: the database system is starting up
> LOG: restored log file "00000001000002440000000B" from archive
> LOG: redo starts at 244/B45A210
> LOG: consistent recovery state reached at 244/BEF2B20
> LOG: database system is ready to accept read only connections
> LOG: restored log file "00000001000002440000000C" from archive
> LOG: restored log file "00000001000002440000000D" from archive
> LOG: restored log file "00000001000002440000000E" from archive
> scp: /var/lib/postgresql/archive/00000001000002440000000F: No such file
> or directory
> LOG: unexpected pageaddr 244/3000000 in log file 580, segment 15, offset 0
> scp: /var/lib/postgresql/archive/00000001000002440000000F: No such file
> or directory
> LOG: streaming replication successfully connected to primary
>

See here for explanation:
http://archives.postgresql.org/pgsql-admin/2011-02/msg00003.php

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com