Re: testing plpython3u on 9.0beta2
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Chris <rfusca@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-06-28T12:14:10Z
Lists: pgsql-hackers
On Fri, Jun 25, 2010 at 2:49 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On fre, 2010-06-25 at 10:17 -0400, Tom Lane wrote: >> 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 ... > > Right. What shall we do about the catversion? We should go ahead and apply this, either with (my vote) or without (Tom's vote) a catversion bump. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company