Table drop that fails ... "No such file or directory"

Just has a support call where the client couldn't drop a table, giving him
a 'No such file or directory' error...yet a \d showed him that the table
existed...

To "fix" the problem, we got him to shutdown his server, touch the file
that it says is missing, bring the server back up and then drop
it...which, of course, succeeded...

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?

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