From f7815d093e2c2107b642615b12270927fce36cdb Mon Sep 17 00:00:00 2001 From: Florin Irion Date: Thu, 28 May 2026 10:41:29 +0200 Subject: [PATCH 1/5] docs(pgd): document reloadable max_writers GUC bdr.max_writers_per_subscription has been PGC_SIGHUP since PGD 6.3.0 and 5.9.2 but was not documented. The setting can now be changed with ALTER SYSTEM + pg_reload_conf() without a node restart; each writer group captures the value at initialization, so the new limit takes effect on the next writer-group start. Updates the pgd-settings reference on 5.9, 6, 6.3, and 6.4, and appends a retroactive entry to the 6.3.0 and 5.9.2 release-note YAML sources. BDR-7474 --- product_docs/docs/pgd/5.9/reference/pgd-settings.mdx | 4 +++- .../docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml | 12 ++++++++++-- .../tables-views-functions/pgd-settings.mdx | 4 +++- .../docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml | 9 ++++++++- .../tables-views-functions/pgd-settings.mdx | 4 +++- .../docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml | 9 ++++++++- .../tables-views-functions/pgd-settings.mdx | 4 +++- 7 files changed, 38 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/pgd/5.9/reference/pgd-settings.mdx b/product_docs/docs/pgd/5.9/reference/pgd-settings.mdx index 735d0b1af7..1d0449a014 100644 --- a/product_docs/docs/pgd/5.9/reference/pgd-settings.mdx +++ b/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` diff --git a/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml b/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml index a269fe3c34..db53b18a88 100644 --- a/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml +++ b/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 \ No newline at end of file + 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). This entry retroactively documents a change shipped in PGD 5.9.2. + component: BDR + jira: BDR-7474 + addresses: "" + type: Enhancement + impact: Low \ No newline at end of file diff --git a/product_docs/docs/pgd/6.3/reference/tables-views-functions/pgd-settings.mdx b/product_docs/docs/pgd/6.3/reference/tables-views-functions/pgd-settings.mdx index b893b5e865..8b687d6f4a 100644 --- a/product_docs/docs/pgd/6.3/reference/tables-views-functions/pgd-settings.mdx +++ b/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` diff --git a/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml b/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml index bf724b0407..d2acdb5b6d 100644 --- a/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml +++ b/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 \ No newline at end of file + 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). This entry retroactively documents a change shipped in PGD 6.3.0. + jira: BDR-7474 + addresses: "" + type: Enhancement + impact: Low \ No newline at end of file diff --git a/product_docs/docs/pgd/6.4/reference/tables-views-functions/pgd-settings.mdx b/product_docs/docs/pgd/6.4/reference/tables-views-functions/pgd-settings.mdx index e6ab3bc33c..6acedf6e00 100644 --- a/product_docs/docs/pgd/6.4/reference/tables-views-functions/pgd-settings.mdx +++ b/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` diff --git a/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml b/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml index bf724b0407..d2acdb5b6d 100644 --- a/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml +++ b/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 \ No newline at end of file + 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). This entry retroactively documents a change shipped in PGD 6.3.0. + jira: BDR-7474 + addresses: "" + type: Enhancement + impact: Low \ No newline at end of file diff --git a/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx b/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx index 8158017fc6..cb4bff47ce 100644 --- a/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx +++ b/product_docs/docs/pgd/6/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` From 879f8aed4cf063b663f32da0a7795920c9283b3f Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 28 May 2026 08:43:49 +0000 Subject: [PATCH 2/5] update generated release notes --- product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx | 2 ++ product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx | 2 ++ product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx | 2 ++ 3 files changed, 6 insertions(+) diff --git a/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx b/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx index 526c28567b..ec67c2cb39 100644 --- a/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx +++ b/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 BDR5.9.2
Added support for user name mapping (pg_ident.conf) to the Connection Manager.

This enhancement allows the Connection Manager to use pg_ident.conf for user name mapping. Currently, this functionality applies to the cert authentication method, aligning Connection Manager behavior with PostgreSQL’s native authentication identity mapping.

+BDR5.9.2
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 5.9.2.

+
diff --git a/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx b/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx index 4c9efc10f5..727d6ae0d6 100644 --- a/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx +++ b/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
Added the bdr.prepared_xacts_summary diagnostic view.

Introduced bdr.prepared_xacts_summary, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.

+
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 6.3.0.

