| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Subject: | Re: PG20 Minimum Dependency Thread |
| Date: | 2026-07-09 18:07:46 |
| Message-ID: | 2769389.1783620466@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> I told Daniel a while back that I thought 3.0 was likely to be the
> "new 1.0.2" (i.e. distros will keep it alive for *way* too long), but
> I also didn't anticipate RHEL jumping to 3.5 in the middle of a
> release line. So maybe Debian and Ubuntu will surprise me too?
> Post-quantum stuff has an awful lot of momentum building, it seems.
I think that Red Hat have shifted their stance a bit about what
compatibility is expected in an LTS distro. Perhaps this change
for openssl was driven mostly by the need to get on board with PQ.
But it's also the case that they've gotten a lot more eager to update
clang/llvm than they were in days of yore: RHEL 9 and 10 are both on
clang 21.1.8, which is the same compiler release I see in current
Fedora 43, and is most certainly not what they shipped with
originally. (I've not dug too deeply into why; there may be options
I've not selected that would restrict what "dnf update" will do by
default.) There are probably other examples, but those are what
I've noticed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Masahiko Sawada | 2026-07-09 17:41:38 | Re: Per-table resync for logical replication subscriptions |