Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Date
Msg-id 28633.1338150915@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2  (Adrian Klaver <adrian.klaver@gmail.com>)
Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-bugs
Adrian Klaver <adrian.klaver@gmail.com> writes:
> After reading the above thread here is what the queries mentioned return:

> production=#  SELECT nspname,proname,probin FROM pg_proc,pg_namespace
> WHERE probin LIKE '%python%' and pg_proc.pronamespace=pg_namespace.oid;

> nspname   |         proname         |      probin
> ------------+-------------------------+------------------
>  pg_catalog | plpython_call_handler   | $libdir/plpython
>  pg_catalog | plpython_inline_handler | $libdir/plpython
>  public     | plpython_call_handler   | $libdir/plpython
> (3 rows)

I think what you need to do is drop the one in public, ie
    drop function public.plpython_call_handler();
The other two are what the language is actually using nowadays.

Hopefully pg_upgrade will then cope with upgrading them ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Next
From: Adrian Klaver
Date:
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2