invalid resource manager ID in primary checkpoint record - Mailing list pgsql-general

From ascot.moss@gmail.com
Subject invalid resource manager ID in primary checkpoint record
Date
Msg-id 0A3270AA-31DC-4BA7-BC74-11BCAF38F80E@gmail.com
Whole thread Raw
In response to Re: Making substrings uppercase  (David Johnston <polobo@yahoo.com>)
Responses Re: invalid resource manager ID in primary checkpoint record  ("ascot.moss@gmail.com" <ascot.moss@gmail.com>)
fsync and wal_sync_method  ("ascot.moss@gmail.com" <ascot.moss@gmail.com>)
List pgsql-general
Hi,

For special testing reason, I am trying to restore PG from a backup that the basebase is from Standby and WAL files are
fromMaster.  During recovery phase, for every WAL file process, it returned 'invalid resource manager ID in primary
checkpointrecord' and paused, I had to manually run "$PGBIN/pg_resetxlog -f $PG_DATA" many times, is there a way to set
PGto ignore this kind of errors. 

LOG:  database system was shut down at 2013-09-10 03:06:29 :  starting archive recovery
LOG:  restored log file "00000001000000B9000000CA" from archive
LOG:  invalid resource manager ID in primary checkpoint record
LOG:  invalid secondary checkpoint link in control file
PANIC:  could not locate a valid checkpoint record
LOG:  startup process (PID 17969) was terminated by signal 6: Aborted
LOG:  aborting startup due to startup process failure
.
LOG:  restored log file "00000001000000B9000000CB" from archive
LOG:  invalid resource manager ID in primary checkpoint record
LOG:  invalid secondary checkpoint link in control file
PANIC:  could not locate a valid checkpoint record
LOG:  startup process (PID 17981) was terminated by signal 6: Aborted
LOG:  aborting startup due to startup process failure
.
LOG:  restored log file "00000001000000B9000000CC" from archive
.
LOG:  restored log file "00000001000000B9000000CD" from archive


Please advise.
regards






pgsql-general by date:

Previous
From: Quentin Hartman
Date:
Subject: Re: Call for design: PostgreSQL mugs
Next
From: Scott Marlowe
Date:
Subject: Re: Call for design: PostgreSQL mugs