I have noticed a few threads pertaining to the "cache lookup failed" error message, and thought I would add some data to the mix. I have suffered this error in the past, and worked around it by dumping, dropping and restoring my database (which is what landed me asking for help yesterday :)). I thought I would throw some data out into the mix in the hopes that it might find someone else who is suffering from the trouble. My circumstance leading to the error: - postgresql 8.3.7 on Centos Linux - PHP connections that create temp table and populate with 100-200K records (environmental modeling simulation system) - tables dropped explicitly at the end of a simulation run (just an effort to be tidy) - at times database log gives error "cache lookup failed for relation XYXY" as a result of the call: "create temp table tmp_tablname ..." - inserts attempts to this table subsequently fail "relation tmp_tablname does not exist" - copying and pasting the CREATE and INSERT statements into a psql command line session SUCCEED without any issue, but subsequent PHP connections (via command line call to php) FAIL with same errors. - dump, drop and recreating the database fixes the problem (for a while) >From what I gathered looking through archives yesterday, this makes ME think that it is catalog corruption perhaps? But it would seem that the PHP connections should not behave differently than the psql connections, but I don't know enough to really say that... Regards, r.b. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
