Skip site navigation (1) Skip section navigation (2)

Re: WAL recovery, stop and resume recovery?

From: David Wall <d(dot)wall(at)computer(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: WAL recovery, stop and resume recovery?
Date: 2008-01-11 20:28:17
Message-ID: 4787D161.9000000@computer.org (view raw or flat)
Thread:
Lists: pgsql-admin
> LOG:  database system was shut down at 2008-01-11 11:40:05 PST
> LOG:  starting archive recovery
> LOG:  restore_command = "~/postgresql/bin/pg_standby -l -d -s 2 -k 20 
> -t ~/postgresql/restoreWALs/STOP_RESTORE ~/postgresql/restoreWALs %f 
> %p 2>> ~/pg_standby.log"
> *LOG:  restored log file "00000001000000050000001D" from archive
> LOG:  invalid record length at 5/1D000068
> LOG:  invalid primary checkpoint record
> LOG:  restored log file "00000001000000050000001D" from archive
> LOG:  invalid resource manager ID in secondary checkpoint record
> PANIC:  could not locate a valid checkpoint record*
> LOG:  startup process (PID 9219) was terminated by signal 6
> LOG:  aborting startup due to startup process failure
> LOG:  logger shutting down

One more thing is that the error above about the 1D log file above 
having an invalid record length, etc. is interesting in that if I 
restore from the TAR backup created for this and start the backup 
database in recover mode, it manages to process the 1D log file just 
fine (along with all the previous log files of course).

David

pgsql-admin by date

Next:From: Tom LaneDate: 2008-01-11 20:33:51
Subject: Re: WAL recovery, stop and resume recovery?
Previous:From: Larry RosenmanDate: 2008-01-11 18:13:33
Subject: Re: PostgreSQL on 64-bit Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group