Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 4855E475D21 for ; Sun, 9 Jun 2002 15:28:15 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 4F097475C42 for ; Sun, 9 Jun 2002 15:28:14 -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 g59JS7b06845; Sun, 9 Jun 2002 15:28:07 -0400 (EDT) To: "Ian Cass" Cc: pgsql-sql@postgresql.org Subject: Re: select failure In-reply-to: <083e01c20e29$7c99fdf0$6602a8c0@salamander> References: <083e01c20e29$7c99fdf0$6602a8c0@salamander> Comments: In-reply-to "Ian Cass" message dated "Fri, 07 Jun 2002 14:44:45 +0100" Date: Sun, 09 Jun 2002 15:28:07 -0400 Message-ID: <6842.1023650887@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200206/98 X-Sequence-Number: 8063 "Ian Cass" writes: > FATAL 2: open of /var/lib/postgres/data/pg_clog/0534 failed: No such file > or directory We have seen a couple reports like this one, eg http://archives.postgresql.org/pgsql-general/2002-03/msg00179.php http://archives.postgresql.org/pgsql-novice/2002-06/msg00027.php It could be that all of you have been bitten by hardware problems (viz, dropped bits in xmin/xmax fields), or there might be some software bug that's leading to this failure. So far, no one's been very cooperative about digging into a failure case to try to determine exactly what happened... regards, tom lane