Re: pg_upgrade from 12 to 13 failes with plpython2
От | Adrian Klaver |
---|---|
Тема | Re: pg_upgrade from 12 to 13 failes with plpython2 |
Дата | |
Msg-id | f8fe260a-4518-5901-15b7-43f56b373d71@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
Re: pg_upgrade from 12 to 13 failes with plpython2 |
Список | pgsql-general |
On 11/17/20 2:17 PM, Devrim Gündüz wrote: > > Hi, > > On Tue, 2020-11-17 at 16:23 -0500, Tom Lane wrote: >> You're confusing what the source code can do (which is what the >> manual documents) versus what individual packagers choose to support. >> The packagers frequently don't have a lot of choice in the matter; >> once their platform drops python2, they can't support plpython2. > First let me say: 1) I don't use Python 2 anymore. 2) I have converted my plpython(2)u functions to plpythonu3u 3) I don't use RH family distros. > Well, CentOS 8 "supports" PY2, however given that Christoph also > dropped PY2 support in Debian packages as of PostgreSQL 12 [1], and > given that *Python 2 is unsupported* anyway, I just wanted to drop > support at this point. Read that sentence again and see the inherent disconnect between the beginning and end. As a packager you are in charge of how the packaging is done. Still announcing a change that effectively nullifies the documentation would to me be something that should be announced somewhere else than a list that I'm guessing 99% of the users don't read. > > FWIW, older PostgreSQL major versions still have PY 2 support. This is > for PostgreSQL 13 only. > > [1] : https://www.postgresql.org/message-id/20200522080114.GA449430%40msg.df7cb.de > > Regards, > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: