| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade with plpython is broken |
| Date: | 2011-12-22 16:42:23 |
| Message-ID: | CA+TgmoYp+7Bn41biE87O41r2G0zBSU8XKBe5nj9kF0WFLrWepQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 19, 2011 at 10:16 AM, Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-12-22 16:49:26 | Re: patch: bytea_agg |
| Previous Message | Robert Haas | 2011-12-22 16:41:32 | Re: [PATCH] Enable min/max optimization for bool_and/bool_or/every |