Re: pg_upgrade from 12 to 13 failes with plpython2 - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_upgrade from 12 to 13 failes with plpython2
Date
Msg-id 1026148.1605766260@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade from 12 to 13 failes with plpython2  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general
Bruce Momjian <bruce@momjian.us> writes:
> It didn't trigger this message for him, and I am also wondering if it
> should have.

The extra functions in this case were in pg_catalog, not public,
so there is exactly no part of that error message that is applicable.

In any case, that seems an overly specific solution.  The generic
problem is how to usefully identify some functions that have dangling
probin pointers.  I don't want a solution that only works for the
plpython functions.

            regards, tom lane



pgsql-general by date:

Previous
From: Paul Förster
Date:
Subject: Re: create type with %type or %rowtype
Next
From: Matthias Apitz
Date:
Subject: \COPY command and indexes in tables