Re: testing plpython3u on 9.0beta2
Peter Eisentraut <peter_e@gmx.net>
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Chris <rfusca@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-06-25T18:49:23Z
Lists: pgsql-hackers
Attachments
- plpython3-handler-name.patch (text/x-patch) patch
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?