From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Chris <rfusca(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: testing plpython3u on 9.0beta2 |
Date: | 2010-06-25 18:49:23 |
Message-ID: | 1277491763.5356.4.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On fre, 2010-06-25 at 10:17 -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > 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.
>
> The fix ought to be to change the function nmes used by plpython3 ...
Right. What shall we do about the catversion?
Attachment | Content-Type | Size |
---|---|---|
plpython3-handler-name.patch | text/x-patch | 1.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-25 19:07:16 | Re: testing plpython3u on 9.0beta2 |
Previous Message | Pavel Baros | 2010-06-25 18:24:32 | Re: GSoC - code of implementation of materialized views |