pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ömer Güven <omer.guven@zuplu.com>
Cc: Rei Monsura <rmonsura@opentext.com>
Cc: rob stone <floriparob@tpg.com.au>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: [EXTERNAL] - Re: FW: Compatibility Confirmation – PostgreSQL 11 and Windows Server 2019
Date: Wed, 28 Oct 2026 09:47:43 -0400
Message-ID: <1493607.1793195263@sss.pgh.pa.us> (raw)
In-Reply-To: <9E8391D5-40E9-4CA3-AE8D-83927BEB0BA0@zuplu.com>
References: <YT3PR01MB9409892F03DED2A48DC5E2F7B76F2@YT3PR01MB9409.CANPRD01.PROD.OUTLOOK.COM>
	<9E8391D5-40E9-4CA3-AE8D-83927BEB0BA0@zuplu.com>

=?utf-8?Q?=C3=96mer_G=C3=BCven?= <omer.guven@zuplu.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






view thread (4+ messages)

Message-ID: <1493607.1793195263@sss.pgh.pa.us>
Permalink:  ../1493607.1793195263@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1493607.1793195263@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, omer.guven@zuplu.com, rmonsura@opentext.com, floriparob@tpg.com.au
  Subject: Re: [EXTERNAL] - Re: FW: Compatibility Confirmation – PostgreSQL 11 and Windows Server 2019
  In-Reply-To: <1493607.1793195263@sss.pgh.pa.us>
  References: <YT3PR01MB9409892F03DED2A48DC5E2F7B76F2@YT3PR01MB9409.CANPRD01.PROD.OUTLOOK.COM> <9E8391D5-40E9-4CA3-AE8D-83927BEB0BA0@zuplu.com> <1493607.1793195263@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox