Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4FDC92E005B for ; Wed, 9 Apr 2008 10:47:37 -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 85724-05 for ; Wed, 9 Apr 2008 10:47:29 -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.182]) by developer.postgresql.org (Postfix) with ESMTP id B78932E0047 for ; Wed, 9 Apr 2008 10:47:30 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id m38so2530788waf.5 for ; Wed, 09 Apr 2008 06:47:29 -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:mime-version:content-type; bh=j6mi7NYHDJFHy5ZUEZj4oOEsriQok6IA9vOaNwA5IIY=; b=VZ+AQytt4FWsHJLf/zVUlg5Nogl/WtLR1lJ9FamT1lN9Nviyy/sRl6NO1febqCCU+FXwsnm4GUyAOqgLC1kae1wFbSHhDKeigdDmhXtFpc/ZPZiM7MeodOIfmBQXR6oV8aGyuVETxrZ/5tKbkVM/PlAFchnGDWvl6DmfUx9VZnk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=vsjdxr3WEMQAouRQQDcN3R10xSFTo0qcMFWGvc8Ow1LLcvcEwWkNEH8wF7KPn4Gz0rzlSWL7C9ATe9ypOABjxndHAmhgJMrc0621UpLZmrz8FaMYMCKZymzBAC8f6k0B6x10UyQbkksi1BY32hjt3njn7iyZk/rRw2qdMwrFOAA= Received: by 10.114.146.1 with SMTP id t1mr165864wad.20.1207748848292; Wed, 09 Apr 2008 06:47:28 -0700 (PDT) Received: by 10.114.102.14 with HTTP; Wed, 9 Apr 2008 06:47:28 -0700 (PDT) Message-ID: <2ca799770804090647m759b72f9gf2d49b4bf7cc8bdf@mail.gmail.com> Date: Wed, 9 Apr 2008 16:47:28 +0300 From: "Mikko Partio" To: pgsql-admin@postgresql.org Subject: FATAL: could not open relation xxx: No such file or directory MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5353_3372136.1207748848285" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/88 X-Sequence-Number: 28852 ------=_Part_5353_3372136.1207748848285 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. Regards Mikko ------=_Part_5353_3372136.1207748848285 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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.

Regards

Mikko


------=_Part_5353_3372136.1207748848285--