Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 113D1476FD7 for ; Thu, 13 Jun 2002 16:51:09 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 9D0A1477466 for ; Thu, 13 Jun 2002 16:07:29 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g5DK7Rb29004; Thu, 13 Jun 2002 16:07:27 -0400 (EDT) To: "Ian Cass" Cc: pgsql-sql@postgresql.org Subject: Re: Another postgres 'file not found' error In-reply-to: <106501c212cb$d6f49750$6602a8c0@salamander> References: <106501c212cb$d6f49750$6602a8c0@salamander> Comments: In-reply-to "Ian Cass" message dated "Thu, 13 Jun 2002 12:17:00 +0100" Date: Thu, 13 Jun 2002 16:07:26 -0400 Message-ID: <29001.1023998846@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200206/184 X-Sequence-Number: 8149 "Ian Cass" writes: > inbound=# update store set state = 0, timestamp = 'now' where timestamp < > (CURRENT_TIMESTAMP - interval '30 seconds') and accountid = '6'; > ERROR: cannot open segment 1 of relation store_ix1 (target block > 1576985508): No such file or directory and later: > In this instance, simply dropping the index and recreating it solved the > problem. Yeah, it would seem that you had a bad tuple pointer in an index entry. While this might have been induced by a software bug, I do not recall many (if any) prior reports of such failures, so I'm leaning towards a hardware glitch having caused it. I'd recommend running some memory and disk diagnostics ... regards, tom lane