Re: pg_upgrade with plpython is broken - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_upgrade with plpython is broken
Date
Msg-id CA+TgmoYp+7Bn41biE87O41r2G0zBSU8XKBe5nj9kF0WFLrWepQ@mail.gmail.com
Whole thread Raw
In response to pg_upgrade with plpython is broken  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: pg_upgrade with plpython is broken  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Mon, Dec 19, 2011 at 10:16 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> Upgrading an instance containing plpython from <=8.4 to >=9.0 is broken
> because the module plpython.so was renamed to plpython2.so, and so the
> pg_upgrade check for loadable libraries fails thus:
>
>    Your installation references loadable libraries that are missing from the
>    new installation.  etc.
>
> Installing a symlink fixes the issue.  Should we teach pg_upgrade about
> this renaming, or should we install the symlink as part of the standard
> installation?

I feel like this is a pg_upgrade bug, not so much a PL/python problem.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Enable min/max optimization for bool_and/bool_or/every
Next
From: Robert Haas
Date:
Subject: Re: patch: bytea_agg