Re: pg_upgrade from 12 to 13 failes with plpython2

Поиск
Список
Период
Сортировка
От Marcin Giedz
Тема Re: pg_upgrade from 12 to 13 failes with plpython2
Дата
Msg-id 1372359469.1497249.1605728536470.JavaMail.zimbra@arise.pl
обсуждение исходный текст
Ответ на Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general

[ please don't top-post, it makes conversations unreadable ]

Marcin Giedz <marcin.giedz@arise.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

--------------------------------------------------------------------------------------------------------------------------------

sorry for top-posting not a day-to-day habits in our env ;)

anyway got this from your query:


  oid  |         proname         | pronamespace | proowner | prolang | procost | prorows | provariadic | prosupport | prokind | prosecdef | proleakproof | proisstrict | proretset | provolatile | proparallel | pronargs | pronargdefaults | prorettype | proargtypes | proallargtypes | proargmodes | proargnames | proargdefaults | protrftypes |         prosrc          |      probin       | proconfig | proacl
-------+-------------------------+--------------+----------+---------+---------+---------+-------------+------------+---------+-----------+--------------+-------------+-----------+-------------+-------------+----------+-----------------+------------+-------------+----------------+-------------+-------------+----------------+-------------+-------------------------+-------------------+-----------+--------
 16402 | plpython_call_handler   |           11 |       10 |      13 |       1 |       0 |           0 | -          | f       | f         | f            | f           | f         | v           | u           |        0 |               0 |       2280 |             |                |             |             |                |             | plpython_call_handler   | $libdir/plpython2 |           |
 16403 | plpython_inline_handler |           11 |       10 |      13 |       1 |       0 |           0 | -          | f       | f         | f            | t           | f         | v           | u           |        1 |               0 |       2278 | 2281        |                |             |             |                |             | plpython_inline_handler | $libdir/plpython2 |           |
 16404 | plpython_validator      |           11 |       10 |      13 |       1 |       0 |           0 | -          | f       | f         | f            | t           | f         | v           | u           |        1 |               0 |       2278 | 26          |                |             |             |                |             | plpython_validator      | $libdir/plpython2 |           |
(3 rows)

(END)

sounds nothing for me I'm afraid but I hope gives a hint for you ;)


Many thx
M.



В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pg_upgrade from 12 to 13 failes with plpython2
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_upgrade from 12 to 13 failes with plpython2