On Wed, Jan 27, 2010 at 2:19 AM, Erik Rijkers <er@xs4all.nl> wrote:
> Now, when restoring a 700MB dump (made with a 9.0devel pg_dump + pg_restore) into the primary,
> errors like the following occur, on all three instances:
>
> FATAL: could not open file "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such
> file or directory
Thanks for the report!
This is the bug of SR :( I think that walsender wrongly treats the WAL-boundary.
> pgsql.sr_slave02/logfile:ERROR: could not read xlog records: FATAL: could not open file
> "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or directory
> pgsql.sr_slavery/logfile:ERROR: could not read xlog records: FATAL: could not open file
> "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or directory
Also the ReadRecord() or its surrounding functions seem to have treated
wrongly the WAL-boundary.
I'll fix those bugs after a night's sleep.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center