Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM40R-00000001pya-0mEw for pgsql-general@arkaria.postgresql.org; Wed, 28 Oct 2026 13:47:55 +0000 Received: from localhost ([127.0.0.1]:47226 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xM40Q-0000000Gl7M-1pWz for pgsql-general@arkaria.postgresql.org; Wed, 28 Oct 2026 13:47:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:41726) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM40L-0000000Gl6n-0IRM for pgsql-general@lists.postgresql.org; Wed, 28 Oct 2026 13:47:54 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM40I-00000001MyW-2bS4 for pgsql-general@lists.postgresql.org; Wed, 28 Oct 2026 13:47:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 69SDlhPZ1493608; Wed, 28 Oct 2026 09:47:43 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 sss.pgh.pa.us 69SDlhPZ1493608 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sss.pgh.pa.us; s=default; t=1793195265; bh=uh4ADVjj/ct+UsHUw7TiIWQQ/TquJqkWWvtjrNlPXnQ=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=00Uk2Asc1n8ekeRgQR13cU9f/7pWq4P0CpXEr/bNG1jEAq4QwXp01rfdJMT+ThAVP 7D0/PLudDhhwiMQ+XlFhIVlJ8x3rnip6yVfXT5TjGybUkqBhbozfG2W7f3zgoa4he1 /VTNq6/qsuUx/b6db6Z6bl0QKZaS12IgV5QI3dT8= From: Tom Lane To: =?utf-8?Q?=C3=96mer_G=C3=BCven?= cc: Rei Monsura , rob stone , pgsql-general@lists.postgresql.org Subject: =?UTF-8?Q?Re:_[EXTERNAL]_-_Re:_FW:_Compatibility_Confirmation_?= =?UTF-8?Q?=E2=80=93_PostgreSQL_11_and_Windows_Server_2019?= In-reply-to: <9E8391D5-40E9-4CA3-AE8D-83927BEB0BA0@zuplu.com> References: <9E8391D5-40E9-4CA3-AE8D-83927BEB0BA0@zuplu.com> Comments: In-reply-to =?utf-8?Q?=C3=96mer_G=C3=BCven?= message dated "Wed, 28 Oct 2026 10:58:26 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1493606.1793195263.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Oct 2026 09:47:43 -0400 Message-ID: <1493607.1793195263@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =3D?utf-8?Q?=3DC3=3D96mer_G=3DC3=3DBCven?=3D writes= : > I understand the client=E2=80=99s 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=E2=80=99s nearl= y three years without security updates, with at least another year planned= . Whether it runs on Windows Server 2019 is hardly the most pressing conce= rn. 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