Horton

Re: BUG #1208: Invalid page header

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: bruc@acm.org
Cc: peter_e@gmx.net, pgman@candle.pha.pa.us, bruc@stone.congenomics.com, pgsql-bugs@postgresql.org, hubert.froehlich@bvv.bayern.de
Date: 2004-08-17T17:10:11Z
Lists: 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