EDB Postgres Distributed 5.0.0 release notes v5
Released: 21 Feb 2023
EDB Postgres Distributed version 5.0.0 is a is a new major version of EDB Postgres Distributed. This version brings major new features and compatibility changes.
The highlights of this release include:
- Flexible deployment architectures
- Enhanced routing capabilities
- Unified replication durability configuration
- Support for EDB Advanced Storage Pack
- Support for TDE with EDB Postgres Advanced 15 and EDB Postgres Extended 15
- Integration with OpenTelemetry
- Improved transaction tracking performance (Group Commit, CAMO)
- Postgres 12 to 15 compatiblity
|PGD||5.0.0||Feature||Flexible Deployment Architectures|
Redefined Always-ON to support wider variety of deployments.
|BDR||5.0.0||Feature||Enhanced routing capabilities|
BDR cluster elects a write leader for every group (and associated location) using per group Raft when routing is enabled for the group. It takes care of write leader failover and provides SQL commands to change a write leader.
|BDR||5.0.0||Feature||Support for EDB Advanced Storage Pack|
EDB Advanced Storage Pack provides advanced storage options for PostgreSQL databases in the form of table access method (TAM) extensions. These storage options can enhance the performance and reliability of databases without requiring application changes.
|BDR||5.0.0||Feature||Unified replication durability configuration|
The durability options such as Group Commit, CAMO, Eager Replication or Lag Control are now all configured through commit scope configuration.
|BDR||5.0.0||Feature||EDB Postgres Advanced and EDB Postgres Extended TDE support|
EDB Postgres Distributed 5 fully supports the Transparent Data Encryption feature in EDB Postgres Advanced and EDB Postgres Extended.
|BDR||5.0.0||Feature||Integration with OpenTelemetry|
BDR extension can now send monitoring metrics as well as traces to the OpenTelemetry collector for better integration with existing monitoring solutions.
|BDR||5.0.0||Feature||Postgres 15 compatibility|
EDB Postgres Distributed 5 is compatible with Postgres 12 to 15.
|BDR||5.0.0||Feature||Improved Cluster Event Management|
|BDR||5.0.0||Change||Improved transaction tracking performance|
Transaction tracking now uses shared memory instead of
|BDR||5.0.0||Feature||Support non-default replication sets with Decoding Worker|
Allows Decoding Worker feature to be used in clusters using non-default replication sets like asymmetric replication setup.
|BDR||5.0.0||Feature||Add support for HASH partitioning in Autopartition|
Extend autopartition/autoscale to support HASH partitioning. Many of things that are required for RANGE partitioning are not needed for HASH partitioning. For example, we expect to create all HASH partitions in one go (at least for the current work; later we may change this). We don't expect HASH partitions to be moved to a different tablespace or dropped. So data retention policies don't apply for HASH partitioning.
|BDR||5.0.0||Feature||Add a new benchmarking utility |
The utility supports benchmarking CAMO transactions and in future releases will be used for benchmarking PGD specific workloads.
|BDR||5.0.0||Change||Nodes now have a node kind|
This better differentiates different kinds of nodes such as data, witness, subscriber-only and standby.
|BDR||5.0.0||Change||Separate Task Management from Autopartition|
In this release, the autopartition work queue mechanism has been moved to a separate module called Task Manager (taskmgr). The task manager is responsible for creating new tasks and executing the ones created by the local node or the task manager leader node. The autopartition worker is thus renamed as taskmgr worker process in this release.
In the older PGD releases, the Raft leader was responsible for creating new work items. But that creates a problem because a witness node can become a Raft leader while it does not have the full view of the cluster objects. In this release, we have introduced a concept of Task Manager Leader node. The node is selected automatically by PGD, but for upgraded clusters, its important to set the
|Proxy||5.0.0||Feature||PGD built-in proxy|
A TCP layer 4, pass through proxy for PGD cluster using routing capabilities of BDR.
|CLI||5.0.0||Feature||PGD cluster verification |
CLI supports two new commands
|CLI||5.0.0||Feature||Proxy management and configuration|
|CLI||5.0.0||Change||Modify output of |