Horton

still getting FATAL errors on btree's...

Marc G. Fournier <scrappy@hub.org>

View thread View on postgr.es
From: The Hermit Hacker <scrappy@hub.org>
To: pgsql-hackers@postgresql.org
Date: 1998-04-13T16:00:39Z
Lists: pgsql-hackers 
I'm still getting the following BTP_CHAIN errors on my btree index.  Funny
thing is that its the *same* index each time, and this is after dropping
and rebulding it...

...where next to investigate?  Recommendations?  IMHO, this is critical
enough to hold off a v6.3.2 release :(


FATAL 1:  btree: BTP_CHAIN flag was expected in radhist_userid (access =
bt_read)
FATAL 1:  btree: BTP_CHAIN flag was expected in radhist_userid (access =
bt_read)
FATAL 1:  btree: BTP_CHAIN flag was expected in radhist_userid (access =
bt_read)
FATAL 1:  btree: BTP_CHAIN flag was expected in radhist_userid (access =
bt_read)
FATAL 1:  btree: BTP_CHAIN flag was expected in radhist_userid (access =
bt_read)