Re: [HACKERS] Table drop that fails ... "No such file or directory"

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Table drop that fails ... "No such file or directory"
Date: 2000-01-07 21:13:50
Message-ID: Pine.BSF.4.21.0001071711000.18498-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 7 Jan 2000, Bruce Momjian wrote:

> > But...does it make sense to error-out in this case? The user wants to get
> > rid of the table, the table is already gone physically, just not
> > virtually...so why not just get rid of the virtual entries also?
>
> It shows something very strange happened to him. We don't want this
> kind of thing to just happen.

Okay...what should be done? How do you trace something like this back?

The scenario for this particular table, as it was explained to me, was
that its the result of a join of two other tables...they find that its
easier to do teh join into one table periodically and use that for
selects, then doing SELECT/JOINS on the fly ... my thought was that what
may have happened is they ran out of disk space on the JOIN, the file was
removed, but not the traces in the systems files, is this a possibility?

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-01-07 21:16:26 Re: [HACKERS] Table drop that fails ... "No such file or directory"
Previous Message Bruce Momjian 2000-01-07 21:05:36 Re: [HACKERS] Table drop that fails ... "No such file or directory"