Skip site navigation (1) Skip section navigation (2)

Re: FATAL: could not open relation xxx: No such file or directory

From: "Mikko Partio" <mpartio(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: FATAL: could not open relation xxx: No such file or directory
Date: 2008-04-15 06:36:33
Message-ID: 2ca799770804142336q6422af38me80054c82699d1e2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Wed, Apr 9, 2008 at 4:47 PM, Mikko Partio <mpartio(at)gmail(dot)com> wrote:

> Hello all
>
> my struggle with the database continues (see earlier thread titled "too
> many trigger records found for relation xyz").
>
> Today, I created yet another to table to the same database. Everything
> went ok, no errors or anything, but when I checked pg_tables -view I saw two
> tables with the same name. Instantly I queried pg_class and yes there was
> again two tables with same oid. I dropped the table before anything more
> serious could happen, but then postgres started to complain of "cache lookup
> failed for relation ...". I disconnected my psql session and tried to
> reconnect but failed to do so:
>
> 2008-04-09 16:39:25 EEST [18984]: [1-1] FATAL:  could not open relation
> 1663/16386/544592: No such file or directory
>
> Indeed, there is no such file in that directory. I'm guessing that file is
> connected to the table I just dropped. Now, is there anything to do to get
> the database back online? I can still connect to other databases in the same
> instance


The cure was to create file 1663/16386/54459 8K in size with dd. The file in
question was in fact the oid index on pg_class -- I had issued a REINDEX on
pg_class just a moment before and apparantly something went wrong and the
system lost track of the index. There was also two entries in pg_index for
index pg_class_oid_index. After I removed the other entry and reindexed
pg_class and pg_index, everything seems to be working ok. All the symptoms
indicate that perhaps a xid wraparound had happened, but there is no such
warning in logs and age(datfrozenxid) went never higher than say
250,000,000. Does anybody have a clue what might have happened?

Regards

Mikko

In response to

Responses

pgsql-admin by date

Next:From: lfeddenDate: 2008-04-15 09:00:26
Subject: OID and filesystem issues
Previous:From: Michael MonnerieDate: 2008-04-15 06:26:31
Subject: Re: duplicate primary index in bayes db from SpamAssassin

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group