pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: GMX LINREG <linreg@gmx.net>
Cc: Bruce Momjian <bruce@momjian.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 12:55:42 -0500
Message-ID: <2816651.1611942942@sss.pgh.pa.us> (raw)
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>

GMX LINREG <linreg@gmx.net> 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





view thread (14+ messages)  latest in thread

Message-ID: <2816651.1611942942@sss.pgh.pa.us>
Permalink:  ../2816651.1611942942@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2816651.1611942942@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, linreg@gmx.net, bruce@momjian.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: <2816651.1611942942@sss.pgh.pa.us>

* 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