EDB Unveils PGD 6.4 Enhancements for Distributed Postgres Deployments
EDB has introduced version 6.4 of its Postgres Distributed (PGD) solution, enhancing its capabilities for distributed Postgres deployments. This latest update features quorum commit, native connection pooling, and support for PostgreSQL large objects, marking a significant advancement in the management of distributed databases.
At the heart of this update is the quorum commit feature, which EDB describes as a mechanism that ensures a unified transaction outcome across cluster nodes before a transaction is finalized locally. This capability is particularly crucial for systems where conflicting writes across different locations could pose financial or operational risks.
EDB is specifically targeting organizations that operate critical workloads in sectors such as banking, payments, telecommunications, and infrastructure. In these environments, maintaining distributed consistency is often paramount. Traditionally, operators have relied on proprietary database solutions to achieve the highest levels of transaction guarantees.
Jozef de Vries, Senior Vice President of Database Engineering at EDB, emphasized that this launch fills a significant gap for Postgres users. He stated, “Postgres has become the de facto standard for modern applications. Yet until now, organizations running high-value workloads in banking, payments, or telecom were forced to fall back on legacy enterprise RDBMS for their strongest consistency requirements. PGD 6.4 changes that, delivering the same distributed consistency those systems were built on, now fully Postgres native.”
Quorum commit operates as a pre-commit coordination step across the cluster. Unlike traditional methods that merely confirm a replica has received a record, this new feature coordinates concurrent writes across various sites before a transaction is completed. For instance, in a payments scenario involving a shared credit card used simultaneously in different regions, conventional replication could allow two transactions to pass local checks and commit independently, leading to potential overspending. With quorum commit, one transaction will achieve cluster consensus first, while the other transaction will be rejected upon seeing the updated balance.
Pooling Built In
In addition to quorum commit, PGD 6.4 enhances the previously introduced Connection Manager with native connection pooling. This advancement eliminates the need for external connection poolers, such as pgBouncer, in many production environments.
The Connection Manager is integrated with PGD’s Raft consensus layer, enabling it to route traffic while being aware of both cluster and regional states. It can automatically adjust routes during failover events and provide monitoring through PostgreSQL logging and monitoring views. This integration aims to streamline operations by reducing the number of components involved in large deployments.
This feature is particularly beneficial for organizations managing numerous clusters, as each additional component can complicate deployment, maintenance, and monitoring efforts. EDB noted that payment processors and other operators overseeing infrastructure across thousands of CPU cores can simplify their operations by utilizing this built-in layer instead of relying on a separate proxy tier.
Broader Workloads
The release also expands replication support to include PostgreSQL large objects, which are essential for storing binary data. This enhancement broadens the applicability of distributed Postgres to workloads that involve scanned documents, image archives, and binary payloads, as well as applications that integrate transactional data with unstructured content within the same database.
This capability could significantly enhance the relevance of distributed Postgres in sectors that manage mixed data sets alongside core records, such as government, healthcare, and financial services. In these contexts, the ability to store binary objects alongside transaction tables and customer records is vital, particularly when systems are distributed across multiple locations.
As data sovereignty continues to be a pressing concern for many organizations, EDB highlighted a Gartner forecast indicating that by 2030, over 75% of enterprises in Europe and the Middle East will have repatriated workloads to their home jurisdictions, a significant increase from less than 5% in 2025. This trend has intensified scrutiny over not only where data is stored but also how consistently it is managed across borders and locations.
For database vendors, the opportunity lies in providing open-source-based systems that can address governance and resilience demands without necessitating a return to proprietary platforms. EDB aims to solidify Postgres’s position in this market segment by focusing on transaction integrity in distributed environments while minimizing reliance on surrounding infrastructure components.
