From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_upgrade from 12 to 13 failes with plpython2 |
Date: | 2020-11-17 22:17:40 |
Message-ID: | f722e1f93c75c17826460951e596baeb0d4a4e0c.camel@gunduz.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
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.
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,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
From | Date | Subject | |
---|---|---|---|
Next Message | George Sexton | 2020-11-17 22:18:45 | Postgres on Kubernetes/VMware |
Previous Message | Post Gresql | 2020-11-17 22:12:45 | create type with %type or %rowtype |