[EMAIL PROTECTED] (J.H.M. Dassen (Ray)) writes:
> Bengt Månsson <[EMAIL PROTECTED]> wrote:
>> Warning: PostgreSQL query failed: FATAL 1: my bits moved right off the end
>> of the world! Recreate index pg_attribute_relid_attnum_index.
This is an internal "can't happen" failure condition, presumably arising
from some weird corner-case bug in btree index manipulation. We have seen
sporadic reports of this failure, mostly from people using lots of large
objects, but no one has yet provided a test case that allows the problem
to be reproduced from scratch. When I'm in an optimistic mood I think
that the bug might be fixed in 7.1, but it's hard to say for sure
because I've never seen this failure happen myself.
> Follow the suggestion given in the warning: recreate index
> pg_attribute_relid_attnum_index, presumably [*] using something like
> DROP INDEX pg_attribute_relid_attnum_index;
> CREATE UNIQUE INDEX pg_attribute_relid_attnum_index ON
> pg_attribute(attrelid,attnum);
I think that will probably crash and burn :-(. To reconstruct a broken
system index you need to use the REINDEX command. See the manual for
the proper procedure for using REINDEX on system indexes; it's a tad
arcane.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
