-
Notifications
You must be signed in to change notification settings - Fork 246
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #6267 from EnterpriseDB/dev/fi/BDR-5715
PGD 5.6.1 release notes
- Loading branch information
Showing
3 changed files
with
253 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
87 changes: 87 additions & 0 deletions
87
product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| --- | ||
| title: EDB Postgres Distributed 5.6.1 release notes | ||
| navTitle: Version 5.6.1 | ||
| --- | ||
|
|
||
| Released: 25 November 2024 | ||
|
|
||
| EDB Postgres Distributed 5.6.1 includes a number of enhancements and bug fixes. | ||
|
|
||
| ## Highlights | ||
|
|
||
| - Postgres 17 support | ||
| - ARM64 processor support | ||
|
|
||
| ## Features | ||
|
|
||
| <table class="table w-100"><thead><tr><th>Component</th><th>Version</th><th width="75%">Description</th><th width="10%">Addresses</th></tr></thead><tbody> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Added Postgres 17 support</summary><hr/><p>Support for Postgres 17 has been added for all flavors (PostgreSQL, EDB Postgres Extended, | ||
| and EDB Postgres Advanced Server) starting with version 17.2.</p> | ||
| </details></td><td></td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Added ARM64 processor Support</summary><hr/><p>Support ARM architecture for EDB Postgres Distributed on Debian 12 and RHEL 9.</p> | ||
| </details></td><td></td></tr> | ||
| </tbody></table> | ||
|
|
||
|
|
||
| ## Enhancements | ||
|
|
||
| <table class="table w-100"><thead><tr><th>Component</th><th>Version</th><th>Description</th><th width="10%">Addresses</th></tr></thead><tbody> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Added <code>bdr.wait_node_confirm_lsn()</code>.</summary><hr/><p>The function <code>bdr.wait_node_confirm_lsn()</code> has been introduced to wait until a specific node | ||
| reaches a designated Log Sequence Number (LSN). It first checks the <code>confirmed_flush_lsn</code> of | ||
| the replication slot for the specified node. If that information is not available, the function | ||
| connects to the node and queries <code>pg_replication_origin_progress()</code>, using the invoking node as | ||
| the origin. | ||
| If the <code>nodename</code> parameter is NULL, the function will wait for all nodes to reach the specified | ||
| LSN. If the <code>target</code> LSN is NULL, it will wait for the current <code>wal_flush_lsn</code>.</p> | ||
| </details></td><td></td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Improvements made in SO Node Management and Progress Tracking.</summary><hr/><p>An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in | ||
| progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh | ||
| configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted | ||
| to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected, | ||
| and the tap test for group slot movement has been revised. | ||
| Additionally, the <code>bdr_get_all_origins</code> function now considers SO node origins.</p> | ||
| </details></td><td></td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>LSN Progress in Optimized Topology Configurations is now communicated.</summary><hr/><p>While there are no connections from non-leader data nodes to subscriber-only nodes in an optimized | ||
| topology configuration, the LSN progress of all data nodes is periodically communicated to these | ||
| subscriber-only nodes through logical replication.</p> | ||
| </details></td><td></td></tr> | ||
| </tbody></table> | ||
|
|
||
|
|
||
| ## Bug Fixes | ||
|
|
||
| <table class="table w-100"><thead><tr><th>Component</th><th>Version</th><th>Description</th><th width="10%">Addresses</th></tr></thead><tbody> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Addressed walsender crash that happend during configuration reload.</summary><hr/><p>Ensure that pglogical GUCs are overridden only when operating within the pglogical worker. | ||
| If this is not the case, MyPGLogicalWorker will be NULL, resulting in a segmentation fault | ||
| when the walsender attempts a configuration reload from the | ||
| pgl_wait_for_standby_confirmation() function.</p> | ||
| </details></td><td>42100</td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed unintended eager connection related to consensus connections among Subscriber Only group members</summary><hr/><p>The msgbroker module used to establish consensus connections lazily, meaning that connections | ||
| were created only when the first message was sent to a specific destination. This method | ||
| negatively affected the latency of Raft leader elections. The behavior was modified to create | ||
| connections to consensus peers eagerly. However, this change resulted in an unintended | ||
| consequence: a fully meshed consensus network among subscriber-only nodes, which may conflict | ||
| with customer network designs. This patch keeps the eager connection setup but limits it to | ||
| voting nodes only, reverting to a lazy connection setup for non-voting nodes.</p> | ||
| </details></td><td>42041</td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed autopatition task scheduling.</summary><hr/><p>To improve reliability, shuffle the scheduling of autopartition tasks. This way, tasks | ||
| that are prone to failure won't consistently impact the success of other tasks.</p> | ||
| </details></td><td>41998</td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting subscription with standbys.</summary><hr/><p>The parting subscription used to hang, failing to wait for standbys when the | ||
| bdr.standby_slot_names parameter was defined.</p> | ||
| </details></td><td>41821</td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting SO node with multiple origins.</summary><hr/><p>All relevant origins must be removed when parting SO node | ||
| With himesh, parting an SO node should result in removing all origins it | ||
| has, not just the one related to its SO group leader. | ||
| When parting a data node, even though there is no subscription to it | ||
| from SO node, the origin should be removed | ||
| DO not make SO node target of a part catchup subscription when himesh | ||
| enabled</p> | ||
| </details></td><td></td></tr> | ||
| <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Stopped creation of slots for subscriber only nodes on witness nodes.</summary><hr/><p>Subscriber only nodes should not have slots on witness nodes.</p> | ||
| </details></td><td></td></tr> | ||
| <tr><td>PGD Proxy</td><td>5.6.1</td><td><details><summary>Fixed routing strategy for read nodes.</summary><hr/><p>Corrected routing strategy for read nodes after a network partition.</p> | ||
| </details></td><td></td></tr> | ||
| </tbody></table> | ||
|
|
||
|
|
164 changes: 164 additions & 0 deletions
164
product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,164 @@ | ||
| product: EDB Postgres Distributed | ||
| version: 5.6.1 | ||
| date: 25 November 2024 | ||
| meta: | ||
| bdrextension: 5.6.1 | ||
| pgdcli: 5.6.1 | ||
| pgdproxy: 5.6.1 | ||
| intro: | | ||
| EDB Postgres Distributed 5.6.1 includes a number of enhancements and bug fixes. | ||
| highlights: | | ||
| - Postgres 17 support | ||
| - ARM64 processor support | ||
| relnotes: | ||
| - relnote: Added Postgres 17 support | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| Support for Postgres 17 has been added for all flavors (PostgreSQL, EDB Postgres Extended, | ||
| and EDB Postgres Advanced Server) starting with version 17.2. | ||
| jira: BDR-5410 | ||
| addresses: "" | ||
| type: Feature | ||
| severity: High | ||
| impact: High | ||
| - relnote: Added ARM64 processor Support | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| Support ARM architecture for EDB Postgres Distributed on Debian 12 and RHEL 9. | ||
| jira: BDR-5410 | ||
| addresses: "" | ||
| type: Feature | ||
| severity: High | ||
| impact: High | ||
| - relnote: Addressed walsender crash that happend during configuration reload. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| Ensure that pglogical GUCs are overridden only when operating within the pglogical worker. | ||
| If this is not the case, MyPGLogicalWorker will be NULL, resulting in a segmentation fault | ||
| when the walsender attempts a configuration reload from the | ||
| pgl_wait_for_standby_confirmation() function. | ||
| jira: BDR-5661 | ||
| addresses: "42100" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Fixed unintended eager connection related to consensus connections among Subscriber Only group members | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| The msgbroker module used to establish consensus connections lazily, meaning that connections | ||
| were created only when the first message was sent to a specific destination. This method | ||
| negatively affected the latency of Raft leader elections. The behavior was modified to create | ||
| connections to consensus peers eagerly. However, this change resulted in an unintended | ||
| consequence: a fully meshed consensus network among subscriber-only nodes, which may conflict | ||
| with customer network designs. This patch keeps the eager connection setup but limits it to | ||
| voting nodes only, reverting to a lazy connection setup for non-voting nodes. | ||
| jira: BDR-5666 | ||
| addresses: "42041" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Fixed autopatition task scheduling. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| To improve reliability, shuffle the scheduling of autopartition tasks. This way, tasks | ||
| that are prone to failure won't consistently impact the success of other tasks. | ||
| jira: BDR-5638 | ||
| addresses: "41998" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Fixed parting subscription with standbys. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| The parting subscription used to hang, failing to wait for standbys when the | ||
| bdr.standby_slot_names parameter was defined. | ||
| jira: BDR-5658 | ||
| addresses: "41821" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Added `bdr.wait_node_confirm_lsn()`. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| The function `bdr.wait_node_confirm_lsn()` has been introduced to wait until a specific node | ||
| reaches a designated Log Sequence Number (LSN). It first checks the `confirmed_flush_lsn` of | ||
| the replication slot for the specified node. If that information is not available, the function | ||
| connects to the node and queries `pg_replication_origin_progress()`, using the invoking node as | ||
| the origin. | ||
| If the `nodename` parameter is NULL, the function will wait for all nodes to reach the specified | ||
| LSN. If the `target` LSN is NULL, it will wait for the current `wal_flush_lsn`. | ||
| jira: BDR-5200 | ||
| addresses: "" | ||
| type: Enhancement | ||
| severity: High | ||
| impact: High | ||
| - relnote: Improvements made in SO Node Management and Progress Tracking. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in | ||
| progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh | ||
| configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted | ||
| to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected, | ||
| and the tap test for group slot movement has been revised. | ||
| Additionally, the `bdr_get_all_origins` function now considers SO node origins. | ||
| jira: BDR-5549 | ||
| addresses: "" | ||
| type: Enhancement | ||
| severity: High | ||
| impact: High | ||
| - relnote: LSN Progress in Optimized Topology Configurations is now communicated. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| While there are no connections from non-leader data nodes to subscriber-only nodes in an optimized | ||
| topology configuration, the LSN progress of all data nodes is periodically communicated to these | ||
| subscriber-only nodes through logical replication. | ||
| jira: BDR-5549 | ||
| addresses: "" | ||
| type: Enhancement | ||
| severity: High | ||
| impact: High | ||
| - relnote: Fixed parting SO node with multiple origins. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| All relevant origins must be removed when parting SO node | ||
| With himesh, parting an SO node should result in removing all origins it | ||
| has, not just the one related to its SO group leader. | ||
| When parting a data node, even though there is no subscription to it | ||
| from SO node, the origin should be removed | ||
| DO not make SO node target of a part catchup subscription when himesh | ||
| enabled | ||
| jira: BDR-5552 | ||
| addresses: "" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Stopped creation of slots for subscriber only nodes on witness nodes. | ||
| component: BDR | ||
| component_version: 5.6.1 | ||
| details: | | ||
| Subscriber only nodes should not have slots on witness nodes. | ||
| jira: BDR-5618 | ||
| addresses: "" | ||
| type: Bug-fix | ||
| severity: High | ||
| impact: High | ||
| - relnote: Fixed routing strategy for read nodes. | ||
| component: PGD Proxy | ||
| component_version: 5.6.1 | ||
| details: | | ||
| Corrected routing strategy for read nodes after a network partition. | ||
| jira: BDR-5216 | ||
| addresses: "" | ||
| type: Bug-fix | ||
| severity: Medium | ||
| impact: Medium |