Re: PG20 Minimum Dependency Thread

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG20 Minimum Dependency Thread
Date: 2026-06-20 13:16:04
Message-ID: fa97726c-1180-4fd6-bf90-4757f91f490f@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18.06.26 22:01, Jacob Champion wrote:
> ...because I don't see one yet, and upcoming things like the Python
> test port are going to need clarity in advance, and I wanna stir up
> trouble right before I go eat lunch.
>
> = Background =
>
> The most recent (mailing list) discussions I am aware of are at
>
> [1] https://postgr.es/m/16098.1745079444%40sss.pgh.pa.us (Python)
> [2] https://postgr.es/m/42e13eb0-862a-441e-8d84-4f0fd5f6def0%40eisentraut.org
> (Meson)

Here is another relevant thread:

https://www.postgresql.org/message-id/flat/CA+hUKGL7trhWiJ4qxpksBztMMTWDyPnP1QN+Lq341V7QL775DA(at)mail(dot)gmail(dot)com

This is now "ready for committer" for PG20 and would de-support RHEL 7.

Another unrelated data point is that making PL/Python thread-safe (at
least in the way I have worked out) would require Python 3.10.

(But RHEL provides a supported way to install newer Python versions, so
this doesn't necessarily have to mean de-supporting a given RHEL version
altogether. I don't have an opinion on that at this time.)

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Fujii Masao 2026-06-20 12:43:59 Re: Fix publisher-side sequence permission reporting