From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrade Python version issue on openSUSE |
Date: | 2020-09-26 14:07:32 |
Message-ID: | 1990004.1601129252@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?utf-8?Q?Paul_F=C3=B6rster?= <paul(dot)foerster(at)gmail(dot)com> writes:
> seems, I found some kind of solution:
> - before running "pg_upgrade --check -k":
> drop extension plpythonu;
> - run pg_upgrade
> - after the upgrade:
> create extension plpython3u;
> Is this the correct way?
If you had plpythonu installed before, that's a plausible thing
to do. (There was discussion some time ago about making the
python-2-to-3 transition less painful for users, but we failed
to come to any consensus about how; so manual fixes like this
are going to be needed for a lot of people.)
However, I don't understand how "drop extension plpythonu"
worked for you, given your previous query showing that
that extension wasn't installed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-09-26 14:11:10 | Re: PG 13 trusted extensions and pg_available_extensions |
Previous Message | Paul Förster | 2020-09-26 10:58:51 | Re: pg_upgrade Python version issue on openSUSE |