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

From Marcin Giedz
Subject Re: pg_upgrade from 12 to 13 failes with plpython2
Date
Msg-id 1948396366.1497285.1605729598546.JavaMail.zimbra@arise.pl
Whole thread Raw
In response to Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade from 12 to 13 failes with plpython2
List pgsql-general

> anyway got this from your query:

> 16402 | plpython_call_handler | 11 | 10 | 13 | 1 | 0 | 0 | - | f | f | f | f | f | v | u | 0 | 0 | 2280 | | | | | | | plpython_call_handler | $libdir/plpython2 | |
> 16403 | plpython_inline_handler | 11 | 10 | 13 | 1 | 0 | 0 | - | f | f | f | t | f | v | u | 1 | 0 | 2278 | 2281 | | | | | | plpython_inline_handler | $libdir/plpython2 | |
> 16404 | plpython_validator | 11 | 10 | 13 | 1 | 0 | 0 | - | f | f | f | t | f | v | u | 1 | 0 | 2278 | 26 | | | | | | plpython_validator | $libdir/plpython2 | |

Uh-huh, so there you have it.  These must be leftovers from some
pre-extension incarnation of plpython that was never cleaned up
properly.  Try

DROP FUNCTION pg_catalog.plpython_call_handler();
DROP FUNCTION pg_catalog.plpython_inline_handler(internal);
DROP FUNCTION pg_catalog.plpython_validator(oid);

It'll be interesting to see if there are any dependencies.

                        regards, tom lane

-------------------------------------

BINGO! after drops all went smooth and easy


Many thx Tom!

M.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2