> > What I don't grok is why all the affected files were indexes, and none
> > of the heap files appeared to have junk pages
>
> Hmmm ... that is mildly interesting, but it doesn't rise to the level of
> warning bells in my head.
I played around a bit yesterday with an INSERT'ing shell script and
Guy Thornley <[EMAIL PROTECTED]> writes:
>> That's what I'd expect if this scenario applies:
>> the pages will be fixed by WAL recovery, it's just that the recently
>> added check for broken page headers was interfering :-(
> What I don't grok is why all the affected files were indexes, and none
>
> > PANIC: invalid page header in block 6 of relation "17792"
> > This was on postgres 7.4.
>
> I believe this is fixed in 7.4.1:
...
> And no sign of corruption after you'd run through the recovery with
> zero_damaged_pages?
I checked them this morning; there isnt.
Sorry for bugging you abou
Guy Thornley <[EMAIL PROTECTED]> writes:
> On one of our test boxen here, weve experienced a corrupted file during
> database recovery after box power outage. The specific error message is
> PANIC: invalid page header in block 6 of relation "17792"
> This was on postgres 7.4.
I believe this
Hi,
On one of our test boxen here, weve experienced a corrupted file during
database recovery after box power outage. The specific error message is
PANIC: invalid page header in block 6 of relation "17792"
At this point I fired up a hex dumper to inspect the file, and the last
block in t
