Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lMtNp-0004tf-Jd for pgsql-bugs@arkaria.postgresql.org; Thu, 18 Mar 2021 14:12:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lMtNn-0005D3-RZ for pgsql-bugs@arkaria.postgresql.org; Thu, 18 Mar 2021 14:12:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lMtNn-0005Cw-Lk for pgsql-bugs@lists.postgresql.org; Thu, 18 Mar 2021 14:12:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lMtNg-00018l-Ix; Thu, 18 Mar 2021 14:12:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 12IEC50x3717549; Thu, 18 Mar 2021 10:12:05 -0400 From: Tom Lane To: github@vlqubed.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form Subject: Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0 In-reply-to: <16932-fc795566ddd4a5f1@postgresql.org> References: <16932-fc795566ddd4a5f1@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 18 Mar 2021 08:46:35 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3717547.1616076725.1@sss.pgh.pa.us> Date: Thu, 18 Mar 2021 10:12:05 -0400 Message-ID: <3717548.1616076725@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form 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