Re: testing plpython3u on 9.0beta2 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: testing plpython3u on 9.0beta2
Date
Msg-id 1835.1277475452@sss.pgh.pa.us
Whole thread Raw
In response to Re: testing plpython3u on 9.0beta2  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: testing plpython3u on 9.0beta2  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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 ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: pgsql: Add TCP keepalive support to libpq.
Next
From: Heikki Linnakangas
Date:
Subject: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes.