Merge pull request #6273 from EnterpriseDB/DOCS-1076-relnote-update-petr

Update relnote_5.6.1.yml

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
 
-<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>
+<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 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>
@@ -45,6 +45,8 @@ Additionally, the <code>bdr_get_all_origins</code> 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.</p>
 </details></td><td></td></tr>
+<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Some DDL commands are now allowed by <code>bdr.permit_unsafe_commands</code> when set.</summary><hr/><p>The <code>bdr.permit_unsafe_commands</code> parameter now allows some DDL commands that were previously disallowed. Specifically <code>ALTER COLUMN...TYPE...USING</code> can now be permitted if the user knows the operation is safe.</p>
+</details></td><td></td></tr>
 </tbody></table>
 
 
@@ -80,6 +82,8 @@ 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>BDR</td><td>5.6.1</td><td><details><summary>Ensure no waiting for DEGRADE timeout when in an already degraded state.</summary><hr/><p>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.</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>

product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml

@@ -152,6 +152,26 @@ relnotes:
   type: Bug-fix
   severity: High
   impact: High
+- relnote: Some DDL commands are now allowed by `bdr.permit_unsafe_commands` when set.
+  component: BDR
+  component_version: 5.6.1
+  details: |
+    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: 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, 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
+  severity: High
+  impact: High
 - relnote: Fixed routing strategy for read nodes.
   component: PGD Proxy
   component_version: 5.6.1