Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id C61052E0063 for ; Thu, 17 Apr 2008 07:44:29 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 32358-09 for ; Thu, 17 Apr 2008 07:44:26 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by developer.postgresql.org (Postfix) with ESMTP id 387322E007C for ; Thu, 17 Apr 2008 07:44:26 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so26330wag.5 for ; Thu, 17 Apr 2008 03:44:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=QNyPxbUYFTzPbkKNdN31RL1tjmDt1cYAeT1lDEShENY=; b=hRZOUiP0YvbNwOs051HaZLzo+k3aFLXNJHgJm/9qbZud6RpPVpU8ErJI3kIQD/7fIWBFmdiRC1UUbfbcuEjB4++Dn0KkBo0xCKm+SJCu/yK7yiPwN3wAIgJyaAR2WZWepKgFhRYt2NXSCfKbmDpM+sDbjT8vuH4QYNE51AnZaQA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hQisNeT+UNp3NiBWSfyXp9Y5cYuYznJhhcIzdjXJz4qFFZ0pmkDugqQJIPL8V1bg0l9eUJbTf9ZcBMGF3lrJwVOJgvMcRHTC/sASAuiyZwd7cbMZ/59Ody1vjcDz39UTia6itUIVe5K6TByz8Az1XWmGehdc+/bxNBaMYqXU0qU= Received: by 10.114.106.1 with SMTP id e1mr1217082wac.95.1208429062248; Thu, 17 Apr 2008 03:44:22 -0700 (PDT) Received: by 10.114.102.14 with HTTP; Thu, 17 Apr 2008 03:44:22 -0700 (PDT) Message-ID: <2ca799770804170344o65291ce3pa56a2694f7a15bc5@mail.gmail.com> Date: Thu, 17 Apr 2008 13:44:22 +0300 From: "Mikko Partio" To: "Pavan Deolasee" Subject: Re: FATAL: could not open relation xxx: No such file or directory Cc: pgsql-admin@postgresql.org In-Reply-To: <2e78013d0804170336j4299161bm3f280fc9b930b474@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_3581_11206518.1208429062241" References: <2ca799770804090647m759b72f9gf2d49b4bf7cc8bdf@mail.gmail.com> <2ca799770804142336q6422af38me80054c82699d1e2@mail.gmail.com> <2ca799770804170308m367eaea2nc7899198c0b260e0@mail.gmail.com> <2e78013d0804170336j4299161bm3f280fc9b930b474@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/170 X-Sequence-Number: 28934 ------=_Part_3581_11206518.1208429062241 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Apr 17, 2008 at 1:36 PM, Pavan Deolasee wrote: > On Thu, Apr 17, 2008 at 3:38 PM, Mikko Partio wrote: > > > > > 2008-04-17 13:05:30 EEST [8435]: [32-1] ERROR: could not open relation > > 1663/16386/359232: No such file or directory > > > > Looks like a corrupt index to me. DId you try REINDEX on the table ? > Hi Pavan and thanks for your reply. I tried to reindex the individual indexes in the table: # reindex index xxx_idx; ERROR: could not open relation 1663/16386/359232: No such file or directory Since I thought the trouble may lie in the system catalogue indexes I issued a REINDEX SYSTEM db, which went through with no errors. After that I tried to remove indexes from the table in question: # drop index xxx_idx; ERROR: could not read block 0 of relation 1663/16386/2673: read only 0 of 8192 bytes Hmm.. this is a different oid # select 2673::regclass; regclass -------------------------- pg_depend_depender_index (1 row) But I just reindexed it! # reindex table pg_depend; WARNING: could not remove relation 1663/16386/2673: No such file or directory REINDEX When I fire pg_dump to take a last minute backup I see this error: pg_dump: Error message from server: ERROR: could not open relation 1663/16386/544529: No such file or directory pg_dump: The command was: SELECT tgname, tgfoid::pg_catalog.regproc as tgfname, tgtype, tgnargs, tgargs, tgenabled, tgisconstraint, tgconstrname, tgdeferrable, tgconstrrelid, tginitdeferred, tableoid, oid, tgconstrrelid::pg_catalog.regclass as tgconstrrelname from pg_catalog.pg_trigger t where tgrelid = '294134'::pg_catalog.oid and tgconstraint = 0 # reindex table pg_catalog.pg_trigger; WARNING: could not remove relation 1663/16386/544529: No such file or directory REINDEX Seems like the whole db is falling apart. Regards Mikko ------=_Part_3581_11206518.1208429062241 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Thu, Apr 17, 2008 at 1:36 PM, Pavan Deolasee <pavan.deolasee@gmail.com> wrote:
On Thu, Apr 17, 2008 at 3:38 PM, Mikko Partio <mpartio@gmail.com> wrote:

>
> 2008-04-17 13:05:30 EEST [8435]: [32-1] ERROR:  could not open relation
> 1663/16386/359232: No such file or directory
>

Looks like a corrupt index to me. DId you try REINDEX on the table ?


Hi Pavan and thanks for your reply.

I tried to reindex the individual indexes in the table:

# reindex index xxx_idx;
ERROR:  could not open relation 1663/16386/359232: No such file or directory

Since I thought the trouble may lie in the system catalogue indexes I issued a REINDEX SYSTEM db, which went through with no errors. After that I tried to remove indexes from the table in question:

# drop index xxx_idx;
ERROR:  could not read block 0 of relation 1663/16386/2673: read only 0 of 8192 bytes

Hmm.. this is a different oid

# select 2673::regclass;
         regclass
--------------------------
 pg_depend_depender_index
(1 row)

But I just reindexed it!

# reindex table pg_depend;
WARNING:  could not remove relation 1663/16386/2673: No such file or directory
REINDEX

When I fire pg_dump to take a last minute backup I see this error:

pg_dump: Error message from server: ERROR:  could not open relation 1663/16386/544529: No such file or directory
pg_dump: The command was: SELECT tgname, tgfoid::pg_catalog.regproc as tgfname, tgtype, tgnargs, tgargs, tgenabled, tgisconstraint, tgconstrname, tgdeferrable, tgconstrrelid, tginitdeferred, tableoid, oid, tgconstrrelid::pg_catalog.regclass as tgconstrrelname from pg_catalog.pg_trigger t where tgrelid = '294134'::pg_catalog.oid and tgconstraint = 0

# reindex table pg_catalog.pg_trigger;
WARNING:  could not remove relation 1663/16386/544529: No such file or directory
REINDEX

Seems like the whole db is falling apart.

Regards

Mikko
------=_Part_3581_11206518.1208429062241--