EDB Postgres Distributed 5.9.2 release notes v5.9.2

Enhanced the node group removal logic to automatically drop replication sets of the same name.

Enhanced how the Connection Manager matches database names and usernames against pg_hba.conf fields. Key improvements include support for sameuser matching, refined samerole logic, and expanded +rolename matching to include the role itself and indirect members. Additionally, quotes are now stripped from usernames before matching to ensure consistent authentication behavior.

This enhancement allows the Connection Manager to use pg_ident.conf for user name mapping. Currently, this functionality applies to the cert authentication method, aligning Connection Manager behavior with PostgreSQL’s native authentication identity mapping.

Patched internal libraries to address a security vulnerability (CVE-2026-4427). Although the vulnerability does not directly expose the PGD Proxy, a malicious or compromised PostgreSQL server could send a crafted DataRow message to crash the PGD Proxy, resulting in a denial-of-service (DoS) attack.

Resolved an issue where logical replication would enter an infinite crash loop if a DETACH PARTITION CONCURRENTLY command was interrupted. Previously, the walsender would fail with the error relation has no parent because it's being detached when decoding WAL for a partition in a detach-pending state.

Fixed an issue where the walsender process could enter a crash loop when encountering partitions with inhdetachpending = true, which reported ERROR: relation %u has no parent failures.

Fixed an issue where replication would break because attributes like NOSUPERUSER or NOREPLICATION were automatically added to the replicated command. Since these options can only be altered by a superuser, the apply process failed on downstream nodes. This change ensures the replicated command only includes options that were explicitly specified and for which the user has sufficient privileges.

Table and index locks are now held until transaction commit when applying changes. This ensures correct serialization and prevents data consistency issues during concurrent operations, specifically addressing risks introduced by parallel apply.

Resolved an issue where enabling Parallel Apply on community PostgreSQL caused writer hangs and stuck subscriptions due to frequent lock timeouts. This fix allows Parallel Apply to be used reliably without requiring it to be disabled as a workaround.

Corrected the help text for pgd group set-option to accurately reflect group-level options.

Inactive/disconnected slots now display ! instead of * when lag is below 10 MB, restoring consistency.

The pgd node upgrade command now supports the in-place conversion of a non-TDE PGD node to a TDE-enabled node via the --key-unwrap-command and --copy-by-block options.

Resolved a malloc-based memory leak related to the improper freeing of connection strings.

Resolved an issue where Postgres would crash with a segmentation fault when executing a COPY command if the pgaudit.role configuration was set to a non-default value.

Resolved a bug where Connection Manager incorrectly ignored the use_https setting. When upgrading to PGD 6.3.0 or 5.9.2, you must explicitly enable HTTPS by setting the use_https group option to true (in addition to having ssl_cert_file and ssl_key_file configured in postgresql.conf or via the command line) before the upgrade to maintain previous behavior.

Resolved a memory leak in the Connection Manager caused by incorrect handling of Postgres memory contexts during configuration reloads.

Fixed an issue where proxy configurations were not preserved after running bdr_init_physical due to Raft snapshot restores failing to persist proxy settings.

Fixed a bug where sequence_alloc entries persisted after a galloc sequence was dropped and recreated. The fix ensures proper cleanup propagation across the cluster, including witness nodes.

Fixed an issue where changing a sequence kind to galloc would silently discard the provided start_value. Additionally, resolved a bug where a startval of 0 was lost during WAL replication.