Frank van Vugt <[EMAIL PROTECTED]> writes:
>> This is consistent with the idea that pg_attribute_relid_attnum_index is
>> corrupted. I would suggest saving a copy of that file for postmortem
>> analysis and then trying to REINDEX pg_attribute.
> Uhm...... looking for a file named 8349771 located in the directory base/<nr>
> where nr corresponds to the proper db, using oid2name.....
> We seem to have a small problem : there is no such file.....
I'm sorry, I meant to say save a copy of
pg_attribute_relid_attnum_index. The correct filename for it can be
found via
select relfilenode from pg_class where relname = 'pg_attribute_relid_attnum_index';
> Oid of table article_property_tree from database "megafox_trial":
> ---------------------------------
> VERY scary: more than one table with that name found!!
Do you have more than one such table (presumably in different schemas)?
If so this isn't scary at all. I don't believe oid2name has been fixed
to be schema-aware :-(
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
