On Mon, Jan 11, 2016 at 06:23:06PM -0500, Tom Lane wrote:
> Date: Mon, 11 Jan 2016 18:23:06 -0500
> From: Tom Lane
> To: Paul Jones
> cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] 9.4 -> 9.5 upgrade problem when both python2 and
> python3 present
>
>
>
Paul Jones writes:
> On Mon, Jan 11, 2016 at 10:04:16AM -0500, Tom Lane wrote:
>> It looks like pg_upgrade tries to load all libraries from functions in
>> any database in the old cluster into a single session in the new cluster,
>> which will fail in a scenario like this even if you keep python2
On Mon, Jan 11, 2016 at 10:04:16AM -0500, Tom Lane wrote:
/tmp/mutt-mayon-1000-19386-284b6a00794950f414
> Paul Jones writes:
> > pg_upgrade complains about not being able to find $libdir/plpython3
> > when upgrading a 9.4 cluster that has both python2 and python3 used.
>
> No, that's not what th
Paul Jones writes:
> pg_upgrade complains about not being able to find $libdir/plpython3
> when upgrading a 9.4 cluster that has both python2 and python3 used.
No, that's not what the error message says:
> Could not load library "$libdir/plpython3"
> FATAL: Python major version mismatch in sess
pg_upgrade complains about not being able to find $libdir/plpython3
when upgrading a 9.4 cluster that has both python2 and python3 used.
Both the 9.4 and 9.5 PGs have been built from source with python2/3 in
the recommended way and the plpython3.so is present in /usr/local/pgsql/lib.
I dropped the
