| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | still getting FATAL errors on btree's... |
| Date: | 1998-04-13 16:00:39 |
| Message-ID: | Pine.NEB.3.95.980413115830.22892L-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Hartwig | 1998-04-13 16:10:58 | Re: [HACKERS] Re: [INTERFACES] New pg_type for large object |
| Previous Message | Boersenspielteam | 1998-04-13 15:32:31 | Re: [HACKERS] subselect and optimizer |