Reduce lock strength in manager process

product_docs/docs/pgd/5.8/rel_notes/pgd_5.8.0_rel_notes.mdx

@@ -101,6 +101,8 @@ Skip reconfiguring subscriptions if there are no leadership changes.</p>
 </details></td><td>46519</td></tr>
 <tr><td>BDR</td><td>5.8.0</td><td><details><summary>Subscriber-only nodes will not take a lock when running DDL</summary><hr/><p>Subscriber-only nodes will no longer attempt to take a lock on the cluster when running DDL. The DDL will be executed locally and not replicated to other nodes.</p>
 </details></td><td>47233</td></tr>
+<tr><td>BDR</td><td>5.8.0</td><td><details><summary>Fixed deadlock during PGD queue cleanup by reducing the lock strength of the manager process</summary><hr/><p>Reduced the lock strength used by the manager process when deleting old rows from the <code>bdr.queue</code> catalog. The previous use of <code>ShareRowExclusiveLock</code> was excessively strict and could lead to a deadlock scenario when concurrently trying to clean up and resolve prepared transactions that had inserted data.</p>
+</details></td><td>46426</td></tr>
 <tr><td>BDR</td><td>5.8.0</td><td><details><summary>Fixed deadlock issue in bdr_init_physical.</summary><hr/><p>Fixed deadlock between bdr_init_physical cleaning unwanted node data and concurrent monitoring queries.</p>
 </details></td><td>46952</td></tr>
 <tr><td>BDR</td><td>5.8.0</td><td><details><summary>Fixed a consistency issue in node join where a joining node could possibly miss some data sent to it from the source node.</summary><hr/><p>Fixed an issue when a new node joining the cluster finishes CATCHUP phase before getting its replication progress against all data nodes. This could have caused a new node to be out of sync with the cluster.</p>

product_docs/docs/pgd/5.8/rel_notes/src/relnote_5.8.0.yml

@@ -249,3 +249,11 @@ relnotes:
   type: Security
   impact: Highest
 
+- relnote: Fixed deadlock during PGD queue cleanup by reducing the lock strength of the manager process
+  details: |
+    Reduced the lock strength used by the manager process when deleting old rows from the `bdr.queue` catalog. The previous use of `ShareRowExclusiveLock` was excessively strict and could lead to a deadlock scenario when concurrently trying to clean up and resolve prepared transactions that had inserted data.
+  component: BDR
+  jira: BDR-6278
+  addresses: "46426"
+  type: Bug Fix
+  impact: Medium

product_docs/docs/pgd/6.1/rel_notes/index.mdx

@@ -20,7 +20,7 @@ The EDB Postgres Distributed documentation describes the latest version of EDB P
 
 | Release Date | EDB Postgres Distributed |
 |---|---|
-| 04 Nov 2025 | [6.1.2](./pgd_6.1.2_rel_notes) |
+| 06 Nov 2025 | [6.1.2](./pgd_6.1.2_rel_notes) |
 | 09 Oct 2025 | [6.1.1](./pgd_6.1.1_rel_notes) |
 | 19 Aug 2025 | [6.1.0](./pgd_6.1.0_rel_notes) |
 | 25 Jun 2025 | [6.0.2](./pgd_6.0.2_rel_notes) |

product_docs/docs/pgd/6.1/rel_notes/pgd_6.1.2_rel_notes.mdx

@@ -6,7 +6,7 @@ originalFilePath: product_docs/docs/pgd/6.1/rel_notes/src/relnote_6.1.2.yml
 editTarget: originalFilePath
 ---
 
-Released: 4 November 2025
+Released: 6 November 2025
 
 EDB Postgres Distributed 6.1.2 includes only bug fixes focused on improving stability and reliability. No new features or enhancements are included in this release. Please see the details below.
 

product_docs/docs/pgd/6.1/rel_notes/src/relnote_6.1.2.yml

@@ -1,7 +1,7 @@
 # yaml-language-server: $schema=https://raw.githubusercontent.com/EnterpriseDB/docs/refs/heads/develop/tools/automation/generators/relgen/relnote-schema.json
 product: EDB Postgres Distributed
 version: 6.1.2
-date:  4 November 2025
+date:  6 November 2025
 intro: |
   EDB Postgres Distributed 6.1.2 includes only bug fixes focused on improving stability and reliability. No new features or enhancements are included in this release. Please see the details below.