[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
Hmm ... so you think the people who have complained of this are all
working with databases that have suffered previous crash corruption?
I doubt it. There's too much consistency to the reports: in
particular, it's generally triggered by creation of lots of large
objects, and it's always the
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
