the WAL file on the master is long gone, how would one inspect the web segment? Any way to have PG "move" on?
On Dec 1, 2011, at 2:02 PM, Jerry Sievers wrote:
> Jim Buttafuoco <jim(at)contacttelecom(dot)com> writes:
>> I have a large PG 9.1.1 server (over 1TB of data) and replica using log shipping. I had some hardware issues on the
>> replica system and now I am getting the following in my pg_log/* files. Same 2 lines over and over since yesterday.
>> 2011-12-01 07:46:30 EST >LOG: restored log file "000000010000028E000000E5" from archive
>> 2011-12-01 07:46:30 EST >LOG: incorrect resource manager data checksum in record at 28E/E555E1B8
>> Anything I can do on the replica or do I have to start over?
> INspect that WAL segment or possibly the one immediatly following it
> in comparison to another copy if you still have it on the master or a
> central WAL repository.
> A standby crashing meanwhile copying in a WAL segment and/or synching
> one to disk could result in ramdon corruption.
> If you have another copy of the segment and does not compare equal to
> the one your standby is trying to read, try another copy.
>> Finally, I know this is not the correct list, I tried general with no answer.
> The admin list is the right one for such a post probably.
>> Jim Buttafuoco
>> 603-647-7170 ext. 2222- Office
>> 603-490-3409 - Cell
>> jimbuttafuoco - Skype
> Jerry Sievers
> Postgres DBA/Development Consulting
> e: postgres(dot)consulting(at)comcast(dot)net
> p: 305.321.1144
603-647-7170 ext. 2222- Office
603-490-3409 - Cell
jimbuttafuoco - Skype
In response to
pgsql-hackers by date
|Next:||From: Andres Freund||Date: 2011-12-01 19:18:41|
|Subject: Re: Command Triggers|
|Previous:||From: Jerry Sievers||Date: 2011-12-01 19:02:42|
|Subject: Re: Postgresql 9.1 replication failing|