System crash and trying to run vacuum getting errors

[Dave Smith]

After a abnormal system shutdown I am trying to run a
vacuum full verbose ANALYZE and getting the following error.

NOTICE: Analyzing classification
NOTICE: RelationBuildDesc: can't open pg_temp_5821_0: No such file or
directory
NOTICE: --Relation pg_temp_5821_0--
ERROR: _mdfd_getrelnfd: cannot open relation pg_temp_5821_0: No such
file or directory

--
Dave Smith
CANdata Systems Ltd
416-493-9020
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Tom Lane]

Dave Smith <da********@candata.com> writes:

After a abnormal system shutdown I am trying to run a
vacuum full verbose ANALYZE and getting the following error. NOTICE: Analyzing classification
NOTICE: RelationBuildDesc: can't open pg_temp_5821_0: No such file or
directory
NOTICE: --Relation pg_temp_5821_0--
ERROR: _mdfd_getrelnfd: cannot open relation pg_temp_5821_0: No such
file or directory

You should be able to DROP that table even though it doesn't have an
underlying file. My guess is that you are running atop a non-crash-safe
filesystem and it lost the directory entry for the just-created file.
You might want to think about switching to a journaling file system.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Dave Smith]

Yup that's what happened. Dropped them and all is good. I really should
get a list of all of the underling files for each index and table and
see if any others are missing.

On Wed, 2003-11-05 at 11:30, Tom Lane wrote:

Dave Smith <da********@candata.com> writes:

After a abnormal system shutdown I am trying to run a
vacuum full verbose ANALYZE and getting the following error.

NOTICE: Analyzing classification
NOTICE: RelationBuildDesc: can't open pg_temp_5821_0: No such file or
directory
NOTICE: --Relation pg_temp_5821_0--
ERROR: _mdfd_getrelnfd: cannot open relation pg_temp_5821_0: No such
file or directory

You should be able to DROP that table even though it doesn't have an
underlying file. My guess is that you are running atop a non-crash-safe
filesystem and it lost the directory entry for the just-created file.
You might want to think about switching to a journaling file system.

regards, tom lane

--
Dave Smith
CANdata Systems Ltd
416-493-9020
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Tom Lane]

Dave Smith <da********@candata.com> writes:

Yup that's what happened. Dropped them and all is good. I really should
get a list of all of the underling files for each index and table and
see if any others are missing.

If VACUUM ran to completion without complaints then there aren't any
other missing files.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

[Greg Stark]

Tom Lane <tg*@sss.pgh.pa.us> writes:

You should be able to DROP that table even though it doesn't have an
underlying file. My guess is that you are running atop a non-crash-safe
filesystem and it lost the directory entry for the just-created file.
You might want to think about switching to a journaling file system.

In which case you might find them in /lost+found
--
greg
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match