Skip site navigation (1) Skip section navigation (2)

Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Date: 2012-05-27 20:35:15
Message-ID: 28633.1338150915@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Adrian KlaverDate: 2012-05-27 20:53:25
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2
Previous:From: Adrian KlaverDate: 2012-05-27 18:49:31
Subject: Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group