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 1l5XaX-00042M-Sb for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 17:29:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l5XaW-0007dL-Kt for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 17:29:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l5XaW-0007dE-EN for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 17:29:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l5XaU-0007JB-Fq for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 17:29:39 +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 10THTYaH2815191; Fri, 29 Jan 2021 12:29:34 -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: <7912997.NyiUUSuA9g@wolfclan.ang.de> References: <16843-174d3e5b66729a60@postgresql.org> <7226587.EvYhyI6sBW@wolfclan.ang.de> <2780634.1611932694@sss.pgh.pa.us> <7912997.NyiUUSuA9g@wolfclan.ang.de> Comments: In-reply-to GMX LINREG message dated "Fri, 29 Jan 2021 17:40:46 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2815189.1611941374.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 29 Jan 2021 12:29:34 -0500 Message-ID: <2815190.1611941374@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Looking at this more closely, it seems like there must be something broken about the plperlu extension in the source database. We see pg_restore: erstelle EXTENSION =C3=82=C2=BBplperlu=C3=82=C2=AB pg_restore: erstelle COMMENT =C3=82=C2=BBEXTENSION "plperlu"=C3=82=C2=AB pg_restore: erstelle PROCEDURAL LANGUAGE =C3=82=C2=BBplperlu=C3=82=C2=AB pg_restore: in Phase PROCESSING TOC: pg_restore: in Inhaltsverzeichniseintrag 2151; 2612 16427 PROCEDURAL LANGU= AGE plperlu postgres pg_restore: Fehler: could not execute query: FEHLER: Sprache =C3=82=C2=BB= plperlu=C3=82=C2=AB existiert nicht Die Anweisung war: CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu"; but a binary-upgrade dump should have dumped the plperlu support functions before the procedural language object. And the CREATE PROCEDURAL LANGUAGE command should have included explicit HANDLER etc clauses. Both things could be explained by supposing that pg_dump didn't see the support functions as part of the extension, but why not? It might be interesting to check the results of "\dx+ plperlu" in the source database. regards, tom lane