| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ömer Güven <omer(dot)guven(at)zuplu(dot)com> |
| Cc: | Rei Monsura <rmonsura(at)opentext(dot)com>, rob stone <floriparob(at)tpg(dot)com(dot)au>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [EXTERNAL] - Re: FW: Compatibility Confirmation – PostgreSQL 11 and Windows Server 2019 |
| Date: | 2026-10-28 13:47:43 |
| Message-ID: | 1493607.1793195263@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?utf-8?Q?=C3=96mer_G=C3=BCven?= <omer(dot)guven(at)zuplu(dot)com> writes:
> I understand the client’s constraints, but deploying PostgreSQL 11 into a new production environment in late 2026 is frankly astonishing.
> PostgreSQL 11 reached end-of-life in November 2023. That’s nearly three years without security updates, with at least another year planned. Whether it runs on Windows Server 2019 is hardly the most pressing concern.
I was thinking of responding along those same lines, so thanks for
saving me the time. I'd just add one more point: there's also
three years' worth of not-then-known data loss bugs that will never
be fixed in PG 11. Since the point of using a database is normally
that you trust it to store your data, that's an independent reason
that this project is just irresponsible as-defined.
If you have doubts about whether any of these concerns apply to you,
I'd suggest trawling the cumulative release notes at
https://www.postgresql.org/docs/release/
It's a pretty good bet that anything that was fixed in the
oldest-then-supported-branch since November 2023 is probably
an issue for v11 as well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-10-28 21:07:33 | Re: Compatibility Confirmation – PostgreSQL 11 and Windows Server 2019 |
| Previous Message | Ömer Güven | 2026-10-28 09:58:26 | Re: [EXTERNAL] - Re: FW: Compatibility Confirmation – PostgreSQL 11 and Windows Server 2019 |