Secure the future of MySQL. Sign this open letter

PostgreSQL minor release postponed in Q1’ 2026

In case you are awaiting the February PostgreSQL Community minor update released on plan on February 12 we want to make sure that our users and customers are up to date and aware of what to expect.

This scheduled PostgreSQL release was delivered by the PostgreSQL Community on time and came carrying 5 CVE fixes and over 65 bugs bug fixes.

Unfortunately shortly after, the release team announced that an additional out of cycle release is planned for February 26. This follow up release addresses two regressions identified in the February 12 update.

Because of this, we have decided not to ship a Percona Distribution for PostgreSQL build based on the February 12 release. Instead, we will wait for the February 26 Community update and base our release on that version once it becomes available from PGDG. This means also a delay in the release of Percona Operator for PostgreSQL that uses images based on our PostgreSQL releases.

Always look on the bright side

 

While this is a delay in release it comes with some benefits. For our users and customers, this means a cleaner upgrade path. Rather than releasing February 12 now and asking you to update again shortly after, we prefer to wait and deliver a single update that includes the fixes. Our goal is to make updates predictable and smooth for users of Percona Distribution for PostgreSQL, as well as extensions such as pg_tde and pg_stat_monitor. It should also allow you to carry less operational burden with the added maintenance that an extra update would require.

We appreciate how quickly the PostgreSQL Community identified and addressed the regressions. Open collaboration across the ecosystem, including reports and testing from many contributors, helps ensure PostgreSQL continues to improve for everyone.

Path forward

This is the third out of cycle release in the past year, following similar updates in November 2024 and February 2025. It highlights how responsive and diligent the PostgreSQL Community is when issues are identified. At the same time, it reminds us all how important continuous testing and collaboration are as PostgreSQL adoption continues to grow. Contributing to PostgreSQL, whether through testing, reporting, or development, is one of the best ways to help strengthen quality across the ecosystem.

Elephants keep ears open

As soon as the February 26 release is available and our builds are ready, we will share the update.

If you need to move forward with the February 12 version in the meantime, please reach out. We are happy to talk through your situation and help you assess what makes the most sense for your environment.

Our customers can contact us through Percona Support Services to receive the high quality assistance we are known for. We also encourage community users to reach out via the Percona Community Forums, where we will do our best to provide guidance based on the information you share.

Thank you for your trust and for being part of the Percona community.

Jan Wieremjewicz

Jan is a Senior Product Manager at Percona, leading the products for PostgreSQL. He has vast experience in the development, deployment and maintenance of enterprise systems.

Professionally, he is passionate about simple solutions that solve complicated problems and user experience that maximizes the product potential.

Privately he is a foodie by day, a tech geek into graphic novels, video and board games by night and parent/spouse in between.

Having spent already almost three years in Percona, most of us learned that he has enough energy and topics to fill in any space and time.

See all posts by Jan Wieremjewicz »

Discussion

We invite you to our forum for discussion. You are welcome to use the widget below.

✎ Edit this page on GitHub