From 41bddadf5fe9474bda87d394048c64296333d999 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Thu, 21 Nov 2024 14:11:38 +0000 Subject: [PATCH] Final edits for 5.6.1 release notes Signed-off-by: Dj Walker-Morgan --- .../docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx | 6 +++++- .../docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml | 12 ++++-------- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx index ac5e69aaf0a..7d5b4b340b4 100644 --- a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx +++ b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx @@ -14,7 +14,7 @@ EDB Postgres Distributed 5.6.1 includes a number of enhancements and bug fixes. ## Features - +
ComponentVersionDescriptionAddresses
@@ -45,6 +45,8 @@ Additionally, the bdr_get_all_origins function now considers SO nod topology configuration, the LSN progress of all data nodes is periodically communicated to these subscriber-only nodes through logical replication.

+
ComponentVersionDescriptionAddresses
BDR5.6.1
Added Postgres 17 support

Support for Postgres 17 has been added for all flavors (PostgreSQL, EDB Postgres Extended, and EDB Postgres Advanced Server) starting with version 17.2.

BDR5.6.1
Some DDL commands are now allowed by bdr.permit_unsafe_commands when set.

The bdr.permit_unsafe_commands parameter now allows some DDL commands that were previously disallowed. Specifically ALTER COLUMN...TYPE...USING can now be permitted if the user knows the operation is safe.

+
@@ -80,6 +82,8 @@ enabled

BDR5.6.1
Stopped creation of slots for subscriber only nodes on witness nodes.

Subscriber only nodes should not have slots on witness nodes.

+BDR5.6.1
Ensure no waiting for DEGRADE timeout when in an already degraded state.

When using commit scope with DEGRADE clause, if system detects that it's in degraded state, transactions should start in the DEGRADE mode. This ensures that the timeout is not applied on every commit.

+
PGD Proxy5.6.1
Fixed routing strategy for read nodes.

Corrected routing strategy for read nodes after a network partition.

diff --git a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml index e62ff6c7547..ddfd29bf032 100644 --- a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml +++ b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml @@ -152,25 +152,21 @@ relnotes: type: Bug-fix severity: High impact: High -- relnote: Allow (some) disallowed DDL when bdr.permit_unsafe_commands is enabled +- relnote: Some DDL commands are now allowed by `bdr.permit_unsafe_commands` when set. component: BDR component_version: 5.6.1 details: | - Some DDL commands can be safe in situations PGD does not allow them yet. For example rewriting - ALTER TABLE that only does immutable conversions. The `bdr.permit_unsafe_commands` now allows user - to override the safety check and execute the command anyway, if they are know the command is safe. + The `bdr.permit_unsafe_commands` parameter now allows some DDL commands that were previously disallowed. Specifically `ALTER COLUMN...TYPE...USING` can now be permitted if the user knows the operation is safe. jira: "" addresses: "" type: Enhancement severity: High impact: High -- relnote: Don't wait for DEGRADE clause in every session +- relnote: Ensure no waiting for DEGRADE timeout when in an already degraded state. component: BDR component_version: 5.6.1 details: | - When using commit scope with DEGRADE clause, the transactions are supposed to start in DEGRADE - mode already if system detects that it's in degraded state, so that the timeout is not - applied on every commit. + When using commit scope with DEGRADE clause, if system detects that it's in degraded state, transactions should start in the DEGRADE mode. This ensures that the timeout is not applied on every commit. jira: BDR-5651 addresses: "" type: Bug-fix