+
diff --git a/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx b/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx index 753ea02cdf..57f397d1d6 100644 --- a/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx +++ b/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
Added the bdr.prepared_xacts_summary diagnostic view.

Introduced bdr.prepared_xacts_summary, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.

+
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 6.3.0.

+
From 2a9f61d3db887d11d5b44a35aa1135cd865b72f3 Mon Sep 17 00:00:00 2001 From: Mireia Perez Fuster Date: Thu, 28 May 2026 17:36:32 +0100 Subject: [PATCH 3/5] Removed relnote from 6.4, removed note about retroactively documenting, and removed reference from 6.0 --- product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml | 2 +- .../pgd/6/reference/tables-views-functions/pgd-settings.mdx | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml b/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml index db53b18a88..74edd6edaf 100644 --- a/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml +++ b/product_docs/docs/pgd/5.9/rel_notes/src/relnote_5.9.2.yml @@ -165,7 +165,7 @@ relnotes: 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). This entry retroactively documents a change shipped in PGD 5.9.2. + `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: "" diff --git a/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx b/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx index cb4bff47ce..5796f6a2b1 100644 --- a/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx +++ b/product_docs/docs/pgd/6/reference/tables-views-functions/pgd-settings.mdx @@ -196,8 +196,6 @@ this with `bdr.alter_node_group_option` for a group.) 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` Replicates current transaction (default is `on`). From b18e89e0eeca157fdbe0b763393d367ee019c94f Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 28 May 2026 16:39:29 +0000 Subject: [PATCH 4/5] update generated release notes --- product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx | 2 +- product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml | 2 +- product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx b/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx index ec67c2cb39..ceffe7e36e 100644 --- a/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx +++ b/product_docs/docs/pgd/5.9/rel_notes/pgd_5.9.2_rel_notes.mdx @@ -19,7 +19,7 @@ This is a patch release of PGD 5, which includes several enhancements and bug fi BDR5.9.2
Added support for user name mapping (pg_ident.conf) to the Connection Manager.

This enhancement allows the Connection Manager to use pg_ident.conf for user name mapping. Currently, this functionality applies to the cert authentication method, aligning Connection Manager behavior with PostgreSQL’s native authentication identity mapping.

-BDR5.9.2
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 5.9.2.

+BDR5.9.2
Made bdr.max_writers_per_subscription runtime-reloadable.

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).

diff --git a/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml b/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml index d2acdb5b6d..2260a94787 100644 --- a/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml +++ b/product_docs/docs/pgd/6.3/rel_notes/src/relnote_6.3.0.yml @@ -255,7 +255,7 @@ relnotes: 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). This entry retroactively documents a change shipped in PGD 6.3.0. + `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 diff --git a/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml b/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml index d2acdb5b6d..2260a94787 100644 --- a/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml +++ b/product_docs/docs/pgd/6.4/rel_notes/src/relnote_6.3.0.yml @@ -255,7 +255,7 @@ relnotes: 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). This entry retroactively documents a change shipped in PGD 6.3.0. + `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 From 732b30362762603d2813ada0499a175c7365fae7 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 28 May 2026 16:56:11 +0000 Subject: [PATCH 5/5] update generated release notes --- product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx | 2 +- product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx b/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx index 727d6ae0d6..e5212dba61 100644 --- a/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx +++ b/product_docs/docs/pgd/6.3/rel_notes/pgd_6.3.0_rel_notes.mdx @@ -53,7 +53,7 @@ EDB Postgres Distributed (PGD) 6.3.0 includes new features, enhancements, and bu
Added the bdr.prepared_xacts_summary diagnostic view.

Introduced bdr.prepared_xacts_summary, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.

-
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 6.3.0.

+
Made bdr.max_writers_per_subscription runtime-reloadable.

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).

diff --git a/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx b/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx index 57f397d1d6..1e84c9bfe3 100644 --- a/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx +++ b/product_docs/docs/pgd/6.4/rel_notes/pgd_6.3.0_rel_notes.mdx @@ -53,7 +53,7 @@ EDB Postgres Distributed (PGD) 6.3.0 includes new features, enhancements, and bu
Added the bdr.prepared_xacts_summary diagnostic view.

Introduced bdr.prepared_xacts_summary, a local diagnostic view for monitoring prepared transactions implicitly created by group commit scopes.

-
Made bdr.max_writers_per_subscription runtime-reloadable.

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). This entry retroactively documents a change shipped in PGD 6.3.0.

+
Made bdr.max_writers_per_subscription runtime-reloadable.

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).