Re: cache lookup failed

"Pascal Tufenkji" <ptufenkji(at)usj(dot)edu(dot)lb> writes:
> Everything was working fine until a couple of days ago, the database is
> starting to display the following error more and more
> cache lookup failed for relation 1852615815

Hm, what PG version is that? Is 1852615815 anywhere near the range of
existing OIDs in pg_class?

> If I look up for this oid in pg_class I dont find it, but I do find it in
> pg_depend. Is that normal ?

No --- at least not when the classid says it's a pg_class OID, as it
does here. Do you find any pg_depend rows with refobjid = 1852615815?
What about other rows mentioning OID 111893? Is that OID present in
pg_namespace? (The 2615 says it's a pg_namespace OID.)

We have seen some previous reports suggesting that once in awhile not
all the catalog entries associated with temp tables get cleaned out at
backend exit. I'm not sure the cause has ever been conclusively
identified, though if memory serves we have fixed a bug or two that
*might* explain it.

If 1852615815 doesn't seem to be a legitimate OID, it's also possible
that this is just data corruption in pg_depend.

If you can't find any evidence of other issues, it might be reasonable
to conclude that the pg_depend row is leftover junk and delete it
manually. But you should make real sure nothing is linked to it first.

regards, tom lane