docs(pgd): document reloadable max_writers GUC

product_docs/docs/pgd/5.9/reference/pgd-settings.mdx

@@ -193,7 +193,9 @@ this with `bdr.alter_node_group_option` for a group.)
 
 ### `bdr.max_writers_per_subscription`
 
-Maximum number of writers per subscription (sets upper limit for the `bdr.writers_per_subscription` setting).
+Maximum number of writers per subscription. Sets the upper limit for the `bdr.writers_per_subscription` setting.
+
+Reloadable at runtime (`PGC_SIGHUP`) since PGD 5.9.2: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
 
 ### `bdr.xact_replication` 
 

product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx

@@ -19,6 +19,8 @@ This is a patch release of PGD 5, which includes several enhancements and bug fi
 </details></td><td></td></tr>
 <tr><td>BDR</td><td>5.9.2</td><td><details><summary>Added support for user name mapping (<code>pg_ident.conf</code>) to the Connection Manager.</summary><hr/><p>This enhancement allows the Connection Manager to use <code>pg_ident.conf</code> for user name mapping. Currently, this functionality applies to the <code>cert</code> authentication method, aligning Connection Manager behavior with PostgreSQL’s native authentication identity mapping.</p>
 </details></td><td></td></tr>
+<tr><td>BDR</td><td>5.9.2</td><td><details><summary>Made <code>bdr.max_writers_per_subscription</code> runtime-reloadable.</summary><hr/><p><code>bdr.max_writers_per_subscription</code> is now <code>PGC_SIGHUP</code>: change the value with <code>ALTER SYSTEM</code> followed by <code>pg_reload_conf()</code> — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).</p>
+</details></td><td></td></tr>
 </tbody></table>
 
 

product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml

@@ -158,8 +158,16 @@ relnotes:
 - relnote: Fixed `ALTER ROLE` replication failures.
   details: |
     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.
-  component: BDR  
+  component: BDR
   jira: BDR-7590
   addresses: "54906"
   type: Bug Fix
-  impact: High
+  impact: High
+- relnote: Made `bdr.max_writers_per_subscription` runtime-reloadable.
+  details: |
+    `bdr.max_writers_per_subscription` is now `PGC_SIGHUP`: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
+  component: BDR
+  jira: BDR-7474
+  addresses: ""
+  type: Enhancement
+  impact: Low

product_docs/docs/pgd/6.3/reference/tables-views-functions/pgd-settings.mdx

@@ -194,7 +194,9 @@ this with `bdr.alter_node_group_option` for a group.)
 
 ### `bdr.max_writers_per_subscription`
 
-Maximum number of writers per subscription (sets upper limit for the `bdr.writers_per_subscription` setting).
+Maximum number of writers per subscription. Sets the upper limit for the `bdr.writers_per_subscription` setting.
+
+Reloadable at runtime (`PGC_SIGHUP`) since PGD 6.3.0: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
 
 ### `bdr.xact_replication`
 

product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx

@@ -53,6 +53,8 @@ EDB Postgres Distributed (PGD) 6.3.0 includes new features, enhancements, and bu
 </details></td><td></td></tr>
 <tr><td><details><summary>Added the <code>bdr.prepared_xacts_summary</code> diagnostic view.</summary><hr/><p>Introduced <a href="/pgd/current/reference/tables-views-functions/catalogs-internal#bdrprepared_xacts_summary">bdr.prepared_xacts_summary</a>, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.</p>
 </details></td><td></td></tr>
+<tr><td><details><summary>Made <code>bdr.max_writers_per_subscription</code> runtime-reloadable.</summary><hr/><p><code>bdr.max_writers_per_subscription</code> is now <code>PGC_SIGHUP</code>: change the value with <code>ALTER SYSTEM</code> followed by <code>pg_reload_conf()</code> — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).</p>
+</details></td><td></td></tr>
 </tbody></table>
 
 

product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml

@@ -252,4 +252,11 @@ relnotes:
   jira: BDR-7590
   addresses: "54906"
   type: Bug Fix
-  impact: High
+  impact: High
+- relnote: Made `bdr.max_writers_per_subscription` runtime-reloadable.
+  details: |
+    `bdr.max_writers_per_subscription` is now `PGC_SIGHUP`: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
+  jira: BDR-7474
+  addresses: ""
+  type: Enhancement
+  impact: Low

product_docs/docs/pgd/6.4/reference/tables-views-functions/pgd-settings.mdx

@@ -194,7 +194,9 @@ this with `bdr.alter_node_group_option` for a group.)
 
 ### `bdr.max_writers_per_subscription`
 
-Maximum number of writers per subscription (sets upper limit for the `bdr.writers_per_subscription` setting).
+Maximum number of writers per subscription. Sets the upper limit for the `bdr.writers_per_subscription` setting.
+
+Reloadable at runtime (`PGC_SIGHUP`) since PGD 6.3.0: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
 
 ### `bdr.xact_replication`
 

product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx

@@ -53,6 +53,8 @@ EDB Postgres Distributed (PGD) 6.3.0 includes new features, enhancements, and bu
 </details></td><td></td></tr>
 <tr><td><details><summary>Added the <code>bdr.prepared_xacts_summary</code> diagnostic view.</summary><hr/><p>Introduced <a href="/pgd/current/reference/tables-views-functions/catalogs-internal#bdrprepared_xacts_summary">bdr.prepared_xacts_summary</a>, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.</p>
 </details></td><td></td></tr>
+<tr><td><details><summary>Made <code>bdr.max_writers_per_subscription</code> runtime-reloadable.</summary><hr/><p><code>bdr.max_writers_per_subscription</code> is now <code>PGC_SIGHUP</code>: change the value with <code>ALTER SYSTEM</code> followed by <code>pg_reload_conf()</code> — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).</p>
+</details></td><td></td></tr>
 </tbody></table>
 
 

product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml

@@ -252,4 +252,11 @@ relnotes:
   jira: BDR-7590
   addresses: "54906"
   type: Bug Fix
-  impact: High
+  impact: High
+- relnote: Made `bdr.max_writers_per_subscription` runtime-reloadable.
+  details: |
+    `bdr.max_writers_per_subscription` is now `PGC_SIGHUP`: change the value with `ALTER SYSTEM` followed by `pg_reload_conf()` — no node restart is required. The value is captured by each writer group at initialization, so an in-flight subscription continues with the value it was started with; the new limit takes effect on the next writer-group start (subscription disable/enable, or the next reconnect cycle).
+  jira: BDR-7474
+  addresses: ""
+  type: Enhancement
+  impact: Low

product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx

@@ -194,7 +194,7 @@ this with `bdr.alter_node_group_option` for a group.)
 
 ### `bdr.max_writers_per_subscription`
 
-Maximum number of writers per subscription (sets upper limit for the `bdr.writers_per_subscription` setting).
+Maximum number of writers per subscription. Sets the upper limit for the `bdr.writers_per_subscription` setting.
 
 ### `bdr.xact_replication`