Re: pg_upgrade from 12 to 13 failes with plpython2

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: pg_upgrade from 12 to 13 failes with plpython2
Дата
Msg-id 7820164d-5086-b3e2-e200-3f02f07b6280@aklaver.com
обсуждение исходный текст
Ответ на Re: pg_upgrade from 12 to 13 failes with plpython2  (Devrim Gündüz <devrim@gunduz.org>)
Ответы Re: pg_upgrade from 12 to 13 failes with plpython2  (Devrim Gündüz <devrim@gunduz.org>)
Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On 11/17/20 12:49 PM, Devrim Gündüz wrote:
> 
> Hi,
> 
> On Tue, 2020-11-17 at 12:18 -0800, Adrian Klaver wrote:
>> This was announced where and when?
> 
> https://www.postgresql.org/message-id/333f3aa334ba93019c75fffaec373f2bf4275d28.camel%40gunduz.org

So to be clear what was dropped was plpythonu, which means plpython2u. 
plpython3u still exists, correct?

It would be nice to mention this on --announce and here as this still 
exists:

https://www.postgresql.org/docs/13/plpython-python23.html

"

Existing users and users who are currently not interested in Python 3 
use the language name plpythonu and don't have to change anything for 
the foreseeable future. It is recommended to gradually “future-proof” 
the code via migration to Python 2.6/2.7 to simplify the eventual 
migration to Python 3.

In practice, many PL/Python functions will migrate to Python 3 with few 
or no changes.
"

> 
> Regards,
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



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

Предыдущее
От: Olivier Gautherot
Дата:
Сообщение: Re: autovacuum recommendations for Large tables
Следующее
От: Devrim Gündüz
Дата:
Сообщение: Re: pg_upgrade from 12 to 13 failes with plpython2