Skip site navigation (1) Skip section navigation (2)

Re: "could not open file" issue

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Daniel Caune <daniel(dot)caune(at)ubisoft(dot)com>
Cc: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-sql(at)postgresql(dot)org
Subject: Re: "could not open file" issue
Date: 2006-04-24 21:40:07
Message-ID: 20060424214006.GE18690@surnet.cl (view raw or flat)
Thread:
Lists: pgsql-sql
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.

In response to

pgsql-sql by date

Next:From: Jim C. NasbyDate: 2006-04-25 00:15:53
Subject: Re: Migrating a Database to a new tablespace
Previous:From: Daniel CauneDate: 2006-04-24 21:02:37
Subject: Re: "could not open file" issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group