On Fri, Jan 20, 2012 at 07:01:46AM +0200, Peter Eisentraut wrote:
> On tor, 2012-01-19 at 17:04 -0500, Bruce Momjian wrote:
> > For that reason, I wonder if I should just hard-code the plpython
> > rename into the pg_upgrade test in check_loadable_libraries().
>
> Yes, I haven't come up with a bet
On tor, 2012-01-19 at 17:04 -0500, Bruce Momjian wrote:
> For that reason, I wonder if I should just hard-code the plpython
> rename into the pg_upgrade test in check_loadable_libraries().
Yes, I haven't come up with a better solution either.
If this becomes a general problem, we might need to ad
On Thu, Dec 22, 2011 at 11:42:23AM -0500, Robert Haas wrote:
> On Mon, Dec 19, 2011 at 10:16 AM, Peter Eisentraut 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 l
On Mon, Dec 19, 2011 at 10:16 AM, Peter Eisentraut 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 loa
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. et
