Re: does this look more like a possible bug or more like a possible hardware problem...? (long)

Hi,

> > ERROR: catalog is missing 6 attribute(s) for relid 8349771

> 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'll hold reindexing in case you first want to look elsewhere.

> If REINDEX makes the problem go away, would you send me the corrupted
> index file off-list?

I happily would, but you already know its content ;-)

Here's a log of what I did:

base/7847604# ls 82*
8240054 8240056 8240058 8240059 8240600 8240602 8261384 8261386
8261388 8261398

base/7847604# ls 83*
8351687 8352194 8352623 8352754 8353080 8353478 8353581 8353741
<cut>

The last few existing entries from the 82* range seem to be regular
user-tables and corresponding indexes, likewise for the first few in the 83*
range

But when I try the particular oid:

# /usr/local/pgsql/bin/oid2name -d megafox_trial -U ... -P ... -o 8349771
Tablename of oid 8349771 from database "megafox_trial":
---------------------------------
8349771 = article_property_tree

and its revers:

# /usr/local/pgsql/bin/oid2name -d megafox_trial -U ... -P ...
-t article_property_tree
Oid of table article_property_tree from database "megafox_trial":
---------------------------------
VERY scary: more than one table with that name found!!

--
Best,

Frank.