public inbox for [email protected]  

help / color / mirror / Atom feed

From: PostgreSQL Global Development Group <[email protected]>
To: PostgreSQL Announce <[email protected]>
Subject: Out-of-cycle release scheduled for February 20, 2025
Date: Fri, 14 Feb 2025 01:57:03 +0000
Message-ID: <[email protected]> (raw)

The [PostgreSQL](https://www.postgresql.org/) Global Development Group is planning for an out-of-cycle release on February 20, 2025 to address a regression that was released as part of the [February 13, 2025 update release](https://www.postgresql.org/about/news/postgresql-173-167-1511-1416-and-1319-released-3015/), which included release [17.3, 16.7, 15.11, 14.16, and 13.19](https://www.postgresql.org/about/news/postgresql-173-167-1511-1416-and-1319-released-3015/). As part of this release, we will issue fixes for all supported versions (17.4, 16.8, 15.12, 14.17, 13.20). While these fixes may not impact all PostgreSQL users, PostgreSQL Global Development Group determined that it would be better to address these sooner than the [next scheduled release on May 8, 2025](https://www.postgresql.org/developer/roadmap/).

The fix for [CVE-2025-1094](https://www.postgresql.org/support/security/CVE-2025-1094/), which closed a vulnerability in the [libpq](https://www.postgresql.org/docs/current/libpq.html) PostgreSQL client library, introduced a regression related to string handling for non-null terminated strings. The error would be visible based on how a PostgreSQL client implemented this behavior, and may not impact [all PostgreSQL drivers](https://wiki.postgresql.org/wiki/List_of_drivers). As a precaution, the PostgreSQL Global Development Group opted for a follow up release.

If you are impacted by this issue, we advise to consider waiting for the availability of 17.4, 16.8, 15.12, 14.17, and 13.29 before upgrading.

Attachments:

  [image/png] slonik.png (20.7K, 3-slonik.png)
  download | view image

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Out-of-cycle release scheduled for February 20, 2025
  In-Reply-To: <[email protected]>

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

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