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

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: does this look more like a possible bug or more like a possible hardware problem...? (long)
Date: 2004-03-10 17:33:12
Message-ID: 200403101833.12972.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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';

Got it, made a backup of the entire database as well. Since the db wasn't
filled yet, both files are fairly small when bzipped (<0.5MB and < 5MB) and
both can be made available if you want.

Issuing 'reindex table pg_attribute' did not solve the problem, though....

> > 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 :-(

Nope, all user-tables are in public at the moment.

Also:

megafox_trial=# select * from article_property_tree;
ERROR: catalog is missing 6 attribute(s) for relid 8349771

--
Best,

Frank.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Paolo Tavalazzi 2004-03-10 17:33:41 Re: postgres FROM clause problem
Previous Message scott.marlowe 2004-03-10 17:17:57 Re: updates (postgreSQL) very slow