Re: [GENERAL] Cause of ERROR: could not open relation

2006-10-03 Thread Tom Lane
"Wyatt Tellis" <[EMAIL PROTECTED]> writes: >>> I'm running 8.1.4 on W2K3 R2. I occasionally get errors of the type: >>> ERROR: could not open relation 1663/856689/856777: Invalid argument > I was able to figure out the table name, but is there a way to figure > out which file caused this error?

Re: [GENERAL] Cause of ERROR: could not open relation

2006-10-02 Thread Wyatt Tellis
Tom Lane wrote: "Wyatt Tellis" <[EMAIL PROTECTED]> writes: I'm running 8.1.4 on W2K3 R2. I occasionally get errors of the type: ERROR: could not open relation 1663/856689/856777: Invalid argument Is there a command or way to determine if an index is corrupt? Is there anyway to discern this in

Re: [GENERAL] Cause of ERROR: could not open relation

2006-10-01 Thread Tom Lane
"Wyatt Tellis" <[EMAIL PROTECTED]> writes: >> I'm running 8.1.4 on W2K3 R2. I occasionally get errors of the type: >> ERROR: could not open relation 1663/856689/856777: Invalid argument > Is there a command or way to determine if an index is corrupt? Is there > anyway to discern this info from th

Re: [GENERAL] Cause of ERROR: could not open relation

2006-10-01 Thread Wyatt Tellis
Greg, Thanks for the pointers. I couldn't find a reference on the pg-admin list to this exact error but I've read up a bit on the REINDEX command. Is there a command or way to determine if an index is corrupt? Is there anyway to discern this info from the error message itself (i.e. are the nu

Re: [GENERAL] Cause of ERROR: could not open relation 1663/856689/856777: Invalid argument?

2006-09-30 Thread Gregory S. Williamson
Wyatt -- We got a spate of similar errors recently; turned out to be a disk was not mounted properly. Once it was reseated all was well. You might also do a RAM check just to make sure that something isn't wonky there. IIRC, I was told (see the archives of the postgres admin mail list) that thi