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 1l5Xzw-0005TD-El for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 17:55:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l5Xzt-0005PQ-TV for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 17:55:53 +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 1l5Xzt-0005PJ-NJ for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 17:55:53 +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 1l5Xzo-0007Lw-3B for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 17:55:52 +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 10THtgQD2816652; Fri, 29 Jan 2021 12:55:42 -0500 From: Tom Lane To: GMX LINREG cc: Bruce Momjian , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed In-reply-to: <5448993.DvuYhMxLoT@wolfclan.ang.de> References: <16843-174d3e5b66729a60@postgresql.org> <7912997.NyiUUSuA9g@wolfclan.ang.de> <2815190.1611941374@sss.pgh.pa.us> <5448993.DvuYhMxLoT@wolfclan.ang.de> Comments: In-reply-to GMX LINREG message dated "Fri, 29 Jan 2021 18:38:18 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2816650.1611942942.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 29 Jan 2021 12:55:42 -0500 Message-ID: <2816651.1611942942@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk GMX LINREG writes: > output from source database: > botdb=# \dx+ plperlu > Objekte in Erweiterung »plperlu« > Objektbeschreibung > -------------------- > language plperlu Yeah, that's definitely broken: it should look like \dx+ plperlu Objects in extension "plperlu" Object description ------------------------------------------- function plperlu_call_handler() function plperlu_inline_handler(internal) function plperlu_validator(oid) language plperlu (4 rows) Offhand I think that completely explains pg_dump's failure: it relies on the dependency-membership entries to decide that it ought to dump the language support functions, so if they're not there, this is what you get. It's possible that the entries *are* there but they're not being found due to index corruption. You could try "REINDEX TABLE pg_depend" and see if the \dx+ output changes. I don't have a lot of hope for that though. The next easiest fix would be to see if you have any plperlu functions to worry about, and if not, just drop the busted extension. If you do have some such functions, the best bet might be to dump them separately, go ahead and DROP CASCADE the busted extension, then upgrade; and restore the plperlu functions separately afterwards. It'd be kind of interesting to figure out why those pg_depend entries are missing, but I suppose the evidence is long gone :-( regards, tom lane