Re: testing plpython3u on 9.0beta2
От | Peter Eisentraut |
---|---|
Тема | Re: testing plpython3u on 9.0beta2 |
Дата | |
Msg-id | 1277445467.28123.7.camel@vanquo.pezone.net обсуждение исходный текст |
Ответ на | Re: testing plpython3u on 9.0beta2 (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: testing plpython3u on 9.0beta2
|
Список | pgsql-hackers |
On ons, 2010-06-23 at 07:17 -0400, Robert Haas wrote: > I can reproduce this, here. The problem seems to be that plpython > only build either plpython2.so or plython3.so, but both languages > expect a call handler called plython_call_handler. So once we load > the shared library for one language, the other language just grabs the > same call handler. The problem is apparently that when CREATE LANGUAGE creates a language from a pg_pltemplate entry, it creates the proname from the tmplhandler name, and if it finds a fitting proname entry already, it used that one. So when you create plpython2 first and plpython3 second, the pg_language entries of the latter point to the pg_proc entries of the former. If you fix that up manually (create additional pg_proc entries and fix the pg_language entries to point there), it works better.
В списке pgsql-hackers по дате отправления: