Thread: Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0
Thanks Tom,
Unfortunately, upgrading is not in the cards, since both 10.11 and 11.6 environments are what azure currently have as their versions for their postgres as a service.
I have installed both 10.11 and 11.6 to try and duplicate on a local docker image, but it did not succeed.
I can't really duplicate this issue using tests. It only happens in production environments unfortunately. I believe it has something to do with connection pooling and asynchronous operations, but I cannot prove it.
I believe something happens where we are writing to the freshly created table, could be related to how azure manages the storage behind the scenes? I am not sure how the storage devices are architected behind the scenes. ( the benefits of platform as a service...).
Is there some threading issue where the newly created table is not ready or out of sync with the internal object cache of postgres when the storage is slower / network attached?
Thanks,
Vlad
On Thu, Mar 18, 2021 at 3:12 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
PG Bug reporting form <noreply@postgresql.org> writes:
> Randomly, we see this error in the logs:
> 2021-03-18 07:52:32 UTC-6052fa73.12638-ERROR: cache lookup failed for type
> 0
> Our process is as follows ( pseudo code simplified ):
> begin trans;
> call a procedure that drops and re-creates a table.
> commit;
> begin trans
> loop 1000 rows
> insert into table above....
> end loop;
> commit;
Hm. Can you provide a self-contained test case?
It'd also be worth your time to update to latest 10.x, in case this is
an already-fixed bug. A quick trawl of the commit logs didn't turn up
an obvious match, but I might have missed a relevant fix.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
regards, tom lane