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.94.2) (envelope-from ) id 1um6FQ-009vvk-5L for pgsql-announce@arkaria.postgresql.org; Wed, 13 Aug 2025 07:50:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1um6FO-00DA0A-EO for pgsql-announce@arkaria.postgresql.org; Wed, 13 Aug 2025 07:50:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um6FN-00DA01-JV for pgsql-announce@lists.postgresql.org; Wed, 13 Aug 2025 07:50:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1um6FK-000UnF-1E for pgsql-announce@lists.postgresql.org; Wed, 13 Aug 2025 07:50:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=LpWqFFqWqkRfhIs27iUtj56WTtqoxaUJx2PNQf6jXxg=; b=wOBTO+baSiqmDS23/U2Ava8ibr YF38MvZ+YxiwbBNJ4haxwSjqBKdcghLPXUjv6QUCskzVgHeiWuqBka5Ps1/XFbmt1LGiQMDNJFUO9 LY8UE4jHIYGo43uhXfeoNPc3U+9LIj/44kC7V0tSCd3UoAVIm/A8H2ICurVX5cyEzojPPJx2X8+Zh GY+PQIExp636aZmVprf0M1iR8bTrsqn5XWzaccSSAoTahxwGvAFk8oa2nxq5k5K8cSrDocNhsjGk/ 9uTII7ek8M3dD3YiDiBq1UcIwFZ08aIwycSCnUz6A/kUCiw+Jhx/KsQaGndgK8qs5B3bdjSMhYBjS szMB0amA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um6FI-000tWn-1Z for pgsql-announce@lists.postgresql.org; Wed, 13 Aug 2025 07:50:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1um6FH-001tKn-0Q for pgsql-announce@lists.postgresql.org; Wed, 13 Aug 2025 07:50:03 +0000 Content-Type: multipart/mixed; boundary="===============1630934097815945004==" MIME-Version: 1.0 Subject: CloudNativePG 1.27.0 Released! To: PostgreSQL Announce From: The CloudNativePG Contributors via PostgreSQL Announce Reply-To: gabriele.bartolini@gmail.com Date: Wed, 13 Aug 2025 07:49:14 +0000 Message-ID: <175507135466.283154.14293583847675293233@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: c249131a8b0015e80e046f5173c8a896d444572ed186b5bfdf84a17461c368d2 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============1630934097815945004== Content-Type: multipart/alternative; boundary="===============7999860130303930165==" MIME-Version: 1.0 --===============7999860130303930165== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The **CloudNativePG Community** is excited to announce the release of **CloudNativePG 1.27.0**, bringing powerful new features, stability improvements, and extended capabilities for running PostgreSQL in Kubernete= s. ## Highlights in 1.27.0 ### Dynamic Loading of PostgreSQL Extensions You can now use the new `.spec.postgresql.extensions` field to mount Postgr= eSQL extensions=E2=80=94packaged as OCI-compliant container images=E2=80=94as **= read-only, immutable volumes** in instance pods. This enables [dynamic extension management](/documentation/1.27/imagevolume= _extensions/) without rebuilding base images, offering faster, more flexible extension deployments. ### Logical Decoding Slot Synchronization A new `synchronizeLogicalDecoding` option under `spec.replicationSlots.highAvailability` introduces [automatic synchronization of logical decoding slots](/documentation/1.27/r= eplication/#logical-decoding-slot-synchronization) across high-availability clusters. This ensures that logical replication subscribers can continue seamlessly after a publisher failover, **improving reliability and integration with Change Data Capture (CDC) tools**. ### Primary Isolation Check =E2=80=94 Now Stable The **liveness pinger**, introduced experimentally in 1.26, is now a stable feature. With `.spec.probes.liveness.isolationCheck` enabled by default, t= he liveness probe now performs [primary isolation checks](/documentation/1.27/instance_manager/#primary-is= olation) to improve detection and handling of primary connectivity issues in Kuberne= tes environments. ## Other Enhancements This release also includes: - **Quorum-based failover** *(experimental)* =E2=80=94 an opt-in feature th= at improves safety and data durability during failover events through synchronous rep= lication. [Learn more](/documentation/1.27/failover/#failover-quorum-quorum-based-f= ailover). - **User maps for predefined users** =E2=80=94 including `streaming_replica= `, enabling the use of self-managed client certificates with different Common Names in environments with strict security policies or shared certificate authorit= ies. - **Improved plugin failure observability** =E2=80=94 with a new `PhaseFail= urePlugin` phase in `Cluster status` to better track plugin-related errors. Full details are available in the [release notes](https://cloudnative-pg.io/documentation/1.27/release_notes/= v1.27/). ## Upgrade Guidance We recommend upgrading to **1.27.0** to benefit from the latest features, enhancements, and long-term stability. If you=E2=80=99re on **1.26.x**, upgrade to **1.26.1** to get the latest fi= xes in that series. Support for the **1.25.x** series ends on **22 August 2025** =E2=80=94 plan= your migration to 1.27 or 1.26 soon. Follow the [upgrade instructions](https://cloudnative-pg.io/documentation/1= .27/installation_upgrade/#upgrades) for a smooth transition. ## Get Involved with the Community [Join us](https://github.com/cloudnative-pg/cloudnative-pg?tab=3Dreadme-ov-= file#communications) to help shape the future of cloud-native Postgres! If you're using CloudNativePG in production, consider [adding your organization as an adopter](https://github.com/cloudnative-pg/= cloudnative-pg/blob/main/ADOPTERS.md) to support the project's growth and evolution. Thank you for your continued support! Upgrade today and discover how CloudNativePG can elevate your PostgreSQL experience to new heights. ## About CloudNativePG [CloudNativePG](https://cloudnative-pg.io) is an open-source Kubernetes Operator specifically designed for PostgreSQL workloads. It manages the ent= ire lifecycle of a PostgreSQL cluster, including bootstrapping, configuration, = high availability, connection routing, and comprehensive backup and disaster recovery mechanisms. By leveraging PostgreSQL's native streaming replicatio= n, CloudNativePG efficiently distributes data across pods, nodes, and zones us= ing standard Kubernetes patterns, enabling seamless scaling of replicas in a Kubernetes-native manner. Originally developed and supported by [EDB](https://www.enterprisedb.com/), CloudNativePG is a CNCF Sandbox proje= ct and the sole PostgreSQL operator in this category. --===============7999860130303930165== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable CloudNativePG 1.27.0 Released!
 

