| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Subject: | Re: What's our minimum supported Python version? |
| Date: | 2025-04-24 11:16:07 |
| Message-ID: | CAGECzQRvxmRD+7cqU8akw+AQ_3j2PfSH1Xrnz5QL+OosVQXH8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 24 Apr 2025 at 10:54, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> The cut-off in practice for these things is usually RHEL. PG18
> currently still supports RHEL 7, which appears to come with Python 3.6.
> Seeing that the small problem with the test script was easily fixed, I
> think we should stick with that for now. There might be value in
> dropping support for RHEL 7 sometime, but that should be done across the
> board (meson version, openssl version, perl version, etc.), and requires
> some buildfarm changes, so I wouldn't do this right now.
RHEL7 is not supported by Devrim for PG16 and PG17 already[1]. Did you
mean something different with "PG18 currently still supports RHEL 7"?
[1]: https://yum.postgresql.org/news/rhel7-postgresql-rpms-end-of-life/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2025-04-24 11:20:52 | Re: [PATCH] dynahash: add memory allocation failure check |
| Previous Message | Christoph Berg | 2025-04-24 10:53:30 | Re: sslmode=secure by default (Re: Making sslrootcert=system work on Windows psql) |