EDB Postgres Distributed 5.1.0 release notes v5
Released: 16 May 2023
EDB Postgres Distributed version 5.1.0 is a minor version of EDB Postgres Distributed. This version addresses security vulnerabilities in dependencies for PGD Proxy and PGD CLI.
Synchronous Commit is now available in PGD’s unified COMMIT SCOPE syntax. Modeled on Postgres’s legacy synchronous commit option, PGD Synchronous Commit allows DBAs to take advantage of the finer-grained commit and sync management. This addition complements the existing Group Commit, CAMO, and Lag Control commit scope options.
Fixes to priority-based proxy routing now enable better handling of failover. You can now configure the grace period for proxies through PGD CLI, allowing you to tune proxy response to losing the Raft leader. To accompany that, Raft events are visible in the PGD CLI’s
show-eventscommand, showing the event, source, and subtype.
bdr.drop_node_group()adds support for removing empty node groups using the PGD SQL interface.
We recommend that users of PGD 5.0 upgrade to PGD 5.1.
PostgreSQL version compatibility
This version is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later.
|BDR||5.1.0||Feature||Added pid to the log message emitted upon writer process death.|
|BDR||5.1.0||Feature||Added group name in the bdr.event_summary view.|
|BDR||5.1.0||Feature||Added SLES support. SLES 15sp4 is now supported.|
|BDR||5.1.0||Feature||Added subscription status column to the group subscription summary view.|
This feature allows you to distinguish whether NULL values are due to a node being down or a subscription being disabled.
|BDR||5.1.0||Feature||Added NOT group filter to Group Commit.|
This feature allows you to invert the meaning of a group filter to include all nodes except the ones in specified groups.
You can now drop empty node groups.
|BDR||5.1.0||Feature||Added SYNCHRONOUS_COMMIT to commit scopes.|
This feature allows dynamic synchronous_commit-like behavior for replication.
|BDR||5.1.0||Feature||Added event_node_name column to |
|BDR||5.1.0||Feature||Added write leader election to event history.|
Added information about the node that's elected as a write leader for each group in the event_history catalog. Also improved the reporting of raft instance ids in the event_detail of event_history.
|BDR||5.1.0||Feature||Added ability to allow exporting and importing of other Raft instance snapshots.|
This feature allows exporting and importing snapshots for other instances and not only top Raft instances.
|BDR||5.1.0||Bug fix||Fixed memory leak in consensus process. (RT91830)|
|BDR||5.1.0||Bug fix||Fixed issue where a node can be inconsistent with the group after rejoining.|
If a node was part of a subgroup, parted, and then rejoined to the group, it could be inconsistent with the group. The changes from some nodes of the group were replayed from a wrong starting point, resulting in potential data loss.
|BDR||5.1.0||Bug fix||Fixed join and replication when SDW and standby_slot_names are set. (RT89702, RT89536)|
|BDR||5.1.0||Bug fix||Fixed spurious warnings when processing sequence options. (RT90668)|
|BDR||5.1.0||Bug fix||Fixed upgrades for nodes with CRDTs.|
|BDR||5.1.0||Bug fix||Adjusted lag tracking parameters for LCRs from pg_stat_replication.|
|BDR||5.1.0||Bug fix||Adjusted node routing options defaults based on node kind.|
This change is related only to the display of the information and not the behavior. For example, witness nodes aren't marked as candidates for receiving writes.
|BDR||5.1.0||Bug fix||All sequences are now converted to "distributed" during create node.|
|BDR||5.1.0||Bug fix||Fixed streaming transactions with |
This might have led to a subscriber-only node getting ahead of a data node.
|BDR||5.1.0||Bug fix||Made priority work properly for routing selection.|
Previously, node priority was working only if there wasn't a previous leader, which is never the case on failover.
|BDR||5.1.0||Bug fix||Fixed the recording of its join as complete for the first node.|
|BDR||5.1.0||Bug fix||Disabled tracing by default.|
Tracing was enabled only for initial debugging and was meant to be disabled before 5.0 release.
|BDR||5.1.0||Bug fix||Added support for reload configuration for the pglogical receiver.|
When the server receives a reload signal, the pglogical receiver reloads and applies the configuration changes.
|BDR||5.1.0||Bug fix||Improved missing instance error message in |
|BDR||5.1.0||Bug fix||Implemented consistent use of tcp keepalives across all BDR connections.|
This change added the following GUCs:
The defaults are set to fairly conservative values and are subject to adjustments in the future patches.
|BDR||5.1.0||Bug fix||Closed Raft connections on no activity after a timeout.|
This uses wal_sender_timeout/wal_receiver_timeout underneath.
|BDR||5.1.0||Bug fix||Made backends that receive Raft messages easily identifiable.|
Added information in the log message related to Raft backends.
|BDR||5.1.0||Bug fix||Fixed issue whereby Parallel Apply might slow down under heavy load.|
|BDR||5.1.0||Enhancement||Restarting sync workers is now avoided.|
This fix is to prevent the node join from failing when config changes are made that signal the restart of subscription workers.
|PGD Proxy||5.1.0||Enhancement||Implemented the new |
|PGD Proxy||5.1.0||Bug fix||Changed from blocking when write leader is unavailable to closing the new client connections.|
|CLI||5.1.0||Enhancement||Enhanced the |
|CLI||5.1.0||Enhancement||Improved clockskew estimation in |
|CLI||5.1.0||Feature||Added support to view and set |
|Utilities||1.1.0||Bug fix||Implemented handling of uninitialized physical replication slots issue.|
- On this page
- Highlights of EDB Postgres Distributed 5.1