| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris <rfusca(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: testing plpython3u on 9.0beta2 |
| Date: | 2010-06-28 12:14:10 |
| Message-ID: | AANLkTimdJe8q3y_6i-EFMAeV7oFN6CSa4LvPAuyAlTmo@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 25, 2010 at 2:49 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> 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?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-28 13:55:01 | Re: get_whatever_oid, part 1: object types with unqualifed names |
| Previous Message | Robert Haas | 2010-06-28 12:09:21 | Re: suppress automatic recovery after back crash |