From: | Robert Mosher <mosher(at)andrews(dot)edu> |
---|---|
To: | Mailing List Postgresql <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Corrupted table |
Date: | 2001-10-08 23:20:19 |
Message-ID: | Pine.SOL.3.91.1011008191501.29394A-100000@orion.cc.andrews.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
> Robert Mosher <mosher(at)andrews(dot)edu> writes:
> > In a Perl script I ended up trying to UPDATE a row in my database with a
> > value that was out of the range. Now whenever I try to do something with
> > the table I get the error:
>
> > ERROR: mdopen: couldn't open tablename: No such file or directory
>
> It seems unlikely that the one led to the other. The known ways to
> cause that type of failure involve other things, like trying to roll
> back a DROP TABLE.
>
> How old is your Postgres?
It's version 6.5.3 . Does this limit my solutions then?
>
> > I can't even drop the table, despite the fact that it shows up when I
> > enter '\dt' in psql. I could probably run destroydb on the
> > database that contains the table,
>
> If it's called "destroydb" and not "dropdb", then the answer to my
> question is "too old". Consider an update, soon.
>
Rob Mosher
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Mosher | 2001-10-09 00:49:36 | Re: Corrupted table |
Previous Message | Tom Lane | 2001-10-08 21:43:11 | Re: Corrupted table |