Re: BUG #1208: Invalid page header - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1208: Invalid page header
Date
Msg-id 5781.1092762611@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #1208: Invalid page header  ("Robert E. Bruccoleri" <bruc@stone.congenomics.com>)
Responses Re: BUG #1208: Invalid page header
Re: BUG #1208: Invalid page header
List pgsql-bugs
"Robert E. Bruccoleri" <bruc@stone.congenomics.com> writes:
>     Besides a no optimization compilation of 7.4.3, what else
> would you recommend to explore this problem further? Thanks. --Bob

I really haven't the foggiest where to look :-(  I don't actually
believe that it's a spinlock problem; that would explain pages getting
substituted for other pages, in whole or in part, but you showed at
least one example where a page was just overwritten with garbage.
That looks more like a memory-stomp problem (again, assuming that it's
software) and so could be anywhere.

Are you using any off-the-beaten-track code (contrib modules,
non-btree indexes, non-mainstream data types)?  That stuff is less
well debugged than the mainstream ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Robert E. Bruccoleri"
Date:
Subject: Re: BUG #1208: Invalid page header
Next
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1221: revoke on schema do not return error on failure