Skip to content

For help, click the link below to get free database assistance or contact our experts for personalized support.

Percona Distribution for PostgreSQL 17.6.1 (2025-09-10)

Percona Distribution for PostgreSQL is a solution that includes PostgreSQL server and the collection of tools from PostgreSQL community. These tools are tested to work together and serve to assist you in deploying and managing PostgreSQL.

The aim of Percona Distribution for PostgreSQL is to address the operational issues like High-Availability, Disaster Recovery, Security, Observability, Spatial data handling, Performance and Scalability, and others that enterprises are facing.

This release of Percona Distribution for PostgreSQL is based on Percona Server for PostgreSQL 17.6.1 - a binary compatible, open source drop in replacement of PostgreSQL Community 17.6.

Release Highlights

SBOMs available for download

Percona now provides Software Bill of Materials (SBOMs) to support compliance and security audits. SBOM files are available for tarball builds.

See Software Bill of Materials (SBOMs) for the full list.

Tarball updates

The binary tarballs for x86_64 and ARM64 architectures have been updated in this release. The following libraries and components have new versions:

  • LIBXSLT: 1.1.43
  • LUA: 5.3.6
  • LIBTIFF: 4.7.0
  • EXPAT: 2.5.0
  • PGPOOL: 4.6.2
  • PGBACKREST: 2.56.0
  • PATRONI: 4.0.6

See Install Percona Distribution for PostgreSQL from binary tarballs for the download links.

Addressed CVEs

This release includes important security measures that address the following CVEs: CVE-2012-0868, CVE-2017-7484, and CVE-2025-8715. For more details, see the PostgreSQL 17.6 release notes.

Known Issue

For minor & major upgrades (RHEL only)

During an upgrade on RHEL, you may encounter the following error:

Unknown Error occurred: Transaction test error:
  file /usr/share/postgresql-common/server/postgresql.mk from install of percona-postgresql-common conflicts with file from package percona-postgresql-common-dev
  file /usr/share/postgresql-common/t/040_upgrade.t from install of percona-postgresql-common conflicts with file from package percona-postgresql-common-dev

To resolve this, remove the percona-postgresql-common-dev package and reinstall it with the new intended upgraded PPG/PSP server.

The following is the list of extensions available in Percona Distribution for PostgreSQL.

Extension Version Description
etcd 3.5.21 A distributed, reliable key-value store for setting up highly available Patroni clusters
python-etcd 0.4.5 A Python client library for interacting with etcd
HAProxy 2.8.15 A high-availability and load-balancing solution
Patroni 4.0.6 A HA (High Availability) solution for PostgreSQL
PgAudit 17.1 A detailed session or object audit logging via the standard logging facility provided by PostgreSQL
pgAudit set_user 4.1.0 Provides an additional layer of logging and control when unprivileged users must escalate roles for maintenance.
pgBackRest 2.56.0 A backup and restore solution for PostgreSQL
pgBadger 13.1 A fast PostgreSQL Log Analyzer
PgBouncer 1.24.1 A lightweight connection pooler for PostgreSQL
pg_gather v31 An SQL script for running the diagnostics of the health of a PostgreSQL cluster
pgpool2 4.6.2 A middleware between PostgreSQL server and client for high availability, connection pooling, and load balancing
pg_repack 1.5.2 Rebuilds PostgreSQL database objects
pgvector v0.8.0 A vector similarity search for PostgreSQL
PostGIS 3.3.8 A spatial extension for PostgreSQL
PostgreSQL Common 280 PostgreSQL database-cluster manager. Supports multiple PostgreSQL versions and clusters simultaneously
wal2json 2.6 A PostgreSQL logical decoding JSON output plugin

For Red Hat Enterprise Linux 8 and compatible derivatives, Percona Distribution for PostgreSQL also includes the supplemental python3-etcd 0.4.5 packages, which are used for setting up Patroni clusters.

Percona Distribution for PostgreSQL is also shipped with the libpq library. It contains “a set of library functions that allow client programs to pass queries to the PostgreSQL backend server and to receive the results of these queries.”