From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-28 14:19:55 |
Message-ID: | 4FC3898B.1040604@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 05/27/2012 01:35 PM, Tom Lane wrote:
> 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 ...
To follow up, I dropped the public function and reran pg_upgrade from
scratch and it completed successfully.
>
> regards, tom lane
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | dmitryturin | 2012-05-28 15:12:53 | BUG #6667: diplom on english language on your site |
Previous Message | Adrian Klaver | 2012-05-27 20:53:25 | Re: BUG #6666: pg_upgrade 9.2beta1 plpython/plpython2 |