| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Magnus Hagander <magnus(at)hagander(dot)net>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade from 12 to 13 failes with plpython2 |
| Date: | 2020-11-18 19:13:22 |
| Message-ID: | 996837.1605726802@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
[ please don't top-post, it makes conversations unreadable ]
Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl> writes:
> so look at this:
> postgres=# drop extension plpython;
> ERROR: extension "plpython" does not exist
> postgres=# drop extension plpythonu;
> ERROR: extension "plpythonu" does not exist
> postgres=# drop extension plpython2u;
> ERROR: extension "plpython2u" does not exist
Well, the pg_upgrade failure clearly shows that you've got some
functions referencing plpython2. Maybe they're "loose" instead
of being bound into an extension --- that's quite possible if
this database has been brought forward from some pre-9.1 state.
Try looking in each database with
select * from pg_proc where probin like '%python2%';
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcin Giedz | 2020-11-18 19:42:16 | Re: pg_upgrade from 12 to 13 failes with plpython2 |
| Previous Message | Marcin Giedz | 2020-11-18 19:05:03 | Re: pg_upgrade from 12 to 13 failes with plpython2 |