pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: GMX Steffen <steffen.ang@gmx.de>
To: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16843: pg_upgrade from 12.5 to 13.1 with extension plperlu failed
Date: Fri, 29 Jan 2021 14:23:31 +0100
Message-ID: <7226587.EvYhyI6sBW@wolfclan.ang.de> (raw)
In-Reply-To: <20210128155644.GB14227@momjian.us>
References: <16843-174d3e5b66729a60@postgresql.org>
	<2547214.1611848625@sss.pgh.pa.us>
	<20210128155644.GB14227@momjian.us>

Am Donnerstag, 28. Januar 2021, 16:56:44 CET schrieben Sie:
> On Thu, Jan 28, 2021 at 10:43:45AM -0500, Tom Lane wrote:
> > Bruce Momjian <bruce@momjian.us> writes:
> > > On Thu, Jan 28, 2021 at 10:34:46AM -0500, Tom Lane wrote:
> > >> PG Bug reporting form <noreply@postgresql.org> writes:
> > >>> pg_restore: Error: could not execute query: ERROR:  Language »plperlu«
> > >>> does
> > >>> not exist
> > >>> The statement was: CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";
> > >> 
> > >> It looks like you neglected to install the plperlu package
> > >> (it's probably named something like postgresql-plperl).
> > > 
> > > Yeah, I am confused why this was not reported clearly to the user.
> > 
> > It is odd that pg_upgrade's checks didn't catch it earlier.  But
> > we can't investigate without more info about exactly what Postgres
> > packages are present on the OP's system.
> 
> Yes, usually the error report is very clear, we would need to see
> _exactly_ what they saw.

Hello,

to clearify, 
- plperl package is already installed (see below).
- command 'CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu";' doesn't create a 
language object, but just an extension object (see below)

Please note the attached upgrade log file from pg_upgrade "pg_upgrade_dump_16401.log".

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

Output from failed database upgrade:
botdb=# \dL 

Attachments:

pg_upgrade_dump_16401.log (text/x-log, 2.9K) download command: "/usr/lib/postgresql13/bin/pg_dump" --host /var/lib/pgsql --port 50432 --username postgres --schema-only --quote-all-identifiers --binary-upgrade --format=custom --file="pg_upgrade_dump_16401.custom" 'dbname=botdb' >> "pg_upgrade_dump_16401.log" 2>&1 command: "/usr/lib/postgresql13/bin/pg_dump" --host /var/lib/pgsql --port 50432 --username postgres --schema-only --quote-all-identifiers --binary-upgrade --format=custom --file="pg_upgrade_dump_16401.custom" 'dbname=botdb' >> "pg_upgrade_dump_16401.log" 2>&1 command: "/usr/lib/postgresql13/bin/pg_restore" --host /var/lib/pgsql --port 50432 --username postgres --create --exit-on-error --verbose --dbname template1 "pg_upgrade_dump_16401.custom" >> "pg_upgrade_dump_16401.log" 2>&1 pg_restore: verbinde mit der Datenbank zur Wiederherstellung pg_restore: erstelle DATABASE »botdb« pg_restore: verbinde mit neuer Datenbank »botdb« pg_restore: erstelle DATABASE PROPERTIES »botdb« pg_restore: verbinde mit neuer Datenbank »botdb« pg_restore: erstelle pg_largeobject »pg_largeobject« pg_restore: erstelle SCHEMA »callbot« pg_restore: erstelle SCHEMA »crm_test« pg_restore: erstelle SCHEMA »firmenbots« pg_restore: erstelle SCHEMA »geo« pg_restore: erstelle SCHEMA »immo« pg_restore: erstelle SCHEMA »lassi« pg_restore: erstelle SCHEMA »mieten_kataster« pg_restore: erstelle SCHEMA »my_cam_bot« pg_restore: erstelle EXTENSION »pg_cron« pg_restore: erstelle COMMENT »EXTENSION "pg_cron"« pg_restore: erstelle SCHEMA »pgcron« pg_restore: erstelle COMMENT »SCHEMA "pgcron"« pg_restore: erstelle EXTENSION »hstore« pg_restore: erstelle COMMENT »EXTENSION "hstore"« pg_restore: erstelle EXTENSION »pg_http« pg_restore: erstelle COMMENT »EXTENSION "pg_http"« pg_restore: erstelle SCHEMA »pghttp« pg_restore: erstelle EXTENSION »pg_mqtt« pg_restore: erstelle COMMENT »EXTENSION "pg_mqtt"« pg_restore: erstelle SCHEMA »pgmqtt« pg_restore: erstelle SCHEMA »planer« pg_restore: erstelle SCHEMA »privatebots« pg_restore: erstelle SCHEMA »replication« pg_restore: erstelle EXTENSION »pg_reporting« pg_restore: erstelle COMMENT »EXTENSION "pg_reporting"« pg_restore: erstelle SCHEMA »reporting« pg_restore: erstelle SCHEMA »taskbot« pg_restore: erstelle SCHEMA »teams« pg_restore: erstelle SCHEMA »telegram« pg_restore: erstelle SCHEMA »websites« pg_restore: erstelle EXTENSION »plperlu« pg_restore: erstelle COMMENT »EXTENSION "plperlu"« pg_restore: erstelle PROCEDURAL LANGUAGE »plperlu« pg_restore: in Phase PROCESSING TOC: pg_restore: in Inhaltsverzeichniseintrag 2151; 2612 16427 PROCEDURAL LANGUAGE plperlu postgres pg_restore: Fehler: could not execute query: FEHLER: Sprache »plperlu« existiert nicht Die Anweisung war: CREATE OR REPLACE PROCEDURAL LANGUAGE "plperlu"; -- For binary upgrade, handle extension membership the hard way ALTER EXTENSION "plperlu" ADD LANGUAGE "plperlu";

view thread (14+ messages)  latest in thread

Message-ID: <7226587.EvYhyI6sBW@wolfclan.ang.de>
Permalink:  ../7226587.EvYhyI6sBW@wolfclan.ang.de/
Also on:    postgresql.org/message-id/7226587.EvYhyI6sBW@wolfclan.ang.de

 · 

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: steffen.ang@gmx.de, bruce@momjian.us, tgl@sss.pgh.pa.us, 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>

* 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