Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 18BE79FB474 for ; Tue, 26 Sep 2006 19:36:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 45117-02 for ; Tue, 26 Sep 2006 22:36:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A935B9FA4C5 for ; Tue, 26 Sep 2006 19:36:41 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k8QMacRn001087; Tue, 26 Sep 2006 18:36:38 -0400 (EDT) To: "Gregory S. Williamson" cc: "Talha Khan" , pgsql-admin@postgresql.org Subject: Re: Runtime error: could not open segment 1 of relation ... In-reply-to: <71E37EF6B7DCC1499CEA0316A256832802B3E60D@loki.wc.globexplorer.net> References: <71E37EF6B7DCC1499CEA0316A256832802B3E60A@loki.wc.globexplorer.net> <71E37EF6B7DCC1499CEA0316A256832802B3E60D@loki.wc.globexplorer.net> Comments: In-reply-to "Gregory S. Williamson" message dated "Tue, 26 Sep 2006 15:28:58 -0700" Date: Tue, 26 Sep 2006 18:36:38 -0400 Message-ID: <1083.1159310198@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/318 X-Sequence-Number: 23232 "Gregory S. Williamson" writes: >> 2006-09-26 10:02:15.124 PDT 1387333718 ERROR: could not open segment 1 of >> relation 1663/43801/7274801 (target block 478216192): No such file or >> directory This is most likely caused by trying to follow a bogus item pointer in an index. If the problem went away after a restart, the bogus value could not have been on disk but must have been in a bad in-memory copy of an index page. Which suggests a hardware glitch ... although if you are using contrib/ltree, I recall seeing several bug fixes go by recently that were described as fixing potential ltree-index corruption issues. regards, tom lane