pg_standby could not open wal file after selecting new timeline

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_standby could not open wal file after selecting new timeline
Date: 2008-11-05 16:58:51
Message-ID: 28E6231D-FBE2-491C-9D41-39E3466DFFFC@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I am trying to move a db from one machine to another.

pg_standby applies all the logs fine, then I trigger it and this
happens ???

2008-11-05 11:43:45 EST [14853] LOG: restored log file
"00000003000016ED0000007E" from archive
2008-11-05 11:43:45 EST [14853] LOG: selected new timeline ID: 4
2008-11-05 11:43:45 EST [14853] LOG: archive recovery complete
2008-11-05 11:43:48 EST [14853] FATAL: could not open file "pg_xlog/
00000004000016ED0000007F" (log file 5869, segment 127): Invalid argument
2008-11-05 11:43:48 EST [14846] LOG: startup process (PID 14853)
exited with exit code 1

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-11-05 17:04:04 Re: Tests citext casts
Previous Message Tom Lane 2008-11-05 16:40:04 Re: some strange bugs related to upgrade from 8.1 to 8.3