| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Warren Little <Warren(dot)Little(at)MeridiasCapital(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: trying to run PITR recovery |
| Date: | 2007-03-26 00:57:47 |
| Message-ID: | 1625.1174870667@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Warren Little <Warren(dot)Little(at)MeridiasCapital(dot)com> writes:
> I'm testing my PITR recovery procedures and something doesn't look
> right.
> The following is from the logs upon starting postgres with
> recovery.conf file in place
> @ 2007-03-23 05:57:33 MDTLOG: restored log file
> "000000010000011A000000FD" from archive
> @ 2007-03-23 05:57:35 MDTLOG: incorrect resource manager data
> checksum in record at 11A/FD492B20
> @ 2007-03-23 05:57:35 MDTLOG: redo done at 11A/FD492210
> My concern is that there were many more logfiles to be played
> following "00000010000011A000000FD"
> (ie 000000010000011E0000005C) yet it appears the recovery stop at
> that point and called it good.
Perhaps you have a bad copy of that particular log segment file?
The "incorrect checksum" failure is normal in certain circumstances
(eg, where the system crashes partway through writing out a large
WAL record), which is why the code treats it as indicating the end
of WAL. But in this case it looks more like corrupt data ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-26 02:01:20 | Re: no verification of client certificate? |
| Previous Message | Peter Koczan | 2007-03-26 00:27:56 | Re: URGENT TABLE PG_SHADOW CORRUTEP |