CloudNativePG 1.27.0 Released!

The CloudNativePG Community is excited to announce the release of CloudNativePG 1.27.0, bringing powerful new features, stab= ility improvements, and extended capabilities for running PostgreSQL in Kubernete= s.

Highlights in 1.27.0

Dynamic Loading of PostgreSQL E= xtensions

You can now use the new .spec.postgre= sql.extensions field to mount PostgreSQL extensions=E2=80=94packaged as OCI-compliant container images=E2=80=94as read-only, immutable volumes in instance pods. This enables dynami= c extension management without rebuilding base images, offering faster, more flexible extension deployments.

Logical Decoding Slot Synchroni= zation

A new synchronizeLogicalDecoding option under spec.replicationSlots.highAvailability introduces automatic synchroni= zation of logical decoding slots across high-availability clusters. This ensures that logical replication subscribers can continue seamlessly after a publisher failover, imp= roving reliability and integration with Change Data Capture (CDC) tools.<= /p>

Primary Isolation Check =E2=80= =94 Now Stable

The liveness pinger, intro= duced experimentally in 1.26, is now a stable feature. With .spec.probes.liveness.isolationCheck enabled by= default, the liveness probe now performs primary isolation c= hecks to improve detection and handling of primary connectivity issues in Kuberne= tes environments.

Other Enhancements

This release also includes:

  • Quorum-= based failover (experimental) =E2=80=94 an opt-in feature= that improves safety and data durability during failover events through synchronous rep= lication. Learn more.
  • User ma= ps for predefined users =E2=80=94 including streaming_replic= a, enabling the use of self-managed client certificates with different Common Names in environments with strict security policies or shared certificate authorit= ies.
  • Improve= d plugin failure observability =E2=80=94 with a new PhaseFai= lurePlugin phase in Cluster status to better track plugin-related error= s.

Full details are available in the release notes.<= /p>

Upgrade Guidance

We recommend upgrading to 1.27.0 to benefit from the latest features, enhancements, and long-term stability.

If you=E2=80=99re on 1.26.x, upgrade to 1.26.1 to get the latest fixes in that serie= s.

Support for the 1.25.x ser= ies ends on 22 August 2025 =E2=80=94 plan your migration to 1.27 or 1.26 soon.

Follow the upgrade instructions for a smooth transition.

Get Involved with the Community=

Join us to help shape the future of cloud-native Postgres!

If you're using CloudNativePG in production= , consider adding your or= ganization as an adopter to support the project's growth and evolution.

Thank you for your continued support! Upgra= de today and discover how CloudNativePG can elevate your PostgreSQL experience to new heights.

About CloudNativePG

CloudNativePG is an ope= n-source Kubernetes Operator specifically designed for PostgreSQL workloads. It manages the ent= ire lifecycle of a PostgreSQL cluster, including bootstrapping, configuration, = high availability, connection routing, and comprehensive backup and disaster recovery mechanisms. By leveraging PostgreSQL's native streaming replicatio= n, CloudNativePG efficiently distributes data across pods, nodes, and zones us= ing standard Kubernetes patterns, enabling seamless scaling of replicas in a Kubernetes-native manner. Originally developed and supported by EDB, CloudNativePG is a CNCF Sandbox project and the sole PostgreSQL operator in this category.
This email was sent to you from The CloudNativePG Contributors. It was deli= vered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to The CloudNativePG Contributors.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============7999860130303930165==-- --===============1630934097815945004==--