> > > 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?
> >
> > Maybe a SELECT INTO failed. You would think it could delete the entries
> > too, or at least the transaction that created the table would be marked
> > as aborted.
>
> Or it could be nothing more then a hard crash of the server :(
That could not mark the transaction that completed the table as
committed.
-- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
