| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: db corruption/recovery help |
| Date: | 2005-06-07 05:15:52 |
| Message-ID: | 26245.1118121352@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> Someone flipped a breaker switch, and evidently triggered
> corruption in one of our major clusters:
> 2005-06-06 14:31:11.984 [20124] PANIC: Invalid page header in block 22376 of 79189398
It's possible that you are one minor release short of having dodged this
problem, as I see in the 7.3.5 CVS log
2003-12-01 11:53 tgl
* src/backend/storage/buffer/bufmgr.c (REL7_3_STABLE): Force
zero_damaged_pages to be effectively ON during recovery from WAL,
since there is no need to worry about damaged pages when we are
going to overwrite them anyway from the WAL. Per recent
discussion.
This doesn't really address the question of how the page header got
clobbered in the first place, though. Did you by any chance make a dump
to see what data was in there?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2005-06-07 05:25:22 | Re: db corruption/recovery help |
| Previous Message | John A Meinel | 2005-06-07 04:36:53 | Re: Postgresql and Software RAID/LVM |