X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CBC3111F605F for ; Mon, 24 Apr 2006 18:40:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 02591-09 for ; Mon, 24 Apr 2006 18:40:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx2.surnet.cl (mx2.surnet.cl [216.155.73.181]) by postgresql.org (Postfix) with ESMTP id 05BDC11F6C5A for ; Mon, 24 Apr 2006 18:40:07 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx2.surnet.cl with ESMTP; 24 Apr 2006 17:40:07 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AQAAAHrcTESIaQEKDio X-IronPort-AV: i="4.02,198,1139194800"; d="scan'208"; a="45508878:sNHT16181924" Received: from alvh.no-ip.org (200.126.100.190) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 443B7DDC001CC26E; Mon, 24 Apr 2006 17:40:07 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 1A61BC30F8E; Mon, 24 Apr 2006 17:40:07 -0400 (CLT) Date: Mon, 24 Apr 2006 17:40:07 -0400 From: Alvaro Herrera To: Daniel Caune Cc: Andrew Sullivan , pgsql-sql@postgresql.org Subject: Re: "could not open file" issue Message-ID: <20060424214006.GE18690@surnet.cl> Mail-Followup-To: Daniel Caune , Andrew Sullivan , pgsql-sql@postgresql.org References: <1E293D3FF63A3740B10AD5AAD88535D20213299C@UBIMAIL1.ubisoft.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1E293D3FF63A3740B10AD5AAD88535D20213299C@UBIMAIL1.ubisoft.org> User-Agent: Mutt/1.5.11+cvs20060403 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/168 X-Sequence-Number: 24977 Daniel Caune wrote: > It seems that was possible: I tried first to truncate the table (it > passed), and finally I tried to drop the table (it also passed). Then > I created the table. I'm not sure that it fixes my problem. I > modified my fstab file so that Linux checks my file system's health on > the next boot. If you experienced memory corruption, it would be wise to run some hardware diagnosys tools, just to be sure. For example memtest86, badblocks, etc. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.