pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: github@vlqubed.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0
Date: Thu, 18 Mar 2021 10:12:05 -0400
Message-ID: <3717548.1616076725@sss.pgh.pa.us> (raw)
In-Reply-To: <16932-fc795566ddd4a5f1@postgresql.org>
References: <16932-fc795566ddd4a5f1@postgresql.org>

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





view thread (3+ messages)  latest in thread

Message-ID: <3717548.1616076725@sss.pgh.pa.us>
Permalink:  ../3717548.1616076725@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3717548.1616076725@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, noreply@postgresql.org
  Subject: Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0
  In-Reply-To: <3717548.1616076725@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox