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 1l5VKY-0004zP-VG for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 15:05:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l5VKX-0002TV-PC for pgsql-bugs@arkaria.postgresql.org; Fri, 29 Jan 2021 15:05:01 +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 1l5VKX-0002TN-Ir for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 15:05:01 +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 1l5VKU-0006Ix-GL for pgsql-bugs@lists.postgresql.org; Fri, 29 Jan 2021 15:05:00 +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 10TF4snR2780635; Fri, 29 Jan 2021 10:04:54 -0500 From: Tom Lane To: GMX Steffen 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: <7226587.EvYhyI6sBW@wolfclan.ang.de> References: <16843-174d3e5b66729a60@postgresql.org> <2547214.1611848625@sss.pgh.pa.us> <20210128155644.GB14227@momjian.us> <7226587.EvYhyI6sBW@wolfclan.ang.de> Comments: In-reply-to GMX Steffen message dated "Fri, 29 Jan 2021 14:23:31 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2780633.1611932694.1@sss.pgh.pa.us> Date: Fri, 29 Jan 2021 10:04:54 -0500 Message-ID: <2780634.1611932694@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk GMX Steffen writes: > OS Packages: > *postgresql*-llvmjit-13-lp152.3.1.noarch > *postgresql*12-pldebugger-1.0+git13.ddbce7b-lp152.1.4.x86_64 > *postgresql*12-llvmjit-12.5-lp152.34.1.x86_64 > *postgresql*-13-lp152.3.1.noarch > *postgresql*12-docs-12.5-lp152.34.1.noarch > *postgresql*12-contrib-12.5-lp152.34.1.x86_64 > *postgresql*13-plperl-13.1-lp152.16.1.x86_64 > *postgresql*12-server-12.5-lp152.34.1.x86_64 > *postgresql*-docs-13-lp152.3.1.noarch > *postgresql*12-12.5-lp152.34.1.x86_64 > *postgresql*12-pg_qualstats-2.0.2-lp152.2.3.x86_64 > *postgresql*12-ip4r-2.4.1+git1.5f9ce88-lp152.8.2.x86_64 > *postgresql*-server-13-lp152.3.1.noarch > *postgresql*12-pg_qualstats-llvmjit-2.0.2-lp152.2.3.x86_64 > *postgresql*13-docs-13.1-lp152.16.1.noarch > *postgresql*13-server-13.1-lp152.16.1.x86_64 > *postgresql*-contrib-13-lp152.3.1.noarch > *postgresql*12-ip4r-llvmjit-2.4.1+git1.5f9ce88-lp152.8.2.x86_64 > *postgresql*13-13.1-lp152.16.1.x86_64 > *postgresql*13-llvmjit-13.1-lp152.16.1.x86_64 > *postgresql*-plperl-13-lp152.3.1.noarch > *postgresql*12-pldebugger-llvmjit-1.0+git13.ddbce7b-lp152.1.4.x86_64 > *postgresql*13-contrib-13.1-lp152.16.1.x86_64 This ... looks like a bit of a mess. You evidently have three independent sets of Postgres packages, but surely there should only be two. And why do they all have "lp152" in the version? (And why are there only two versions of plperl? And why are some of these "noarch"? That would make sense for the docs subpackage, but not much else.) The pg_restore trace gives us no more info than we had before. But given this package list, I am suspecting some confusion over which version of plperl.so should get loaded. You might try looking into the destination postmaster's log file (not pg_upgrade's user-visible output) to see if there is any low-level message from the dynamic loader emitted just before it complains about plperlu not existing. regards, tom lane