Re: BUG #6532: pg_upgrade fails on Python stored procedures

From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6532: pg_upgrade fails on Python stored procedures
Date: 2012-03-15 14:18:36
Message-ID: CADmi=6P7A43Bv6ErGAD_g2B5jKA9iwzoB0XRiY68aYrcg+p_bw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, Mar 15, 2012 at 9:01 PM, Stuart Bishop <stuart(at)stuartbishop(dot)net> wrote:

> Yes, it is there. I can see the library with the new name of
> plpython2.so, not the old plpython.so from 8.4. createlang installs
> the language just fine if I build a cluster and database myself.

As expected, symlinking plpython2.so to plpython.so works around
things. I have no idea if this work around will cause problems when
upgrading the db to PG 9.2+.

--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message vozhdb 2012-03-15 14:33:35 BUG #6533: postgre server crashes by create function (create table as)
Previous Message Stuart Bishop 2012-03-15 14:01:10 Re: BUG #6532: pg_upgrade fails on Python stored procedures

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-03-15 14:23:43 Re: CREATE FOREGIN TABLE LACUNA
Previous Message Tom Lane 2012-03-15 14:17:49 Re: libpq should have functions for escaping data for use in COPY FROM