From 5f992d7661fc8cfecec4d6002cfdc6ed71bf2425 Mon Sep 17 00:00:00 2001
From: smaher-edb <suraj.maher@enterprisedb.com>
Date: Wed, 25 Oct 2023 18:44:54 +0530
Subject: [PATCH 01/38] Remove pre-upgrade step which alters the conn limit to
 0 at db level

Ref: BDR-4159
---
 product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx | 1 -
 product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx | 3 +--
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
index b75915c667f..bb641554852 100644
--- a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
@@ -128,7 +128,6 @@ Steps performed when running `bdr_pg_upgrade`.
 | Checking if bdr schema exists                   | `skip`             |
 | Turning DDL replication off                     | `skip`             |
 | Terminating connections to database.            | `skip`             |
-| Disabling connections to database               | `skip`             |
 | Waiting for all slots to be flushed             | `skip`             |
 | Disconnecting from old cluster                  | `skip`             |
 | Stopping old cluster                            | `skip`             |
diff --git a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
index 7f87b9d5c04..e71d01813eb 100644
--- a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
@@ -49,7 +49,7 @@ To upgrade to a newer major version of Postgres, you must first install the new
 ### bdr_pg_upgrade command-line
 
 bdr_pg_upgrade passes all parameters to pg_upgrade. Therefore, you can
-specify any parameters supported by [pg_upgrade](https://www.postgresql.org/docs/current/pgupgrade.html#id-1.9.5.12.6). 
+specify any parameters supported by [pg_upgrade](https://www.postgresql.org/docs/current/pgupgrade.html#id-1.9.5.12.6).
 
 #### Synopsis
 
@@ -149,7 +149,6 @@ These steps are performed when running bdr_pg_upgrade.
 | Checking if bdr schema exists                   | `skip`             |
 | Turning DDL replication off                     | `skip`             |
 | Terminating connections to database.            | `skip`             |
-| Disabling connections to database               | `skip`             |
 | Waiting for all slots to be flushed             | `skip`             |
 | Disconnecting from old cluster                  | `skip`             |
 | Stopping old cluster                            | `skip`             |

From d1190e352406f667c8fd4e82c68f9ac047ad491a Mon Sep 17 00:00:00 2001
From: smaher-edb <suraj.maher@enterprisedb.com>
Date: Wed, 1 Nov 2023 18:04:52 +0530
Subject: [PATCH 02/38] Add the version supported for 3.7

---
 product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx | 2 +-
 product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
index bb641554852..94764e068d2 100644
--- a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
@@ -33,7 +33,7 @@ There are several prerequisites for `bdr_pg_upgrade` that have to be met:
 -   Peer authentication is configured for both clusters, `bdr_pg_upgrade`
     requires peer authentication
 -   BDR versions on both clusters must be exactly the same and must be version
-    4.1.0 or above
+    4.1.0 or above. For v3.7, version 3.7.22 and above are also supported.
 -   The new cluster must be in a shutdown state
 -   BDR packages must be installed in the new cluster
 -   The new cluster must be already initialized and configured as needed to
diff --git a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
index e71d01813eb..e48e49511a0 100644
--- a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
@@ -32,7 +32,7 @@ You must meet several prerequisites for bdr_pg_upgrade:
 -   Configure peer authentication for both clusters. bdr_pg_upgrade
     requires peer authentication.
 -   PGD versions on both clusters must be exactly the same and must be version
-    4.1.0 or later.
+    4.1.0 or later. For v3.7, version 3.7.22 and above are also supported.
 -   The new cluster must be in a shutdown state.
 -   You must install PGD packages in the new cluster.
 -   The new cluster must be already initialized and configured as needed to

From e4a573609229e05a33c6a5a80a16cc1c560ee57d Mon Sep 17 00:00:00 2001
From: smaher-edb <suraj.maher@enterprisedb.com>
Date: Wed, 1 Nov 2023 19:57:45 +0530
Subject: [PATCH 03/38] Fix the review comments

---
 product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx | 4 ++--
 product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
index 94764e068d2..c28e470c301 100644
--- a/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/4/upgrades/bdr_pg_upgrade.mdx
@@ -32,8 +32,8 @@ There are several prerequisites for `bdr_pg_upgrade` that have to be met:
     be redirected to another node in the cluster
 -   Peer authentication is configured for both clusters, `bdr_pg_upgrade`
     requires peer authentication
--   BDR versions on both clusters must be exactly the same and must be version
-    4.1.0 or above. For v3.7, version 3.7.22 and above are also supported.
+-   The same BDR version must be installed on both clusters.
+-   The BDR version must be 4.1.0 or above. Version 3.7.22 and later is also supported.
 -   The new cluster must be in a shutdown state
 -   BDR packages must be installed in the new cluster
 -   The new cluster must be already initialized and configured as needed to
diff --git a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
index e48e49511a0..e4256819007 100644
--- a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
@@ -31,8 +31,8 @@ You must meet several prerequisites for bdr_pg_upgrade:
     redirect them to another node in the cluster.
 -   Configure peer authentication for both clusters. bdr_pg_upgrade
     requires peer authentication.
--   PGD versions on both clusters must be exactly the same and must be version
-    4.1.0 or later. For v3.7, version 3.7.22 and above are also supported.
+-   The same BDR version must be installed on both clusters.
+-   The BDR version must be 4.1.0 or above. Version 3.7.22 and later is also supported.
 -   The new cluster must be in a shutdown state.
 -   You must install PGD packages in the new cluster.
 -   The new cluster must be already initialized and configured as needed to

From 28e6e0b0d03b4ecac876e43f1c7f540644189719 Mon Sep 17 00:00:00 2001
From: smaher-edb <suraj.maher@enterprisedb.com>
Date: Wed, 1 Nov 2023 20:05:32 +0530
Subject: [PATCH 04/38] change BDR to PGD only in v5 doc

---
 product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
index e4256819007..c9fff321723 100644
--- a/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
+++ b/product_docs/docs/pgd/5/upgrades/bdr_pg_upgrade.mdx
@@ -31,8 +31,8 @@ You must meet several prerequisites for bdr_pg_upgrade:
     redirect them to another node in the cluster.
 -   Configure peer authentication for both clusters. bdr_pg_upgrade
     requires peer authentication.
--   The same BDR version must be installed on both clusters.
--   The BDR version must be 4.1.0 or above. Version 3.7.22 and later is also supported.
+-   The same PGD version must be installed on both clusters.
+-   The PGD version must be 4.1.0 or above. Version 3.7.22 and later is also supported.
 -   The new cluster must be in a shutdown state.
 -   You must install PGD packages in the new cluster.
 -   The new cluster must be already initialized and configured as needed to

From b81dc27ad8c1acf9f09a16aae728e98bc053b024 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Wed, 8 Nov 2023 10:44:24 +0000
Subject: [PATCH 05/38] Simplified compatibility chart

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/5/index.mdx | 30 +++++++++++++++++++++++++-----
 1 file changed, 25 insertions(+), 5 deletions(-)

diff --git a/product_docs/docs/pgd/5/index.mdx b/product_docs/docs/pgd/5/index.mdx
index da57bf12902..8d198e2b3b2 100644
--- a/product_docs/docs/pgd/5/index.mdx
+++ b/product_docs/docs/pgd/5/index.mdx
@@ -53,14 +53,34 @@ the peer nodes only after the local commit. You can configure additional levels
 [Group Commit](durability/group-commit), [CAMO](durability/camo), or
 [Eager](consistency/eager) Replication.
 
+## Compatibility
+
+EDB Postgres Distributed 5 is compatible with
+
+ Package | Versions
+-------- | ------------
+Community PostgreSQL | 12-16
+EDB Postgres Extended Server | 12-16
+EDB Postgres Advanced Server | 12-16
+
+!!! Note Postgres 16 support
+Postgres 16 support is only available in EDB Postgres Distributed 5.3 and later
+!!!
+
+See the [compatibility matrix](/pgd/4/#compatibility-matrix) for previous Versions
+
+<!---
 ## Compatibility matrix
 
 | EDB Postgres <br/> Distributed | Community <br/> PostgreSQL | EDB Postgres <br/> Extended Server | EDB Postgres <br/> Advanced Server | PGD <br/> CLI | PGD-Proxy | BDR <br/> Extension | pgLogical3 <br/> Extension | HARP |
 | ------------------------------ | --------------------------- | ---------------------------------- | ---------------------------------- | ------------- | --------- | ------------------- | -------------------------- | ---- |
-| 5                              | 12-15              | 12-15                     | 12-15                     | 5             | 5         | 5                   | n/a                        | n/a  |
-| 4                              | 12-14                  | 12-14                         | 12-14                         | 1             | n/a       | 4                   | n/a                        | 2    |
-| 3.7                            | 11-13                  | 11r2-13                       | 11-13                         | n/a           | n/a       | 3.7                 | 3.7                        | 2    |
+| 5                              | 12-16\*              | 12-16\*                     | 12-16\*                     | 5             | 5         | 5                   | n/a                        | n/a  |
+| 4                              | 12-14                  | 12-14                         | 12-14                         | 1\*\*             | n/a       | 4                   | n/a                        | 2\*\*\*    |
+| 3.7                            | 11-13                  | 11r2-13                       | 11-13                         | n/a           | n/a       | 3.7                 | 3.7                        | 2\*\*\*    |
+
+&nbsp;&nbsp;&nbsp;&nbsp; \* Version 16 is only supported from PGD 5.3 and later.<br/>
+&nbsp;&nbsp;&nbsp;&nbsp; \*\* PGD CLI 1 is supported with BDR 4.1 and later.<br/>
+&nbsp;&nbsp;&nbsp;&nbsp; \*\*\* BDR DCS in HARP 2 is supported with BDR 3.7.15 and later and 4.0.1 and later.<br/>
 
-- PGD CLI 1 is supported with BDR 4.1 and later.
-- BDR DCS in HARP 2 is supported with BDR 3.7.15 and later and 4.0.1 and later.
 
+--->

From d10241e905b6e524af1cb762eaa3c336b3aafa2a Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Wed, 8 Nov 2023 10:45:08 +0000
Subject: [PATCH 06/38] Fix typo

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/5/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/index.mdx b/product_docs/docs/pgd/5/index.mdx
index 8d198e2b3b2..bf4c894d88f 100644
--- a/product_docs/docs/pgd/5/index.mdx
+++ b/product_docs/docs/pgd/5/index.mdx
@@ -67,7 +67,7 @@ EDB Postgres Advanced Server | 12-16
 Postgres 16 support is only available in EDB Postgres Distributed 5.3 and later
 !!!
 
-See the [compatibility matrix](/pgd/4/#compatibility-matrix) for previous Versions
+See the [compatibility matrix](/pgd/4/#compatibility-matrix) for previous versions
 
 <!---
 ## Compatibility matrix

From 82db13302ac3c5bc6635ea98242ff10025f83e3b Mon Sep 17 00:00:00 2001
From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com>
Date: Thu, 9 Nov 2023 20:59:46 +0530
Subject: [PATCH 07/38] pgPool - New release

---
 .../pgpool/4/pgpool_rel_notes/443_rel_notes.mdx     | 13 +++++++++++++
 .../docs/pgpool/4/pgpool_rel_notes/index.mdx        |  2 ++
 2 files changed, 15 insertions(+)
 create mode 100644 product_docs/docs/pgpool/4/pgpool_rel_notes/443_rel_notes.mdx

diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/443_rel_notes.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/443_rel_notes.mdx
new file mode 100644
index 00000000000..26b3a7f434b
--- /dev/null
+++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/443_rel_notes.mdx
@@ -0,0 +1,13 @@
+---
+title: "EDB PgPool-II 4.4.3 release notes"
+navTitle: Version 4.4.3
+---
+
+Released: 09 Nov 2023
+
+EDB Pgpool-II 4.4.3 includes the following upstream merge:
+
+| Type           | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Upstream merge | Merged with community Pgpool-II 4.4.3. See the community [Release Notes](https://www.pgpool.net/docs/44/en/html/release-4-4-3.html) for details.                                        |
+| Enhancement    | Added support for EDB Postgres Advanced Server 16. |
\ No newline at end of file
diff --git a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx
index 1b0236f8d2f..1d1e39b90e7 100644
--- a/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx
+++ b/product_docs/docs/pgpool/4/pgpool_rel_notes/index.mdx
@@ -3,6 +3,7 @@ title: "Release notes"
 redirects:
   - ../01_whats_new/
 navigation:
+- 443_rel_notes
 - 442_rel_notes
 - 07_432_rel_notes
 - 08_430_rel_notes
@@ -18,6 +19,7 @@ The EDB Pgpool-II documentation describes the latest version of EDB Pgpool-II, i
 
 |                                                             Version                                                             | Release Date |                                                                                                                                                                                                   Upstream merges                                                                                                                                                                                                    |     |
 | ------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
+| [4.4.3](443_rel_notes)                                                                                                       | 09 Nov 2023 | Upstream [4.4.3](https://www.pgpool.net/docs/44/en/html/release-4-4-3.html)                                                                                                                                                                                                                                                                                                                                |     |
 | [4.4.2](442_rel_notes)                                                                                                       | 14 Feb 2023 | Upstream [4.4.2](https://www.pgpool.net/docs/44/en/html/release-4-4-2.html)                                                                                                                                                                                                                                                                                                                                |     |
 | [4.3.2](07_432_rel_notes), [4.2.9](429_rel_notes), [4.1.12](4112_rel_notes), [4.0.19](4019_rel_notes), [3.7.24](3724_rel_notes) | 05 Jul 2022 | Upstream [4.3.2](https://www.pgpool.net/docs/43/en/html/release-4-3-2.html#bug-fixes), [4.2.9](https://www.pgpool.net/docs/43/en/html/release-4-2-9.html#bug-fixes),  [4.1.12](https://www.pgpool.net/docs/43/en/html/release-4-1-12.html#bug-fixes), [4.0.19](https://www.pgpool.net/docs/43/en/html/release-4-0-19.html#bug-fixes), [3.7.24](https://www.pgpool.net/docs/43/en/html/release-3-7-24.html#bug-fixes) |     |
 | [4.3.0](08_430_rel_notes)                                                                                                       | 01 Feb 2022 | Upstream [4.3.0](https://www.pgpool.net/docs/43/en/html/release-4-3-0.html#bug-fixes)                                                                                                                                                                                                                                                                                                                                |     |

From 4d40971d738e831d2ad9733d3686193c687cd9f3 Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Wed, 1 Nov 2023 17:08:12 +0530
Subject: [PATCH 08/38] Create release notes for PGD 3.7.23 and pglogical
 3.7.23 and entry for bdr_pg_upgrade

---
 .../docs/pgd/3.7/bdr/release-notes.mdx        | 459 +++++++++---------
 .../docs/pgd/3.7/pglogical/release-notes.mdx  | 143 +++---
 2 files changed, 315 insertions(+), 287 deletions(-)

diff --git a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
index ff46107a01b..578b9c874ee 100644
--- a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
+++ b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
@@ -5,6 +5,25 @@ originalFilePath: release-notes.md
 
 ---
 
+## BDR 3.7.23 (2023 Nov 14)
+
+This is a maintenance release for BDR 3.7 that includes minor
+improvements as well as fixes for issues identified in previous
+versions.
+
+Also check the release notes for [pglogical 3.7.23](/pgd/3.7/pglogical/release-notes/#pglogical-3723) for resolved issues
+that affect BDR as well.
+
+
+### Resolved issues
+
+### Improvements
+
+- Add support for BDR 3.7.22 and above in bdr_pg_upgrade v1.2.0
+
+### Upgrades
+
+
 ## BDR 3.7.22 (2023 Aug 31)
 
 This is a maintenance release for BDR 3.7 that includes minor
@@ -58,7 +77,7 @@ This is a maintenance release for BDR 3.7 that includes minor
 improvements as well as fixes for issues identified in previous
 versions.
 
-Also check the release notes for [pglogical 3.7.21](/pgd/3.7/pglogical/release-notes/#pglogical-3721) for resolved issues
+Also check the release notes for [pglogical 3.7.21](/pgd/3.7/pglogical/release-notes/#pglogical-372PG1) for resolved issues
 that affect BDR as well.
 
 
@@ -138,7 +157,7 @@ that affect BDR as well.
 
 ### Resolved issues
 
-- Fix timeout issue related to global lock handling (BDR-2836)   
+- Fix timeout issue related to global lock handling (BDR-2836)
   Correctly lock Raft maintained tables when needed.
 
 ### Upgrades
@@ -159,18 +178,18 @@ that affect BDR as well.
 
 ### Resolved issues
 
-- Don't wait for ADD CONSTRAINT progress if DDL replication is off (BDR-2645, RT86043)  
+- Don't wait for ADD CONSTRAINT progress if DDL replication is off (BDR-2645, RT86043)
   The constraint validation from all nodes is not needed if we don't replicate
   the DDL or from any node that is PARTED or STANDBY.
 
-- Fix raft snapshot read/write routines for sequences (BDR-2666, RT86246)  
+- Fix raft snapshot read/write routines for sequences (BDR-2666, RT86246)
   Adjust joining to older BDR 3.6 version nodes while using galloc sequences.
 
-- Fix rare segfault for bdr.drop_node()  
+- Fix rare segfault for bdr.drop_node()
   Check for null values in the result from all the other nodes
   when trying to drop a node.
 
-- Fix hangs in multiple concurrent joins (RT82977)  
+- Fix hangs in multiple concurrent joins (RT82977)
   Various lock corrections for functons and raft requests that reduces
   the probability of distributed deadlocks.
 
@@ -193,19 +212,19 @@ that affect BDR as well.
 
 ### Resolved issues
 
-- Fix spurious segmentation faults when conflicts are logged to bdr.conflict_history  (BDR-2403, RT83436, RT83928)  
+- Fix spurious segmentation faults when conflicts are logged to bdr.conflict_history  (BDR-2403, RT83436, RT83928)
   When conflicts are logged to the catalog bdr.conflict_history, the pglogical
   writer process may crash because of a segmentation fault due to an invalid
   pointer being used. Fix this usage.
 
-- Clean up the replication slot when bdr_init_physical fails (BDR-2364, RT74789)  
+- Clean up the replication slot when bdr_init_physical fails (BDR-2364, RT74789)
   If bdr_init_physical aborts without being able to join the node, it will
   leave behind an inactive replication slot. Remove such a replication slot
   when it is inactive before an irregular exit.
 
 ### Improvements
 
-- Allow consumption of the reserved galloc sequence slot (BDR-2367, RT83437, RT68255)  
+- Allow consumption of the reserved galloc sequence slot (BDR-2367, RT83437, RT68255)
   The galloc sequence slot reserved for future use by background allocator can
   be consumed in the presence of consensus failure.
 
@@ -227,27 +246,27 @@ that affect BDR as well.
 
 ### Resolved issues
 
--   Make ALTER TABLE lock the underlying relation only once (RT80204)  
+-   Make ALTER TABLE lock the underlying relation only once (RT80204)
     This avoids the ALTER TABLE operation falling behind in the queue
     when it released the lock in between internal operations. With this
     fix, concurrent transactions trying to acquire the same lock after
     the ALTER TABLE command will properly wait for the ALTER TABLE to
     finish.
 
--   Show a proper wait event for CAMO / Eager confirmation waits (BDR-1899, RT75900)  
+-   Show a proper wait event for CAMO / Eager confirmation waits (BDR-1899, RT75900)
     Show correct "BDR Prepare Phase"/"BDR Commit Phase" in `bdr.stat_activity`
     instead of the default “unknown wait event”.
 
--   Correct `bdr.monitor_local_replslots` for down nodes (BDR-2080)  
+-   Correct `bdr.monitor_local_replslots` for down nodes (BDR-2080)
     This function mistakenly returned an okay result for down nodes
     before.
 
--   Reduce log for bdr.run_on_nodes (BDR-2153, RT80973)  
+-   Reduce log for bdr.run_on_nodes (BDR-2153, RT80973)
     Don't log when setting `bdr.ddl_replication` to off if it's
     done with the "run_on_nodes" variants of function. This eliminates
     the flood of logs for monitoring functions.
 
--   Correct an SDW decoder restart edge case (BDR-2109)  
+-   Correct an SDW decoder restart edge case (BDR-2109)
     Internal testing revealed a possible error during WAL decoder
     recovery about mismatch between confirmed_flush LSN of WAL decoder
     slot also stating: "some LCR segments might be missing". This could
@@ -279,63 +298,63 @@ that affect BDR as well.
 ### Improvements
 
 -   Performance of COPY replication including the initial COPY during join has
-    been greatly improved for partitioned tables (BDR-1479)  
+    been greatly improved for partitioned tables (BDR-1479)
     For large tables this can improve the load times by order of magnitude or
     more.
 
--   Back-port `bdr.run_on_nodes()` and `bdr.run_on_group()` from BDR 4.0 (BDR-1433)  
+-   Back-port `bdr.run_on_nodes()` and `bdr.run_on_group()` from BDR 4.0 (BDR-1433)
     These functions behave same as `bdr.run_on_all_nodes()` but allow running SQL
     on specific group or set of nodes rather than all nodes.
 
--   Add execute_locally option to bdr.replicate_ddl_command (RT73533)  
+-   Add execute_locally option to bdr.replicate_ddl_command (RT73533)
     This allows optional queueing of ddl commands for replication to other groups
     without executing it locally.
 
--   Don't ERROR on consensus issue during JOIN  
+-   Don't ERROR on consensus issue during JOIN
     The reporting of these transient errors was confusing as they are shown in
     bdr.worker_errors. These are now changed to WARNINGs.
 
 ### Resolved issues
 
--   WAL decoder confirms end LSN of the running transactions record (BDR-1264)  
+-   WAL decoder confirms end LSN of the running transactions record (BDR-1264)
     Confirm end LSN of the running transactions record processed by WAL
     decoder so that the WAL decoder slot remains up to date and WAL senders
     get the candidate in timely manner.
 
--   Improve handling of node name reuse during parallel join (RT74789)  
+-   Improve handling of node name reuse during parallel join (RT74789)
     Nodes now have a generation number so that it's easier to identify the name
     reuse even if the node record is received as part of a snapshot.
 
 -   Fix locking and snapshot use during node management in the BDR manager
-    process (RT74789)  
+    process (RT74789)
     When processing multiple actions in the state machine, we make sure reacquire
     the lock on the processed node and update the snapshot to make sure any updates
     happening through consensus are taken into account.
 
--   Improve cleanup of catalogs on local node drop  
+-   Improve cleanup of catalogs on local node drop
     Drop all groups, not only the primary one and drop all the node state
     history info as well.
 
--   Don't wait for autopartition tasks to complete on parting nodes (BDR-1867)  
+-   Don't wait for autopartition tasks to complete on parting nodes (BDR-1867)
     When a node has started parting process, it makes no sense to wait for
     autopartition tasks on such nodes to finish since it's not part of the group
     anymore.
 
--   Ensure loss of CAMO partner connectivity switches to Local Mode immediately  
+-   Ensure loss of CAMO partner connectivity switches to Local Mode immediately
     This prevents disconnected partner from being reported as CAMO ready.
 
--   Fix the cleanup of `bdr.node_pre_commit` for async CAMO configurations (BDR-1808)  
+-   Fix the cleanup of `bdr.node_pre_commit` for async CAMO configurations (BDR-1808)
     Previously, the periodic cleanup of commit decisions on the CAMO
     partner checked the readiness of it's partner, rather than the
     origin node.  This is the same node for symmetric CAMO
     configurations, so those were not affected.  This release corrects
     the check for asymmetric CAMO pairings.
 
--   Improve error checking for join request in bdr_init_physical  
+-   Improve error checking for join request in bdr_init_physical
     Previously bdr_init_physical would simply wait forever when there was any issue
     with the consensus request, now we do same checking as the logical join does.
 
--   Improve handling of various timeouts and sleeps in consensus  
+-   Improve handling of various timeouts and sleeps in consensus
     This reduces amount of new consensus votes needed when processing many consensus
     requests or time consuming consensus requests, for example during join of a
     new node.
@@ -358,7 +377,7 @@ that affect BDR as well.
 
 ### Improvements
 
--   Reduce frequency of CAMO partner connection attempts (EE)  
+-   Reduce frequency of CAMO partner connection attempts (EE)
     In case of a failure to connect to a CAMO partner to verify its
     configuration and check the status of transactions, do not retry
     immediately (leading to a fully busy pglogical manager process), but
@@ -367,17 +386,17 @@ that affect BDR as well.
 
 -   Ensure CAMO configuration is checked again after a reconnect (EE)
 
--   Add dummy CAMO configuration catalogs and Raft support (BDR-1676)  
+-   Add dummy CAMO configuration catalogs and Raft support (BDR-1676)
     This is just to ease rolling upgrades from BDR 3.7 to 4.0.x on CAMO enabled
     installations.
 
--   Avoid unnecessary LCR segment reads (BDR-1426)  
+-   Avoid unnecessary LCR segment reads (BDR-1426)
     We'll now only attempt to read new LCR segments when there are some available.
     This should reduce I/O load when decoding worker is enabled.
 
 ### Resolved issues
 
--   Switch from CAMO to Local Mode only after timeouts (EE, RT74892)  
+-   Switch from CAMO to Local Mode only after timeouts (EE, RT74892)
     Do not use the `catchup_interval` estimate when switching from CAMO
     protected to Local Mode, as that could induce inadvertent switching
     due to load spikes.  Use the estimate only when switching from Local
@@ -385,25 +404,25 @@ that affect BDR as well.
     to lag on the CAMO partner).
 
 -   Prevent duplicate values generated locally by galloc sequence in high
-    concurrency situations when the new chunk is used (RT76528)  
+    concurrency situations when the new chunk is used (RT76528)
     The galloc sequence could have temporarily produce duplicate value when
     switching which chunk is used locally (but not across nodes) if there were
     multiple sessions waiting for the new value. This is now fixed.
 
 -   Ensure that the group slot is moved forward when there is only one node in
-    the BDR group  
+    the BDR group
     This prevents disk exhaustion due to WAL accumulation when the group is left
     running with just single BDR node for prolonged period of time. This is not
     recommended setup but the WAL accumulation was not intentional.
 
--   Advance Raft protocol version when there is only one node in the BDR group  
-    Single node clusters would otherwise always stay on oldest support protocol 
+-   Advance Raft protocol version when there is only one node in the BDR group
+    Single node clusters would otherwise always stay on oldest support protocol
     until another node was added. This could limit available feature set on that
     single node.
 
 ### Other changes
 
--   Add CAMO configuration infrastructure needed for upgrade to BDR4 (BDR-1676)  
+-   Add CAMO configuration infrastructure needed for upgrade to BDR4 (BDR-1676)
     Add dummy CAMO configuration infrastructure bdr.camo_pairs table
     and bdr.add/remove_camo_pair() functions to be able to upgrade a
     CAMO enabled cluster to BDR4
@@ -425,7 +444,7 @@ This is a hotfix release for BDR 3.7.13.
 
 -   Fix lag calculation for CAMO local mode delay (BDR-1681)
 
-## BDR 3.7.13 
+## BDR 3.7.13
 
 This is a maintenance release for BDR 3.7 that includes minor improvements
 as well as fixes for issues identified in previous versions.
@@ -435,17 +454,17 @@ BDR as well.
 
 ### Improvements
 
--   Use a separate replication origin for the BDR consensus process (BDR-1613)  
+-   Use a separate replication origin for the BDR consensus process (BDR-1613)
     For Eager transactions that need to COMMIT PREPARED from the consensus
     process, use a dedicated replication origin, this way
     the consensus does not conflict with writer origins.
 
--   Improve documentation of the backup/restore procedure (RT72503, BDR-1340)  
+-   Improve documentation of the backup/restore procedure (RT72503, BDR-1340)
     Recommend against dropping the extension with cascade because
     it may drop user columns that are using CRDT types and break
     the sequences. It's better to use `drop_node` function instead.
 
--   Add function `bdr.get_decoding_worker_stat()` (BDR-1302)  
+-   Add function `bdr.get_decoding_worker_stat()` (BDR-1302)
     If the Decoding Worker is enabled, this function shows information
     about the state of the Decoding Worker associated with the current
     database. This also provides more granular information about
@@ -453,23 +472,23 @@ BDR as well.
 
 ### Resolved issues
 
--   Fix a subscriber-side memory leak when bulk-inserting into a partitioned table (BDR-1473)  
+-   Fix a subscriber-side memory leak when bulk-inserting into a partitioned table (BDR-1473)
     This improves memory usage during node join when there are
     partitioned tables present.
 
--   Fix `bdr.alter_sequence_set_kind` to accept a bigint as a start value (RT74294)  
+-   Fix `bdr.alter_sequence_set_kind` to accept a bigint as a start value (RT74294)
     The function was casting the value to an `int` thus getting bogus values
     when `bigint` was used.
 
--   Fix memory leak from consensus worker of Raft leader (RT74769)  
+-   Fix memory leak from consensus worker of Raft leader (RT74769)
     The tracing context was leaked causing growing memory usage from the consensus,
     on BDR groups with many nodes, this could cause memory exhaustion.
 
--   Enable async conflict resolution for explicit 2PC (BDR-1666, RT71298)  
+-   Enable async conflict resolution for explicit 2PC (BDR-1666, RT71298)
     Continue applying the transaction using the async conflict resolution
     for explicit two phase commit.
 
--   Fix potential crash if `bdr.receive_lcr` is "false" (BDR-1620)  
+-   Fix potential crash if `bdr.receive_lcr` is "false" (BDR-1620)
     Adust Single Decoding Worker feature to automatically disable
     itself if the `bdr.receive_lcr` is "false". This prevents crash
     situation when starting replication from a peer in the
@@ -478,7 +497,7 @@ BDR as well.
 
 ### Other changes
 
--   Add deprecation hint for `bdr.group_max_connections` (BDR-1596)  
+-   Add deprecation hint for `bdr.group_max_connections` (BDR-1596)
     Allow `bdr.group_max_connections` option, but make sure it's properly marked
     as deprecated in favor of `bdr.raft_group_max_connections`. This GUC will
     be removed in BDR 4.0.
@@ -500,14 +519,14 @@ BDR as well.
 
 ### Improvements
 
--   Tweak Single Decoding performance by caching and better locking (BDR-1311, BDR-1312)  
+-   Tweak Single Decoding performance by caching and better locking (BDR-1311, BDR-1312)
     Add caching for BDR-internal catalog information about the Decoding
     Worker.  Split a single global lock into multiple locks (one per WAL
     sender) for access to internal status information of the WAL sender.
     This improves performance especially with many concurrent WAL sender
     processes.
 
--   Add a new view bdr.replication_status (BDR-1412)  
+-   Add a new view bdr.replication_status (BDR-1412)
     This is similar to the view `pglogical.replication_status` and shows
     information about the replication status of the local node with
     respect to all other BDR nodes in the cluster.
@@ -517,18 +536,18 @@ BDR as well.
     by a Decoding Worker, and if so the name of the LCR file currently being read
     from.
 
--   Prevent CAMO to be used in combination with Decoding Worker (BDR-792)  
+-   Prevent CAMO to be used in combination with Decoding Worker (BDR-792)
     These features cannot currently work in combination.  This release
     prevents enabling them both in many cases.  This is just a
     best-effort strategy to prevent mis-configuration.
 
--   Allow to specify a postgresql.auto.conf file for `bdr_init_physical` (RT72989, BDR-1400)  
+-   Allow to specify a postgresql.auto.conf file for `bdr_init_physical` (RT72989, BDR-1400)
     Add a command line argument to `bdr_init_physical` allowing to
     provide a custom file to be used for `postgresql.auto.conf`.
 
 ### Resolved issues
 
--   Fix a potential data loss issue with bdr_init_physical (RT71888)  
+-   Fix a potential data loss issue with bdr_init_physical (RT71888)
     When reusing a slot name, previous state was not properly cleaned up
     in all cases.  This has caused potential data loss during physical
     join as the slot is created ahead of time by `bdr_init_physical`
@@ -537,7 +556,7 @@ BDR as well.
     and recreates the slot.  This release properly cleans slot
     information when dropped and thereby prevents data loss.
 
--   Fix `bdr.camo_local_mode_delay` to really kick in (BDR-1352)  
+-   Fix `bdr.camo_local_mode_delay` to really kick in (BDR-1352)
     This artificial delay allows throttling a CAMO node that is not
     currently connected to its CAMO partner to prevent it from producing
     transactions faster than the CAMO partner can possibly apply.  In
@@ -545,19 +564,19 @@ BDR as well.
     `bdr.global_commit_timeout` amount of lag, but only 1000 times
     later (due to erroneously comparing seconds to milliseconds).
 
--   Prevent segfault in combination with third-party output plugins (BDR-1424, RT72006)  
+-   Prevent segfault in combination with third-party output plugins (BDR-1424, RT72006)
     Adjust handling of logical WAL messages specific to BDR's Eager All
     Node Replication mode for output plugins unrelated to BDR.  This
     allows for example Debezium's decoderbufs output plugin to work
     alongside BDR.
 
--   Improve compatibility with Postgres 13 (BDR-1396)  
+-   Improve compatibility with Postgres 13 (BDR-1396)
     Adjust to an API change in ReplicationSlotAcquire that may have led
     to unintended blocking when non-blocking was requestend and vice
     versa.  This version of PGLogical eliminates this potential problem,
     which has not been observed on production systems so far.
 
--   Fix serialization of Raft snapshots including commit decisions (CAMO, BDR-1454)  
+-   Fix serialization of Raft snapshots including commit decisions (CAMO, BDR-1454)
     A possible mismatch in number of tuples could lead to serialization
     or deserialization errors for a Raft snapshot taken after
     transactions using CAMO or Eager All Node replication were used
@@ -584,23 +603,23 @@ BDR as well.
 
 -   Reduce debug logging of decoding worker (BDR-1236, BDR-1239)
 
--   Allow configuration of maximum connections for consensus (BDR-1005)  
+-   Allow configuration of maximum connections for consensus (BDR-1005)
     This allows for setting up very large clusters.
 
 ### Resolved issues
 
--   Fix snapshot handling in autopatition and executor  
+-   Fix snapshot handling in autopatition and executor
     For compatibility with latest version of PostgreSQL
 
--   Fix deadlock handling in CAMO  
+-   Fix deadlock handling in CAMO
     This solves issue with extremely slow resolution of conflicts in cross-CAMO
     setup.
 
--   Get copy of slot tuple when logging conflict (BDR-734)  
+-   Get copy of slot tuple when logging conflict (BDR-734)
     Otherwise we could materialize the row early causing wrong update in presence
     of additional columns on the downstream.
 
--   Improve LCR segment removal logic (BDR-1180, BDR-1183, BDR-993, BDR-1181)  
+-   Improve LCR segment removal logic (BDR-1180, BDR-1183, BDR-993, BDR-1181)
     Make sure we keep LCR segments for all the LSN that is the smaller between
     group slot LSN and the decoding worker slot LSN.
 
@@ -625,7 +644,7 @@ as well as fixes for issues identified in previous versions.
     Return "CRITICAL" status in `bdr.monitor_group_raft()` if at least
     half of the voting nodes are unreachable.
 
--   Allow `bdr_monitor` role to read additional informational views. (BDR-732)  
+-   Allow `bdr_monitor` role to read additional informational views. (BDR-732)
     -   `bdr.group_camo_details`
     -   `bdr.group_versions_details`
     -   `bdr.group_raft_details`
@@ -639,21 +658,21 @@ as well as fixes for issues identified in previous versions.
 
 -   Make the consensus worker always exit if postmaster dies (BDR1063, RT70024)
 
--   Fix starting LSN of Decoding Worker after a restart  
+-   Fix starting LSN of Decoding Worker after a restart
     When the Decoding Worker restarts, it scans the existing LCR segments to find
     the LSN, transactions upto which, are completely decoded. If this LSN is
     higher than the slot's confirmed LSN, it updates the slot before decoding any
     transactions. This avoids transactions being decoded and replicated multiple
     times. (BDR-876, RT71345)
 
--   Do not synchronize Decoding Worker's replication slot on a physical standby  
+-   Do not synchronize Decoding Worker's replication slot on a physical standby
     When the WAL decoder starts the first time, the Decoding Worker's slot needs
     to be behind all the WAL sender slots so that it decodes the WAL required by
     the WAL senders. But the slot on primary has moved ahead of all WAL senders
     so synchronizing it is not useful. It is created anew after the physical
     standby is promoted. (BDR-738)
 
--   Improve join performance when Decoding Worker is enabled  
+-   Improve join performance when Decoding Worker is enabled
     When `fsync` = `on`, joining a new node to a cluster takes much longer with
     Decoding Worker enabled. Also WAL buildup is observed on the node used as the
     source of join. This was because the Decoding Worker synced the LCR segments
@@ -662,25 +681,25 @@ as well as fixes for issues identified in previous versions.
 
 -   Fix TOAST handling for UPDATE/UPDATE conflicts when Decoding Worker is used
 
--   Fix filtering of additional origins when Decoding Worker is used  
+-   Fix filtering of additional origins when Decoding Worker is used
     This mostly affects mixing BDR with Decoding Worker and a separate pglogical
     replication.
 
--   Eliminate potential hang in `bdr.raft_leadership_transfer` (BDR-1039)  
+-   Eliminate potential hang in `bdr.raft_leadership_transfer` (BDR-1039)
     In combination with `wait_for_completion`, the best effort approach led
     to an infinite loop in case the original request was submitted properly,
     but the actual leadership transfer still failed.
 
--   Do not throw an error when PGL manager can not start a worker (RT71345)  
+-   Do not throw an error when PGL manager can not start a worker (RT71345)
     If PGL manager throws an error, it is restarted. Since it's responsible
     for maintaining the node states and other BDR management tasks
     restarting it on such errors affects the EDB Postgres Distributed cluster's health.
     Instead log a WARNING.
 
--   Make the repset configuration handling during join more deterministic (RT71021)  
+-   Make the repset configuration handling during join more deterministic (RT71021)
     The `autoadd_tables` option might not be respected in all cases before.
 
--   Deprecate `pub_repsets` and `sub_repsets` in bdr.node_summary (BDR-702, RT70743)  
+-   Deprecate `pub_repsets` and `sub_repsets` in bdr.node_summary (BDR-702, RT70743)
     They now always show `NULL` rather than bogus info, will be removed completely
     in next major version.
 
@@ -700,20 +719,20 @@ as well as fixes for issues identified in previous versions.
 ### Improvements
 
 -   Add `bdr.local_group_slot_name()` function which returns the group slot
-    name (BDR-931)  
+    name (BDR-931)
     Useful primarily for monitoring.
 
 -   Add `bdr.workers` view which show additional information about BDR workers
-    (BDR-725)  
+    (BDR-725)
     Helps with monitoring of BDR specific activity. Useful especially when joined
     with `bdr.stat_activity`.
 
--   Allow Parallel Apply on logical standbys for forwarded transaction (BDR-852)  
+-   Allow Parallel Apply on logical standbys for forwarded transaction (BDR-852)
     Previously, parallel apply would could be used only for changes replicated
     directly from the upstream of the logical standby, but not for any changes
     coming from another node.
 
--   Introduce `bdr.batch_inserts` configuration variable (RT71004, RT70727)  
+-   Introduce `bdr.batch_inserts` configuration variable (RT71004, RT70727)
     This sets after how many `INSERT`s into same table in a row (in same transaction)
     BDR will switch to multi insert strategy.
 
@@ -743,37 +762,37 @@ as well as fixes for issues identified in previous versions.
     only when the node reaches PROMOTE state. That's the state when other
     nodes may start connecting to the node and hence need WAL decoder.
 
--   Fix group slot advance on subscriber-only nodes (BDR-916, BDR-925, RT71182)  
+-   Fix group slot advance on subscriber-only nodes (BDR-916, BDR-925, RT71182)
     This solves excessive WAL log retention on subscriber-only nodes.
 
 -   Use correct slot name when joining subscriber-only node using
-    `bdr_init_physical` (BDR-895, BDR-898, RT71124)  
+    `bdr_init_physical` (BDR-895, BDR-898, RT71124)
     The `bdr_init_physical` used to create wrong slot, which resulted in 2 slots
     existing on the join source node when subscriber-only node was joined using
     this method. This would result in excessive WAL retention on the join source
     node.
 
--   Fix group monitoring view to allow more than one row per node (BDR-848)  
+-   Fix group monitoring view to allow more than one row per node (BDR-848)
     Group monitoring views would previously truncate the information from any node
     reporting more than one row of information. This would result in for example
     slots missing in `bdr.group_replslots_details`.
 
--   Correct commit cancellation for CAMO (BDR-962()  
+-   Correct commit cancellation for CAMO (BDR-962()
     This again corrects CAMO behaviour when a user cancels a query.
 
--   Restore global lock counters state after receiver restart (BDR-958)  
+-   Restore global lock counters state after receiver restart (BDR-958)
     We already restored locks themselves but not the counters which could cause
     deadlocks during global locking when using parallel apply.
 
 -   Fix handling of `skip_transaction` conflict resolver when there are multiple
     changes in the transaction after the one that caused the `skip_transaction` (BDR-886)
 
--   Fix Raft snapshot creation for autopartitioned tables (RT71178, BDR-955)  
+-   Fix Raft snapshot creation for autopartitioned tables (RT71178, BDR-955)
     Previously the Raft snapshot didn't take into account state of autopartition
     tasks on all nodes when writing the information. This could result in some
     nodes skipping partition creation after prolonged period of downtime.
 
--   Adjust transaction and snapshot handling in autopartition (BDR-903)  
+-   Adjust transaction and snapshot handling in autopartition (BDR-903)
     This ensures valid snapshot is used during autopartition processing at all
     times. The previous approach would cause problem in the future point release
     of PostgreSQL.
@@ -785,19 +804,19 @@ as well as fixes for issues identified in previous versions.
 -   Ensure that correct sequence type is always set in the global galloc
     sequence state.
 
--   Fix DDL replication and locking management of several commands (BDR-874)  
+-   Fix DDL replication and locking management of several commands (BDR-874)
     `ANALYZE`, `CHECKPOINT`, `CLUSTER`, `PREPARE`/`COMMIT`/`ABORT` `TRANSACTION`,
     `MOVE`, `RELEASE`, `ROLLBACK` were documented as replicated and some of these
     even tried to take DDL lock which they should not.
 
--   Reduce logging of some unreplicated utility commands (BDR-874)  
+-   Reduce logging of some unreplicated utility commands (BDR-874)
     `PREPARE` and `EXECTUE` don't need to spam about not being replicated as nobody
     expects that they would be.
 
--   Fix global locking of `ALTER TABLE ... SET` (BDR-653)  
+-   Fix global locking of `ALTER TABLE ... SET` (BDR-653)
     It should not take global DML lock.
 
--   Fix documentation about how `TRUNCATE` command is replicated (BDR-874)  
+-   Fix documentation about how `TRUNCATE` command is replicated (BDR-874)
     While `TRUNCATE` can acquire global locks, it's not replicated the way other
     DDL commands are, it's replicated like DML, according to replication set
     settings.
@@ -823,27 +842,27 @@ Upgrades are supported from BDR 3.6.25 and 3.7.7 in this release.
 
 -   Support for PostgreSQL 11, 12 and 13
 
--   Support EDB Advanced Server  
+-   Support EDB Advanced Server
     Both Standard Edition and Enterprise Edition are now available to use with
     EDB Advanced Server
 
--   Parallel Apply  
+-   Parallel Apply
     Allows configuring number of parallel writers that apply the replication
     stream. This is feature is supported in Enterprise Edition only.
 
--   AutoPartition  
+-   AutoPartition
     Allows automatic management of partitioned tables, with automated creation,
-    automated cleanup with configurable retention periods and more.  
+    automated cleanup with configurable retention periods and more.
 
--   Introduce option to separate BDR WAL decoding worker  
+-   Introduce option to separate BDR WAL decoding worker
     This allows using single decoding process on each node, regardless of number
-    of subscriptions connected to it.  
+    of subscriptions connected to it.
     The decoded information is stored in logical change record (LCR) files which
     are streamed to the other nodes in similar way traditional WAL is.
-    Optional separation of decoding from walsender.  
+    Optional separation of decoding from walsender.
     This is feature is supported in Enterprise Edition only.
 
--   Implement the concept of `subscriber-only` nodes  
+-   Implement the concept of `subscriber-only` nodes
     These are wholly joined nodes, but they don't ever send replication
     changes to other BDR nodes in the cluster. But they do receive changes
     from all nodes in the cluster (except, of course the other subscriber-only
@@ -853,32 +872,32 @@ Upgrades are supported from BDR 3.6.25 and 3.7.7 in this release.
     don't send replication changes. Similarly, we don't need to create any
     subscriptions for these nodes on other BDR nodes.
 
--   Support `CREATE TABLE ... AS` and `SELECT INTO` statement  
+-   Support `CREATE TABLE ... AS` and `SELECT INTO` statement
     This feature is now supported in Enterprise Edition only.
 
 -   New ability to define BDR sub-groups in order to better represent physical
-    configuration of the EDB Postgres Distributed cluster.  
+    configuration of the EDB Postgres Distributed cluster.
     This also simplifies configurations where the EDB Postgres Distributed cluster is spread over
     multiple data centers and only part of the database is replicated across
     data centers as each subgroup will automatically have new default replication
     set assigned to it.
 
--   Multiple new monitoring views  
+-   Multiple new monitoring views
     Focused primarily on group level monitoring and in-progress monitoring on
     the apply side.
 
--   Conflicts are now logged by default to `bdr.conflict_history`  
+-   Conflicts are now logged by default to `bdr.conflict_history`
     Logging to a partitioned table with row level security to allow easier
     access to conflicts for application users.
 
--   New conflict types `multiple_unique_conflicts` and `apply_error_ddl`  
+-   New conflict types `multiple_unique_conflicts` and `apply_error_ddl`
     Allows continuing replication in more edge case situations
 
--   Reduced lock levels for some DDL statements  
+-   Reduced lock levels for some DDL statements
     Also, documented workarounds that help with reducing lock levels for
     multiple other DDL statements.
 
--   Use best available index when applying update and delete  
+-   Use best available index when applying update and delete
     This can drastically improve performance for `REPLICA IDENTITY FULL` tables
     which don't have primary key.
 
@@ -888,19 +907,19 @@ Following are changes since 3.7.7.
 
 -   Support Parallel Apply in EDB Advanced Server (EE)
 
--   Increase progress reporting frequency when needed (BDR-436, BDR-522)  
+-   Increase progress reporting frequency when needed (BDR-436, BDR-522)
     This helps speed up the performance of  VALIDATE CONSTRAINT without DML
     locking.
 
 -   Change all BDR configuration options that are settable from SQL session to be
     settable by `bdr_superuser` rather than only Postgres superuser.
 
--   Set bdr.ddl_replication to off in `bdr.run_on_all_nodes()` (BDR-445)  
+-   Set bdr.ddl_replication to off in `bdr.run_on_all_nodes()` (BDR-445)
     It's usually not desirable to replicate any DDL executed using the
     `bdr.run_on_all_nodes()` function as it already runs it on all nodes.
 
 -   Improve monitoring of transactions that are in progress on apply side
-    (BDR-690, BDR-691)  
+    (BDR-690, BDR-691)
     Add query to pg_stat_activity when applying DDL and several additional
     fields to `bdr.subscription_summary` view which show LSN of latest received
     change, LSN of latest received commit, applied commit LSN, flushed LSN and
@@ -912,7 +931,7 @@ Following are changes since 3.7.7.
 -   Add view `bdr.stat_activity`, similar to `pg_stat_activity` but shows BDR
     specific wait states.
 
--   Allow batching inserts outside of the initial data sync  
+-   Allow batching inserts outside of the initial data sync
     Improves performance of big data loads into existing BDR Group.
 
 -   Reduce the global lock level obtained by DROP INDEX from DML Global Lock to
@@ -920,55 +939,55 @@ Following are changes since 3.7.7.
 
 ### Resolved issues
 
--   Fix replication settings of several DDL commands  
+-   Fix replication settings of several DDL commands
     In general make sure that actual behavior and documented behavior for
     what's allowed, what's replicated and what locks are held during DDL
     replication match.
 
     For example TABLESPACE related commands should not be replicated.
 
--   Fix a race condition in concurrent join. (BDR-644, BDR-645)  
+-   Fix a race condition in concurrent join. (BDR-644, BDR-645)
     Always create initially enabled subscription if the local node has already
     crossed the PROMOTING state.
 
--   Set group leader for already held lock (BDR-418, BDR-291)  
+-   Set group leader for already held lock (BDR-418, BDR-291)
     This solves "canceling statement due to global lock timeout" during some
     DDL operations when the writer already had open table before. This was
     especially problem when partitioning or parallel apply is involved.
 
--   Progress WAL sender's slot based on WAL decoder input (BDR-567)  
+-   Progress WAL sender's slot based on WAL decoder input (BDR-567)
     Without this, server could eventually stop working with single decoding worker.
 
--   Switch to TEMPORARY replication slots in `bdr_init_physical` (BDR-191)  
+-   Switch to TEMPORARY replication slots in `bdr_init_physical` (BDR-191)
     This ensures they are properly cleaned up after `bdr_init_physical` is done.
 
--   Clean up XID progress records that are no longer required (BDR-436, BDR-532)  
+-   Clean up XID progress records that are no longer required (BDR-436, BDR-532)
     Reduces the size of the xid progress snapshot.
 
--   Track applied_timestamp correctly in BDR Writer (BDR-609)  
+-   Track applied_timestamp correctly in BDR Writer (BDR-609)
     It was not updated in 3.7.7
 
--   Fix creation of BDR Stream triggers on EPAS (BDR-581)  
+-   Fix creation of BDR Stream triggers on EPAS (BDR-581)
     They used to be created as wrong trigger type.
 
 -   Improve error handling when options stored in LCR file and passed to walsender
     differ (BDR-551)
 
--   Enable WAL decoder config only for top node group (BDR-566)  
+-   Enable WAL decoder config only for top node group (BDR-566)
     We only allow group configuration changes for top node group in general.
 
--   Use "C" collation or "name" type for specific BDR catalog columns (BDR-561)  
+-   Use "C" collation or "name" type for specific BDR catalog columns (BDR-561)
     This solves potential index collation issues for BDR catalogs.
 
--   Correct commit cancellation for CAMO  
+-   Correct commit cancellation for CAMO
     This fixes CAMO behavior when user cancels a query.
 
 -   Fix autopartition handling of tables with already existing partitions (BDR-668)
 
--   Don't cache relation with no remote id in BDRWrite (BDR-620)  
+-   Don't cache relation with no remote id in BDRWrite (BDR-620)
     Fixes replication breakage after some forms of TRUNCATE command.
 
--   Craft upstream decoder slot name considering upstream dbname in wal decoder (BDR-460)  
+-   Craft upstream decoder slot name considering upstream dbname in wal decoder (BDR-460)
     Fixes slot names used by wal decoder.
 
 -   Use correct BDR output options used by WAL decoder and WAL sender using LCR (BDR-714)
@@ -977,10 +996,10 @@ Following are changes since 3.7.7.
 
 -   Don't show nonexisting slots for PARTED in bdr.node_slots view
 
--   Drop Stream Trigger when dropping node (BDR-692)  
+-   Drop Stream Trigger when dropping node (BDR-692)
     This enables use of `bdr_init_physical` with Stream Triggers.
 
--   Ensure we don't segfault while handling a SIGUSR2 signal  
+-   Ensure we don't segfault while handling a SIGUSR2 signal
     Signals can come at any point in process lifetime so don't make any
     assumptions about the current state.
 
@@ -989,12 +1008,12 @@ Following are changes since 3.7.7.
 
 -   Make sure we don't crash when we get ERROR during handing of different ERROR
 
--   Don't send global xid to client if we are in background worker  
+-   Don't send global xid to client if we are in background worker
     There is nobody to send this.
 
 ### Other changes
 
--   Allow session-level bdr.xact_replication = off when bdr.permit_unsafe_commands is on  
+-   Allow session-level bdr.xact_replication = off when bdr.permit_unsafe_commands is on
     Helps when using `pg_restore` to manually populate the database.
 
 -   Various larger documentaion improvements
@@ -1003,15 +1022,15 @@ Following are changes since 3.7.7.
     not in the repset already (BDR-562)
 
 -   Allow `check_constraints` option again, but make sure it's properly marked
-    as deprecated (BDR-26)  
+    as deprecated (BDR-26)
     Will be removed in BDR 4.0.
 
 -   Move the management of WAL senders when WAL decoder is enabled/disabled to
-    manager process (BDR-612)  
+    manager process (BDR-612)
     Managing them in consensus worker could negatively affect responsiveness of
     consensus subsystem.
 
--   Check for interrups in more places  
+-   Check for interrups in more places
     Should reduce chance of runaway loops
 
 ## BDR 3.7.7 (2021 Apr 08)
@@ -1030,31 +1049,31 @@ Upgrades are supported from BDR 3.6.25 and 3.7.6 in this release.
 
 ### Improvements
 
--   Support Enterprise Edition features on EDB Advanced Server  
+-   Support Enterprise Edition features on EDB Advanced Server
     This notably excludes CAMO and Eager replication.
 
--   Support most of the EDB Advanced Server DDL commands (EBC-45)  
+-   Support most of the EDB Advanced Server DDL commands (EBC-45)
     Note that DDL related to queues is replicated, but the contents of queues
     are not replicated.
 
 -   Adjust DDL replication handling to follow more on command level rather than
-    internal representation (BDR-275)  
+    internal representation (BDR-275)
     This mainly makes filtering and documentation easier.
 
 -   Allow SELECT INTO statement in Enterprise Edition (BDR-306)
 
--   Handle BDR sequences in COPY FROM (BDR-466)  
+-   Handle BDR sequences in COPY FROM (BDR-466)
     COPY FROM does it's own processing of column defaults which
     does not get caught by query planner hook as it only uses
     expression planner. Sadly, expression planner has no hook
     so we need to proccess the actual COPY FROM command itself.
 
--   Improve bdr.run_on_all_nodes(BDR-326, BDR-303)  
+-   Improve bdr.run_on_all_nodes(BDR-326, BDR-303)
     Change return type to jsonb, always return status of each command,
     Improve error reporting by returning the actual error message received from
     remote server.
 
--   Add more info to conflict_history (BDR-440)  
+-   Add more info to conflict_history (BDR-440)
     This adds couple new fields to the conflict history table for easier
     identification of tuples without having to look at the actual data.
 
@@ -1072,29 +1091,29 @@ Upgrades are supported from BDR 3.6.25 and 3.7.6 in this release.
     local_time is the partition key of bdr.conflict_history,
     which we need to allow monitoring queries to execute efficiently.
 
--   Add --node-group-name option to bdr_init_physical  
+-   Add --node-group-name option to bdr_init_physical
     Same as node_group_name in bdr.join_node_group - allows joining
     sub-group of a node.
 
--   Store LCRs under directory named after WAL decoder slot (BDR-60)  
+-   Store LCRs under directory named after WAL decoder slot (BDR-60)
     Pglogical stores LCR in a directory named after the replication slot
     used to produce those.
 
 -   Various improvements in WAL decoder/sender coordination (BDR-232, BDR-335,
-    BDR-342)  
+    BDR-342)
     We now expose the information about WALDecoder waitlsn and let WALSender
     use that information to wait and signal the WALDecoder when the required
     WAL is available. This avoids the unnecessary polling and improves
     coordinator between the two.
 
--   Single Decoder Worker GUC Option Changes. (BDR-222)  
+-   Single Decoder Worker GUC Option Changes. (BDR-222)
     Changed `bdr.receive_logical_change_records` to `bdr.receive_lcr` and
     `bdr.logical_change_records_cleanup_interval` to `bdr.lcr_cleanup_interval`
 
--   Move most of the CAMO/Eager code into BDR (BDR-330)  
+-   Move most of the CAMO/Eager code into BDR (BDR-330)
     Makes CAMO and Eager All Node less dependent on Postgres patches.
 
--   Support the parallelization of initial sync.  
+-   Support the parallelization of initial sync.
     When parallel apply is enabled, the initial sync during logical join will
     be paralellized as well.
 
@@ -1102,16 +1121,16 @@ Upgrades are supported from BDR 3.6.25 and 3.7.6 in this release.
 
 ### Resolved issues
 
--   Fix logic in `bdr_stop_wal_decoder_senders()` (BDR-232)  
+-   Fix logic in `bdr_stop_wal_decoder_senders()` (BDR-232)
     Increase the period for which bdr_stop_wal_decoder_senders() should wait
     before checking status of WAL sender again.
 
--   Disallow running ALTER TABLE..ADD FOREIGN KEY in some cases (EBC-38,BDR-155)  
+-   Disallow running ALTER TABLE..ADD FOREIGN KEY in some cases (EBC-38,BDR-155)
     If the current user does not have permissions to read the
     referenced table, disallow the ALTER TABLE ADD FOREIGN KEY
     to such a table
 
--   Improve detection of queries which mix temporary and permanent objects  
+-   Improve detection of queries which mix temporary and permanent objects
     These need to be disallowed otherwise they could break replication.
 
 -   Fix EXPLAIN statement when using INTO TABLE clause.
@@ -1120,20 +1139,20 @@ Upgrades are supported from BDR 3.6.25 and 3.7.6 in this release.
 
 -   Fix CTAS handling on older minor versions of EPAS
 
--   Consolidate table definition checks (BDR-24)  
+-   Consolidate table definition checks (BDR-24)
     This fixes several hidden bugs where we'd miss the check or creation
     of extra object
 
--   Fix REINDEX and DROP index on an invalid index (BDR-155, EBC-41)  
+-   Fix REINDEX and DROP index on an invalid index (BDR-155, EBC-41)
     REINDEX throws error if index is invalid. Users can drop invalid
     indexes using DROP index if_exists.
 
--   Improve checks for local node group membership (BDR-271)  
+-   Improve checks for local node group membership (BDR-271)
     Couple of functions, namely `bdr_wait_for_apply_queue` and
     `bdr_resynchronize_table_from_node` didn't do this check,
     potentially causing a crash.
 
--   Corrected misleading CTAS ERROR  
+-   Corrected misleading CTAS ERROR
     In case of underlying un-supported or non-replicated utility, we
     should error out and should mention the underlying utility.
 
@@ -1159,7 +1178,7 @@ Upgrades are supported from BDR 3.6.25 in this release.
 ### Improvements
 
 -   Introduce option to separate BDR WAL decoding worker
-    (RM18868, BDR-51, BDR-58)  
+    (RM18868, BDR-51, BDR-58)
     This allows using single decoding process on each node, regardless of number
     of subscriptions connected to it.
     The decoded information is stored in logical change record (LCR) files which
@@ -1167,30 +1186,30 @@ Upgrades are supported from BDR 3.6.25 in this release.
 
 -   Enable parallel apply for CAMO and Eager (RM17858)
 
--   Rework relation caching in BDRWriter  
+-   Rework relation caching in BDRWriter
     This fixes missed invalidations that happened between our cache lookup
     and table opening.
     We also reduced the amount of hash table lookups (improving performance).
 
 -   Don't allow mixing temporary and permanent object in single DDL command
-    (BDR-93)  
+    (BDR-93)
     It's important to not try to replicate DDLs that work with temporary objects
     as such DDL is sure to break replication.
 
--   Add bdr.alter_subscription_skip_changes_upto() (BDR-76)  
+-   Add bdr.alter_subscription_skip_changes_upto() (BDR-76)
     Allows skipping replication changes up to given LSN for a specified
     subcription. Similar function already exists in pglogical.
 
--   Make the snapshot entry handler lookup more robust (BDR-86)  
+-   Make the snapshot entry handler lookup more robust (BDR-86)
     This should make it harder to introduce future bugs with consensus snapshot
     handling.
 
--   Add bdr.consensus_snapshot_verify() (BDR-124)  
+-   Add bdr.consensus_snapshot_verify() (BDR-124)
     Can be used to verify that consensus snapshot provided is correct before
     passing it to bdr.consensus_snapshot_import().
 
 -   Add support for most DDL commands that are specific to
-    EDB Postgres Advanced Server (EBC-39, EBC-40)  
+    EDB Postgres Advanced Server (EBC-39, EBC-40)
 
 -   Reduce WARNING spam on non-replicated commands that are not expected to be
     replicated in the first place (like VACUUM)
@@ -1199,56 +1218,56 @@ Upgrades are supported from BDR 3.6.25 in this release.
 
 ### Resolved issues
 
--   Make sure we have xid assigned before opening relation in writer  
+-   Make sure we have xid assigned before opening relation in writer
     This should improve deadlock detection for parallel apply
 
--   Check table oid in function drop_trigger (BDR-35)  
+-   Check table oid in function drop_trigger (BDR-35)
     Fixes crash when invalid oid was passed to the function.
 
--   Fix application of older consensus snapshots (BDR-231)  
+-   Fix application of older consensus snapshots (BDR-231)
     We used to not handle missing group UUID correctly resulting in 3.7 node
     not being able to join 3.6 cluster.
 
--   Readjust default truncate handling (BDR-25)  
+-   Readjust default truncate handling (BDR-25)
     Don't take lock by default. While this can cause potential out of order
     truncation, it presents better backwards compatibility.
 
 -   Fix crash when OPTION clause is used in CREATE FOREIGN TABLE statement
-    (EBC-37)  
+    (EBC-37)
 
 -   Ensure that we don't send extra data while talking to node with old
-    consensus protocol (BDR-135)  
+    consensus protocol (BDR-135)
 
--   Read kv_data part of consensus snapshot in mixed version group (BDR-130)  
+-   Read kv_data part of consensus snapshot in mixed version group (BDR-130)
     Both BDR 3.6. and 3.7 write this part of consensus snapshot but BDR 3.7
     would only read it if the snapshot was also written by 3.7.
 
--   Move bdr.constraint to EE script (EBC-36)  
+-   Move bdr.constraint to EE script (EBC-36)
     It's Enterprise Edition only feature so the catalog should only be installed
     with Enterprise Edition.
 
 -   Don't try to replicate GRANT/REVOKE commands on TABLESPACE and Large
-    Objects  
+    Objects
     These objects are not replicated so trying to replicate GRANT and REVOKE would
     break replication.
 
--   Make sure CAMO does not block replay progress (RT69493)  
+-   Make sure CAMO does not block replay progress (RT69493)
 
--   Fix failed CAMO connection handling (RT69493, RM19924)  
+-   Fix failed CAMO connection handling (RT69493, RM19924)
     Correct the state machine to properly cleanup and recover from this
     failure and reset to the UNUSED & IDLE state.
 
--   Don't accept Raft request from unknown nodes  
+-   Don't accept Raft request from unknown nodes
     Consensus leader should not accept raft request from nodes it does not know.
 
--   Don't try to negotiate consensus protocol on unknown node progress (RT69779)  
+-   Don't try to negotiate consensus protocol on unknown node progress (RT69779)
     When node is forcefully dropped, we might still receive progress message from
     it. This has to gracefully ignore such message otherwise consensus could break
     in such situation.
 
 ### Other changes
 
--   Remove code unsupported consensus protocols (BDR-86)  
+-   Remove code unsupported consensus protocols (BDR-86)
 
 ## BDR 3.7.5 (2021 Jan 19)
 
@@ -1269,7 +1288,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
 
 -   Reduce "now supports consensus protocols" log spam. (RT69557)
 
--   Extend `bdr.drop_node` with a `node_state` check. (RM19280)  
+-   Extend `bdr.drop_node` with a `node_state` check. (RM19280)
     Adds a new argument 'force' to `bdr.drop_node`, defaulting to false,
     in which case the following additional check is performed:
     Via `bdr.run_on_all_nodes`, the current `node_state` of the node to
@@ -1280,17 +1299,17 @@ Upgrades are supported from BDR 3.6.22 in this release.
     now we have two distinct options, one to skip sanity checks (force) and
     one to cascade to dependent objects (cascade).
 
--   Deprecate `pg2q.enable_camo` (RM19942, RT69521)  
+-   Deprecate `pg2q.enable_camo` (RM19942, RT69521)
     The parameter has been changed in 3.7 to the new `bdr.enable_camo`.
 
 -   Add new parameter `detector_args` to `bdr.alter_table_conflict_detection`
-    (RT69677)  
+    (RT69677)
     Allow additional parameters for individual detectors.
     Currently just adds atttype for row_version which allows using
     smallint and bigint, not just the default integer for the column
     type.
 
--   Add `bdr.raft_leadership_transfer` (RM20159)  
+-   Add `bdr.raft_leadership_transfer` (RM20159)
     Promote a specific node as the Raft leader.
     Per Raft paper, transferring leadership to a specific node can be done by
     the following steps:
@@ -1308,7 +1327,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
     also check status of the designated node and don't accept the request if
     the node is not an active node or if it doesn't have voting rights.
 
--   Implement the concept of `subscriber-only` nodes  
+-   Implement the concept of `subscriber-only` nodes
     These are wholly joined nodes, but they don't ever send replication
     changes to other BDR nodes in the cluster. But they do receive changes
     from all nodes in the cluster (except, of course the other subscriber-only
@@ -1323,17 +1342,17 @@ Upgrades are supported from BDR 3.6.22 in this release.
     someone needs to create the subscriber-only BDR nodegroup first. The
     feature does not attempt to create it automatically.
 
--   Improve DDL replication support for PostgreSQL 13  
+-   Improve DDL replication support for PostgreSQL 13
     The `ALTER STATISTICS` and `ALTER TYPE ... SET` commands are now supported.
 
 ### Resolved issues
 
--   Relax the safety check in `bdr.drop_node`. (RT69639)  
+-   Relax the safety check in `bdr.drop_node`. (RT69639)
     If a node is already dropped on any peer node, that peer does not
     know the status of the node to drop.  It must still be okay to
     drop that node.
 
--   Do not re-insert a deleted autopartition rule.  
+-   Do not re-insert a deleted autopartition rule.
     When an autopartition rule is dropped by one node and while the action is
     being replicated on some other node, if the other node executes one or
     more pending tasks for the table, we might accidentally re-insert the
@@ -1341,7 +1360,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
     the table on the remote node because the dependency check on autopartition
     rules fails.
 
--   Fix definition of `node_summary` and `local_node_summary` views (RT69564)  
+-   Fix definition of `node_summary` and `local_node_summary` views (RT69564)
     While the underlying pglogical catalogs support multiple interfaces per
     node, BDR will only ever use one, the one that's named same as the node.
     These views didn't reflect that and shown wrong information - if the
@@ -1349,25 +1368,25 @@ Upgrades are supported from BDR 3.6.22 in this release.
     results and the local_node_summary would not necessarily pick the
     correct one from those either.
 
--   Fix `bdr.node_log_config` (RM20318)  
+-   Fix `bdr.node_log_config` (RM20318)
     Adjust the view `bdr.node_log_config` to return correctly the
     conflict resolution.
 
--   Fix table access statistics reporting inside the writer  
+-   Fix table access statistics reporting inside the writer
     This should fix PostgreSQL monitoring views that show access and I/O
     statistics for tables which was broken in previous betas.
 
--   Fix the partitioning of `bdr.conflict_history` after upgrade from 3.6  
+-   Fix the partitioning of `bdr.conflict_history` after upgrade from 3.6
     Previously we'd keep the 3.6 definition, now we do the automatic
     partitioning same way as fresh 3.7 installs.
 
--   Fix node name reuse for nodes that get initialized from snapshot (RM20111)  
+-   Fix node name reuse for nodes that get initialized from snapshot (RM20111)
     These nodes previously missed initial state info which could cause catchup
     phase of join process to be skipped, with the new node missing concurrently
     written data as a result. This now works correctly.
 
 -   Fix potential crash on table rewrite (`VACUUM FULL`) on Standard Edition
-    (EBC-34)  
+    (EBC-34)
     Check for triggers on Standard Edition could cause crash on table rewrite
     previously.
 
@@ -1395,7 +1414,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
 
 -   Add support for PostgreSQL 13
 
--   Extend `bdr.get_node_sub_receive_lsn` with an optional `committed` argument  
+-   Extend `bdr.get_node_sub_receive_lsn` with an optional `committed` argument
     The default behaviour has been corrected to return only the last
     received LSN for a committed transaction to apply (filtered), which
     is the original intent and use of the function (e.g. by HARP).
@@ -1409,7 +1428,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
     1000000000 values allocated in each chunk respectively. We error out if
     the INCREMENT value is more than these ranges.
 
--   Add support for validating constraints without a global DML lock (RM12646)  
+-   Add support for validating constraints without a global DML lock (RM12646)
     The DDL operation ALTER TABLE ... ADD CONSTRAINT can take quite some
     time due to the validation to be performed.  BDR now allows
     deferring the validation and running the ALTER TABLE ... VALIDATE
@@ -1419,16 +1438,16 @@ Upgrades are supported from BDR 3.6.22 in this release.
     See the section "Adding a CONSTRAINT" in the "DDL Replication"
     chapter of the documentation for more details.
 
--   ALTER TABLE ... VALIDATE CONSTRAINTS waits for completion  
+-   ALTER TABLE ... VALIDATE CONSTRAINTS waits for completion
     Instead of expecting the user to explicitly wait for completion of
     this DDL operation, BDR now checks progress and waits for completion
     automatically.
 
--   Add new conflict kind `apply_error_ddl` and resolver `skip_transaction` (RM19351)  
+-   Add new conflict kind `apply_error_ddl` and resolver `skip_transaction` (RM19351)
     Can be used to skip transactions where DDL replication would cause `ERROR`.
     For example when same DDL was applied manually on multiple nodes.
 
--   Add new statistics to `bdr.stat_subscription` (RM18548)  
+-   Add new statistics to `bdr.stat_subscription` (RM18548)
     -   nabort - how many aborts did writer get
     -   how many errors the writer seen (currently same as above)
     -   nskippedtx - how many txes did the writer skip (using the
@@ -1439,7 +1458,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
 
 ### Resolved issues
 
--   Correct a hang in `bdr.wait_for_apply_queue` (RM11416, also affects CAMO)  
+-   Correct a hang in `bdr.wait_for_apply_queue` (RM11416, also affects CAMO)
     Keepalive messages possibly move the LSN forward.  In an otherwise
     quiescent system (without any transactions processed), this may have
     led to a hang in `bdr.wait_for_apply_queue`, because there may not
@@ -1451,7 +1470,7 @@ Upgrades are supported from BDR 3.6.22 in this release.
     the hang by discarding LSN increments for which there is nothing to
     apply on the subscriber.
 
--   Allow consensus protocol version upgrades despite parted nodes (RM19041)  
+-   Allow consensus protocol version upgrades despite parted nodes (RM19041)
     Exclude already parted nodes from the consensus protocol version
     negotiation, as such nodes do not participate in the consensus
     protocol any more.  Ensures the newest protocol version among the
@@ -1467,11 +1486,11 @@ Upgrades are supported from BDR 3.6.22 in this release.
         to be invoked multiple times. The various variables to track the loops
         needed adjustment.
 
--   Fix tracking of the last committed LSN for CAMO and Eager transactions (RM13509)  
+-   Fix tracking of the last committed LSN for CAMO and Eager transactions (RM13509)
     The GUC `bdr.last_committed_lsn` was only updated for standard
     asynchronous BDR transactions, not for CAMO or Eager ones.
 
--   Fix a problem with NULL values in `bdr.ddl_epoch` catalog (RM19046, RM19072)  
+-   Fix a problem with NULL values in `bdr.ddl_epoch` catalog (RM19046, RM19072)
     Release 3.7 added a new `epoch_consumed_lsn` column to
     `bdr.ddl_epoch` catalog. Adding a new column would set the column
     value to NULL in all existing rows in the table. But the code failed to
@@ -1485,24 +1504,24 @@ Upgrades are supported from BDR 3.6.22 in this release.
     explicitly and the code is fixed to never generate new NULL values for
     the column.
 
--   Corrections for upgrading from BDR 3.6.22  
+-   Corrections for upgrading from BDR 3.6.22
     Properly migrate subscription writer and conflict handlers from
     PGLogical, where this information used to be with BDR 3.6.  Ensure
     bdr.conflict_history is handled properly after an upgrade.
 
--   Fix `JOINING` state handling on consensus request timeout (RT69076)  
+-   Fix `JOINING` state handling on consensus request timeout (RT69076)
     The timeoud during `JOINING` state handling could result in node unable to
     join the BDR group. The retry logic now handles this state correctly.
 
 -   Validate inputs to replication_set_remove_table (RT69248, RM19620)
 
--   Handle missing column gracefully for `ALTER COLUMN TYPE` (RM19389, RT69114)  
+-   Handle missing column gracefully for `ALTER COLUMN TYPE` (RM19389, RT69114)
     Throw the standard ERROR rather than crashing when this happens.
 
--   Fix memory handling of a tuple slot during conflict lookup (RM18543)  
+-   Fix memory handling of a tuple slot during conflict lookup (RM18543)
     No longer crashes when the found tuple is logged into conflict log table.
 
--   Fix local node cache invalidation handling (RM13821)  
+-   Fix local node cache invalidation handling (RM13821)
     Previously BDR might not notice node creation or node drop due to race
     conditions, and would chose wrong behavior inside user backend.
 
@@ -1523,16 +1542,16 @@ Upgrade from 3.6 is not supported in this release, yet.
 
 ### Improvements
 
--   Parallel Apply (RM6503)  
+-   Parallel Apply (RM6503)
     Using the new infrastructure in pglogical 3.7.3, add support for parallel
-    writers.  
+    writers.
     The defaults are controlled by same pglogical configuration options (and
-    hence this feature is currently off by default)  
+    hence this feature is currently off by default)
     The number of parallel writers can be changed per group using the
     `num_writers` parameter of the `bdr.alter_node_group_config()` administration
     interface.
 
--   `resynchronize_table_from_node()` works with the generated columns (RM14876)  
+-   `resynchronize_table_from_node()` works with the generated columns (RM14876)
     It copies all the columns except the generated columns from remote node
     and computes the generated column values locally.
 
@@ -1552,23 +1571,23 @@ Upgrade from 3.6 is not supported in this release, yet.
     cluster and when the CRDT value is updated, `InvalidOid` will be replaced by
     a proper node identifier as part of the UPDATE operation.
 
--   Add consistent KV Store implementation for the use by the HARP project (RM17825)  
+-   Add consistent KV Store implementation for the use by the HARP project (RM17825)
     This is not meant for direct user consumption, but enables the HARP to work
     with BDR without additional consensus setup.
 
 ### Resolved issues
 
--   Re-add the "local_only" replication origin (RT68021)  
+-   Re-add the "local_only" replication origin (RT68021)
     Using `bdr_init_physical` may have inadvertently removed it due to a
     bug that existing up until release 3.6.19.  This release ensures to
     recreate it, if it's missing.
 
--   Handle NULL arguments to bdr.alter_node_set_log_config() gracefully (RT68375, RM17994)  
+-   Handle NULL arguments to bdr.alter_node_set_log_config() gracefully (RT68375, RM17994)
     The function caused segmentation fault when the first argument to this
     function is NULL. It is now fixed to provide an appropriate error message
     instead.
 
--   Fix MAXVALUE and MINVALUE with galloc sequences (RM14596)  
+-   Fix MAXVALUE and MINVALUE with galloc sequences (RM14596)
     While fetching values in advance, we could have reached the limit. Now we
     use only the values that we fetched before reaching the limit.
 
@@ -1582,7 +1601,7 @@ Upgrade from 3.6 is not supported in this release, yet.
     This is important in order to not allow unprivileged users to copy tables
     that they don't have otherwise ability to access.
 
--   Allow new group creation request to work after previous attempt has failed (RM17482)  
+-   Allow new group creation request to work after previous attempt has failed (RM17482)
     Previously, the new requests would always fail in some setups until BDR was
     completely removed from the node and reinstalled if the initial group creation
     has failed.
@@ -1592,32 +1611,32 @@ Upgrade from 3.6 is not supported in this release, yet.
 
 -   Fix memory leak during initial data synchronization (RM17668)
 
--   Fix `update_recently_deleted` conflict detection (RM16471)  
+-   Fix `update_recently_deleted` conflict detection (RM16471)
     This conflict was not detected correctly in 3.7.2.
 
 -   Check the options when altering a galloc sequence (RM18301, RT68470)
     Galloc sequences do not accept some modifications, warn the user in case
     not allowed options are used.
 
--   Make sure `bdr_wait_slot_confirm_lsn` is waiting for all slots (RM17478)  
+-   Make sure `bdr_wait_slot_confirm_lsn` is waiting for all slots (RM17478)
     This function used to skip some of the slots when checking if downstream
     has replicated everything.
 
--   Improve `PART_CATCHUP` node state handling (RM17418)  
+-   Improve `PART_CATCHUP` node state handling (RM17418)
     Resolves cases where node state would stay `PART_CATCHUP` forever due to
     race condition between nodes.
 
--   Make the consensus process more resilient when there are missing parted nodes  
+-   Make the consensus process more resilient when there are missing parted nodes
     Don't fail when trying to update a node's state to `PARTED` and the node no
     longer exists.
 
--   Remove `--recovery-conf` argument from `bdr_init_physical` (RM17196)  
+-   Remove `--recovery-conf` argument from `bdr_init_physical` (RM17196)
     It didn't work previously anywa and PostgreSQL12 does not longer have
     `recovery.conf`.
 
 ### Other improvements
 
--   Enable `bdr.truncate_locking` by default  
+-   Enable `bdr.truncate_locking` by default
     This is needed for TRUNCATE operations to always produce consistent results
     when there is concurrent DML happening in the BDR Group.
     This was missed by previous beta.
@@ -1646,51 +1665,51 @@ Upgrade from 3.6 is not supported in this release, yet.
 
 ### The highlights of BDR 3.7
 
--   Parallel Apply  
+-   Parallel Apply
     Allows configuring number of parallel writers that apply the replication
     stream.
 
--   AutoPartition  
+-   AutoPartition
     See [AutoPartition](scaling) for details.
 
--   Support `CREATE TABLE ... AS` statement (RM9696)  
+-   Support `CREATE TABLE ... AS` statement (RM9696)
     This feature is now supported in Enterprise Edition only.
 
 -   New ability to define BDR sub-groups in order to better represent physical
-    configuration of the EDB Postgres Distributed cluster.  
+    configuration of the EDB Postgres Distributed cluster.
     This also simplifies configurations where the EDB Postgres Distributed cluster is spread over
     multiple datacenters and only part of the database is replicated across
     datacenters as each subgroup will automatically have new default replication
     set assigned to it.
 
--   Conflicts are now logged by default to `bdr.conflict_history`  
+-   Conflicts are now logged by default to `bdr.conflict_history`
     Logging to a partitioned table with row level security to allow easier
     access to conflicts for application users.
 
--   New conflict type `multiple_unique_conflicts`  
+-   New conflict type `multiple_unique_conflicts`
     Allows resolution of complex conflicts involving multiple UNIQUE
     constraints for both INSERT and UPDATE.
 
 -   Merge views `bdr.node_replication_rates` and `bdr.node_estimate` into
     `bdr.node_replication_rates`. `bdr.node_estimate` has been removed (RM13523)
 
--   Don't replicate REINDEX command, now treated as a maintenance command  
+-   Don't replicate REINDEX command, now treated as a maintenance command
 
--   Various other changes to default settings  
+-   Various other changes to default settings
 
 ### Other improvements
 
 -   Optional monitoring tables for describing node connections and geographical
     distribution
 
--   Add bdr.resynchronize_table_from_node function (RM13565, RM14875)  
+-   Add bdr.resynchronize_table_from_node function (RM13565, RM14875)
     This function resynchronizes the relation from a remote node. This
     acquires a global DML lock on the relation, truncates the relation
     locally, and copies data into it from the remote note. The relation must
     exist on both nodes with the same name and definition.
 
 -   Add a function bdr.trigger_get_origin_node_id to be used in
-    conflict triggers(RM15105, RT67601)  
+    conflict triggers(RM15105, RT67601)
     This will enable users to define their conflict triggers such that a
     trusted node will always win in case of DML conflicts.
 
@@ -1698,24 +1717,24 @@ Upgrade from 3.6 is not supported in this release, yet.
 
 -   Add committed LSN reporting via `bdr.last_committed_lsn` (RM11059, RT65827)
 
--   BDR now accepts also URI in connection strings (RM14588)  
+-   BDR now accepts also URI in connection strings (RM14588)
     We can now specify also the format URI "postgresql://... " for the
     connection string.
 
 ### Resolved issues
 
--   Resilience against `idle_in_transaction_session_timeout` (RM13649, RT67029, RT67688)  
+-   Resilience against `idle_in_transaction_session_timeout` (RM13649, RT67029, RT67688)
     Set `idle_in_transaction_session_timeout` to 0 so we avoid any user setting
     that could close the connection and invalidate the snapshot.
 
--   Correct parsing of BDR WAL messages (RT67662)  
+-   Correct parsing of BDR WAL messages (RT67662)
     In rare cases a DDL which is replicated across a EDB Postgres Distributed cluster and requires
     a global lock may cause errors such as "invalid memory alloc request size"
     or "insufficient data left in message" due to incorrect parsing of direct
     WAL messages. The code has been fixed to parse and handle such WAL
     messages correctly.
 
--   Fix locking in ALTER TABLE with multiple sub commands (RM14771)  
+-   Fix locking in ALTER TABLE with multiple sub commands (RM14771)
     Multiple ALTER TABLE sub-commands should honor the locking
     requirements of the overall set. If one sub-command needs the locks,
     then the entire ALTER TABLE command needs it as well.
diff --git a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
index ba1ca43544a..7cc7497875d 100644
--- a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
+++ b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
@@ -5,6 +5,15 @@ originalFilePath: release-notes.md
 
 ---
 
+## pglogical 3.7.23
+
+This is a maintenance release for pglogical 3.7 which includes minor
+improvements as well as fixes for issues identified previously.
+
+### Resolved Issues
+
+### Upgrades
+
 ## pglogical 3.7.22
 
 This is a maintenance release for pglogical 3.7 which includes minor
@@ -71,7 +80,7 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
-- Adjust docs related to drop_subscription (RT86700, BDR-2705)  
+- Adjust docs related to drop_subscription (RT86700, BDR-2705)
   The function accepts 3 arguments, specify it in the documentation.
 
 ### Upgrades
@@ -89,13 +98,13 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
-- Add Windows specific workaround for wal_sender_timeout  
+- Add Windows specific workaround for wal_sender_timeout
 
-- Resolve hang related to `standby_slots_min_confirmed` (BDR-2445, RT80692)  
+- Resolve hang related to `standby_slots_min_confirmed` (BDR-2445, RT80692)
   Allow the WAl sender to proceed without the need to wait for the timeout
   after a Subscriber Only node is parted, while using `standby_slot_names`.
 
-- Don't replicate TRUNCATE as global message (BDR-2821, RT87453)  
+- Don't replicate TRUNCATE as global message (BDR-2821, RT87453)
   The TRUNCATE command now takes the replication set into account.
 
 ### Upgrades
@@ -113,7 +122,7 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
-- Fix spurious pglogical receiver timeouts on idle connections (RT82315)  
+- Fix spurious pglogical receiver timeouts on idle connections (RT82315)
   When there is nothing to replicate and apply, the pglogical receiver may
   misinterpret the state as timeout and exit with error "ERROR:  08006:
   terminating pglogical receiver due to timeout". Correct this
@@ -135,14 +144,14 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
--   Keep the `lock_timeout` as configured on non-CAMO-partner BDR nodes (BDR-1916)  
+-   Keep the `lock_timeout` as configured on non-CAMO-partner BDR nodes (BDR-1916)
     A CAMO partner uses a low `lock_timeout` when applying transactions
     from its origin node.  This was inadvertently done for all BDR nodes
     rather than just the CAMO partner, which may have led to spurious
     `lock_timeout` errors on pglogical writer processes on normal BDR
     nodes.
 
--   Prevent walsender processes spinning when facing lagging standby slots (RT80295, RT78290)  
+-   Prevent walsender processes spinning when facing lagging standby slots (RT80295, RT78290)
     Correct signaling to reset a latch so that a walsender process does
     consume 100% of a CPU in case one of the standby slots is lagging
     behind.
@@ -178,15 +187,15 @@ improvements as well as fixes for issues identified previously.
 ### Resolved Issues
 
 -   For the view `pglogical.subscriptions`, ensure the correct value is displayed
-    in the `provider_dsn` column (BDR-1859)  
+    in the `provider_dsn` column (BDR-1859)
     Previously the subscriber node's DSN was being displayed.
 
--   Fix handling of `wal_receiver_timeout` (BDR-1848)  
+-   Fix handling of `wal_receiver_timeout` (BDR-1848)
     The `wal_receiver_timeout` has not been triggered correctly due to a regression
     in BDR 3.7 and 4.0.
 
 -   Limit the `pglogical.standby_slot_names` check when reporting flush position only to
-    physical slots (RT77985, RT78290)  
+    physical slots (RT77985, RT78290)
     Otherwise flush progress is not reported in presence of disconnected nodes when
     using `pglogical.standby_slot_names`.
 
@@ -209,7 +218,7 @@ improvements as well as fixes for issues identified previously.
 
 ### Improvements
 
--   Implement buffered read for LCR segment file (BDR-1422)  
+-   Implement buffered read for LCR segment file (BDR-1422)
     This should reduce both I/O operations done by decoding worker as well as the
     amount of signalling between the decoding worker and wal senders which results
     in improved performance when decoding worker is used.
@@ -217,18 +226,18 @@ improvements as well as fixes for issues identified previously.
 ### Resolved Issues
 
 -   Invalidate output plugin's replication set cache when published replication sets
-    change (BDR-1715)  
+    change (BDR-1715)
     This ensures that published replicated sets are always up to date when user
     changes what should be published on node level. Before this fix, the old
     settings would have been applied until downstream has reconnected.
     This primarily affects BDR in situations where the `bdr.alter_node_replication_sets`
     was called on multiple nodes in quick succession.
 
--   Don't try to retry transaction replication when writer receives SIGTERM or SIGINT  
+-   Don't try to retry transaction replication when writer receives SIGTERM or SIGINT
     This would unnecessarily hold back the shutdown of postgres when parallel apply
     is enabled.
 
--   Log correct error message during initial schema synchronization error (BDR-1598)  
+-   Log correct error message during initial schema synchronization error (BDR-1598)
     Previously we'd always log ERROR with message "Success" which is not helpful for
     troubleshooting.
 
@@ -248,7 +257,7 @@ improvements as well as fixes for issues identified previously.
 
 ### Improvements
 
--   Allow the BDR consensus process to use a (sub) replorigin (BDR-1613)  
+-   Allow the BDR consensus process to use a (sub) replorigin (BDR-1613)
     For parallel apply, multiple writers could use invididual origins
     that would be merged, thus act kind of as child origins for a main
     or parent origin.
@@ -257,7 +266,7 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
--   Fix the replication protocol handling of some strings (RT74123)  
+-   Fix the replication protocol handling of some strings (RT74123)
     Certain strings like e.g. relation schema, relation name, attribute
     name, and message prefix were mistakenly changed to not include a
     terminating NULL character.  This led to a protocol incompatibility
@@ -265,25 +274,25 @@ improvements as well as fixes for issues identified previously.
     messages are used (e.g. due to the use of BDR features CAMO or Eager
     All Node Replication).
 
--   Fix segfault when creating a subscription with the RabbitMQ writer plugin (BDR-1482, RT72434)  
+-   Fix segfault when creating a subscription with the RabbitMQ writer plugin (BDR-1482, RT72434)
 
--   Don't wait on own replication slot when waiting for `standby_slot_names` (RT74036)  
+-   Don't wait on own replication slot when waiting for `standby_slot_names` (RT74036)
     The walsenders that use slots named in `standby_slot_names` should not
     wait for anything, otherwise it might wait forever.
 
--   Reduce logging when WAL decoder is not available (BDR-1041)  
+-   Reduce logging when WAL decoder is not available (BDR-1041)
     `pgl_xact_fully_decoded()` will log a message when it finds that
     the WAL decoder is not running. WAL decoder may not start for long
     duration and thus this log line will repeat and increase the log file
     size. There are other ways to know whether WAL decoder is running. So
     this line is not required.
 
--   Handle deprecated `update_differing` and `update_recently_deleted` (BDR-1610, RT74973)  
+-   Handle deprecated `update_differing` and `update_recently_deleted` (BDR-1610, RT74973)
     While upgrading to 3.7, take care of the deprecated conflict types
     otherwise, as they would be unknown to the new version, it would
     not know how to handle them and break the upgrade process.
 
--   Enable async conflict resolution for explicit 2PC (BDR-1609, RT71298)  
+-   Enable async conflict resolution for explicit 2PC (BDR-1609, RT71298)
     Continue applying the transaction using the async conflict resolution
     for explicit two phase commit.
 
@@ -303,12 +312,12 @@ improvements as well as fixes for issues identified previously.
 
 ### Improvements
 
--   Add replication status monitoring (BDR-865)  
+-   Add replication status monitoring (BDR-865)
     Track the connection establishment and drops, the number of
     transactions committed as well as the restart LSN to detect repeated
     restarts and diagnose stalled replication.
 
--   Improve performance when used in combination with synchronous replication (BDR-1398)  
+-   Improve performance when used in combination with synchronous replication (BDR-1398)
     Override `synchronous_commit` to `local'` for all PGLogical
     processes performing only bookkeeping transactions which do not need
     to be replicated.  Only the PGLogical writer processes applying user
@@ -325,7 +334,7 @@ improvements as well as fixes for issues identified previously.
     Decoding Worker, and reduce number of system calls when writing one
     LCR chunk to an LCR segment file.
 
--   Improve compatibility with Postgres 13 (BDR-1396)  
+-   Improve compatibility with Postgres 13 (BDR-1396)
     Adjust to an API change in ReplicationSlotAcquire that may have led
     to unintended blocking when non-blocking was requestend and vice
     versa.  This version of PGLogical eliminates this potential problem,
@@ -346,25 +355,25 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
--   Add protection against malformed parameter values in pgl output plugin  
+-   Add protection against malformed parameter values in pgl output plugin
     This fixes potential crash when some parameters sent to the output plugin
     were malformed.
 
--   Get copy of slot tuple when logging conflict (BDR-734)  
+-   Get copy of slot tuple when logging conflict (BDR-734)
     Otherwise we could materialize the row early causing wrong update in presence
     of additional columns on the downstream.
 
--   Use a separate memory context for processing LCRs (BDR-1237, RT72165)  
+-   Use a separate memory context for processing LCRs (BDR-1237, RT72165)
     This fixes memory leak when using the decoding worker feature of BDR.
 
--   Truncate LCR segment file after recovery (BDR-1236, BDR-1259)  
+-   Truncate LCR segment file after recovery (BDR-1236, BDR-1259)
     This fixes memory errors reported by the decoding worker after crash.
 
 -   Ensure `pg_read_and_filter_lcr` will exit when postmaster dies
-    (BDR-1226, BDR-1209, RT72083)  
+    (BDR-1226, BDR-1209, RT72083)
     Solves issues with hanging decoder worker on shutdown.
 
--   Fix memory leak in the pglogical COPY handler (BDR-1219, RT72091)  
+-   Fix memory leak in the pglogical COPY handler (BDR-1219, RT72091)
     This fixes memory leak when synchronizing large tables.
 
 -   Allow binary and internal protocol on more hardware combinations. This
@@ -406,32 +415,32 @@ improvements as well as fixes for issues identified previously.
 
 ### Improvements
 
--   Support two-phase commit transaction with Decoding Worker (BDR-811)  
+-   Support two-phase commit transaction with Decoding Worker (BDR-811)
 
     A two-phase commit transaction is completely decoded and sent downstream when
     processing its PREPARE WAL record. COMMIT/ROLLBACK PREPARED is replicated
     separately when processing the corresponding WAL record.
 
--   Reduce writes to `pg_replication_origin` when using parallel apply (RT71077)  
+-   Reduce writes to `pg_replication_origin` when using parallel apply (RT71077)
     Previously, especially on EPAS pglogical could produce thousands of dead rows
     in `pg_replication_origin` system catalog if it had connection problems to
     upstream.
 
 ### Resolved Issues
 
--   Fix flush queue truncation (BDR-890)  
+-   Fix flush queue truncation (BDR-890)
     During queue compaction flush to correct LSN instead of always truncating
     whole flush queue.
 
--   Fix the pglogical.worker_error columns `werr_worker_index` and `werr_time`  
+-   Fix the pglogical.worker_error columns `werr_worker_index` and `werr_time`
     Used to report wrong values.
 
--   Fix snapshot handling in internal executor usage (BDR-904)  
+-   Fix snapshot handling in internal executor usage (BDR-904)
     Row filtering didn't correctly pushed snapshot in some situations.
 
     Caught thanks to upcoming change in PostgreSQL that double checks for this.
 
--   Fix handling of domains over arrays and composite types (BDR-29)  
+-   Fix handling of domains over arrays and composite types (BDR-29)
     The replication protocol previously could not always handle columns using
     domains over arrays and domains over composite types.
 
@@ -450,7 +459,7 @@ Upgrades are supported from pglogical 3.6.25 and 3.7.7 in this release.
 
 ### Resolved Issues
 
--   Fix divergence after physical failover (BDR-365, RT68894 and RM19886)  
+-   Fix divergence after physical failover (BDR-365, RT68894 and RM19886)
     Make sure that we don't report back LSN on subscriber that
     hasn't been received by named standbys (pglogical.standby_slot_names).
 
@@ -461,34 +470,34 @@ Upgrades are supported from pglogical 3.6.25 and 3.7.7 in this release.
 
 -   Fix crash when ERROR happened during fast shutdown of pglogical writer
 
--   Don't re-enter worker error handling loop recursively (BDR-667)  
+-   Don't re-enter worker error handling loop recursively (BDR-667)
     This should help make what happens clearer in any cases where we do
     encounter errors during error processing.
 
--   Assign collation to the index scan key (BDR-561)  
+-   Assign collation to the index scan key (BDR-561)
     When doing lookups for INSERT/UPDATE/DELETE, either to find conflicts
     or key for the operation to be applied, we should use correct collation.
 
     This fixes index lookups for index on textual fields on Postgres 12+.
 
--   Use `name` data type for known fixed length fields (BDR-561)  
+-   Use `name` data type for known fixed length fields (BDR-561)
     This solves potential index collation issues with pglogical catalogs.
 
--   Progress WAL sender's slot based on WAL decoder input (BDR-567)  
+-   Progress WAL sender's slot based on WAL decoder input (BDR-567)
     Without slot progression the server will eventually stop working.
 
 -   Fix begin of transaction write when LCR file does not have enough space (BDR-606)
 
--   Restart decoding a transaction that was not completed in single decoding worker (BDR-247)  
+-   Restart decoding a transaction that was not completed in single decoding worker (BDR-247)
     If we crashed during a long transaction that spawns on more then one lcr file
     we start decoding again from the lsn of the beginning of the transaction and
     find the last lcr file where we can write into.
 
--   Generate temp slot with correct length in subscription sync  
+-   Generate temp slot with correct length in subscription sync
     Otherwise the name of the slot might be shortened by Postgres leading to
     confusion on the slot cleanup.
 
--   Improve detection of mixing temporary and nontemporary objects in DDLs (BDR-485)  
+-   Improve detection of mixing temporary and nontemporary objects in DDLs (BDR-485)
     These can break replication so it's important to not allow them.
 
 -   Fix pre-commit message handling in Eager replication (BDR-492)
@@ -508,13 +517,13 @@ Upgrades are supported from pglogical 3.6.25 and 3.7.6 in this release.
 
 -   Use parallel apply during initial sync during logical join
 
--   Add worker process index to the worker_error catalog (BDR-229)  
+-   Add worker process index to the worker_error catalog (BDR-229)
     The column `werr_worker_index` in worker_error table keeps track
     of the writers for the same subscription.
 
 -   Various improvements for WAL decoder/sender coordination (BDR-232, BDR-335)
 
--   Name LCR segment similar to XLOG segments (BDR-236, BDR-253, BDR-321, BDR-322)  
+-   Name LCR segment similar to XLOG segments (BDR-236, BDR-253, BDR-321, BDR-322)
     An LCR segment file is identified by five 8-digit hex numbers.
     Timeline first group, XLOG the next two groups and file number the last
     two groups.
@@ -527,7 +536,7 @@ Upgrades are supported from pglogical 3.6.25 and 3.7.6 in this release.
 
 -   Force and wait for all writers to exit when one writer dies (BDR-229)
 
--   Name LCR directory after the replication slot (BDR-60)  
+-   Name LCR directory after the replication slot (BDR-60)
     Logical output plugin may be used by multiple replication slots. Store
     the LCRs from a given replication slot in a directory named after that
     replication slot to avoid mixing LCRs for different slots.
@@ -548,7 +557,7 @@ Upgrades are supported from pglogical 3.6.25 in this release.
 -   Enable parallel apply for CAMO and Eager (RM17858)
 
 -   Improve error handling in Eager/CAMO, especially with parallel apply
-    (BDR-106)  
+    (BDR-106)
 
 -   Reduce severity of Eager/CAMO feedback errors
 
@@ -557,30 +566,30 @@ Upgrades are supported from pglogical 3.6.25 in this release.
 
 ### Resolved Issues
 
--   Improve relcache invalidation handling in heap writer  
+-   Improve relcache invalidation handling in heap writer
     This should solve missed invalidations after opening table for DML apply.
 
 -   Wait for the writer that has XID assigned rather then one that doesn't
-    (BDR-137)  
+    (BDR-137)
     This fixes deadlock in parallel apply when there is a mix of empty and
     non-empty transactions where the non-empty ones conflict.
 
 -   Correct writer state tracking for Eager/CAMO (BDR-107)
 
--   Correct and improve CAMO misconfiguration handling (BDR-105)  
+-   Correct and improve CAMO misconfiguration handling (BDR-105)
     Properly abort the transaction in case of sync CAMO, so the internal
     state of the PGL writer is cleared
 
--   Fix transaction state tracking for CAMO/Eager  
+-   Fix transaction state tracking for CAMO/Eager
     Do not abort the transaction at pre-commit time for non-CAMO nodes, but
     keep it open until the final commit.  Adjust the transaction state
     tracking accordingly
 
--   Fix MERGE handling in 2ndQPostgres 12 and 13  
+-   Fix MERGE handling in 2ndQPostgres 12 and 13
     We'd before allow the MERGE command on replicated tables without appropriate
     REPLICA IDENTITY which could result in broken replication.
 
--   Fix CAMO feedback sending (RM17858)  
+-   Fix CAMO feedback sending (RM17858)
     Fixes stalls in CAMO feedback, improving performance compared to previous
     3.7 beta releases. This is especially visible with parallel apply enabled.
 
@@ -664,7 +673,7 @@ major new features as well as smaller enhancements.
 
 -   Support PostgreSQL 13
 
--   Add `pglogical.replication_origin_status` view (RM17074)  
+-   Add `pglogical.replication_origin_status` view (RM17074)
     Same as `pg_replication_origin_status` but does not require superuser
     permissions to access it.
 
@@ -675,7 +684,7 @@ major new features as well as smaller enhancements.
 ### Resolved Issues
 
 -   Fix race condition in replication table filtering which could cause
-    crash (RM18839)  
+    crash (RM18839)
     The cached info about table might get invalidated while used which would
     crash the backend during one of the following operations:
 
@@ -683,10 +692,10 @@ major new features as well as smaller enhancements.
     -   new subcription creation
     -   table resynchronization
 
--   Don't do transparent DDL replication on commands that affect temporary objects (RM19491, RT69170)  
+-   Don't do transparent DDL replication on commands that affect temporary objects (RM19491, RT69170)
     These are likely to not exist on the subscription.
 
--   Only run pgl specific code in deadlock detector when inside writer (RM18402)  
+-   Only run pgl specific code in deadlock detector when inside writer (RM18402)
     It's not relevant in user backends and would cause ERRORs there.
 
 ## pglogical 3.7.3
@@ -705,11 +714,11 @@ major new features as well as smaller enhancements.
     (`num_writers` option in `pglogical.create_subscription()` and
     `pglogical.alter_subscription_num_writers()`).
 
--   Split "replicating" subscription status into two statuses  
+-   Split "replicating" subscription status into two statuses
     One is still "replicating" and is reported only if something was actually
     replicated by the subcription since last worker start. The other is "started"
     and just means that the worker for the subscription is running at the time
-    the status query was executed.  
+    the status query was executed.
     This should reduce confusion where subscription would report "replicating"
     status but worker is in restart loop due to an apply error.
 
@@ -720,16 +729,16 @@ major new features as well as smaller enhancements.
 -   Add PostgreSQL 12 support to `pglogical_create_subscriber`
 
 -   Rework table resynchronization to use separate receiver process from the
-    main one  
+    main one
     This improves performance of both main apply (primarily latency) and the
-    resynchronization itself.  
+    resynchronization itself.
     It also fixes potential issue where table could be considered synchronized
     before the catchup finished completely.
 
 ### Resolved Issues
 
 -   Fix crash on resynchronization of large partitioned tables (RM18154, RM15733,
-    RT68455, RT68352)  
+    RT68455, RT68352)
     The resync process would keep crashing due to cache invalidation race
     condition if the `COPY` took very long or if there was DDL activity on the
     copied table during the `COPY`.
@@ -744,11 +753,11 @@ major new features as well as smaller enhancements.
 
 -   Resolve rare crash in HeapWriter row cleanup code (RM16956)
 
--   Resolve rare crash on worker exit (RM11686)  
+-   Resolve rare crash on worker exit (RM11686)
     If a pglogical worker exited before it finished initialization it could
     crash instead of exiting cleanly.
 
--   Fix apply errors parallel index rebuild afrer `TRUNCATE` (RM17602)  
+-   Fix apply errors parallel index rebuild afrer `TRUNCATE` (RM17602)
 
 ## pglogical 3.7.2
 
@@ -769,13 +778,13 @@ existing applications.
 
 ### Improvements
 
--   Add support for Postgres 12, deprecate support for older versions  
+-   Add support for Postgres 12, deprecate support for older versions
     pglogical 3.7 now requires at least Postgres 10 and supports up to
     Postgres 12.
 
 ### Resolved Issues
 
--   Keep open the connection until pglogical_create_subscriber finishes (RM13649)  
+-   Keep open the connection until pglogical_create_subscriber finishes (RM13649)
     Set idle_in_transaction_session_timeout to 0 so we avoid any user setting
     that could close the connection and invalidate the snapshot.
 

From bcbcaea769de3da53fee81eb4047182d8d865c28 Mon Sep 17 00:00:00 2001
From: willmyersatenterprisedb
 <102972161+willmyersatenterprisedb@users.noreply.github.com>
Date: Mon, 13 Nov 2023 11:06:10 -0500
Subject: [PATCH 09/38] Update linux.mdx

a couple of typos
---
 product_docs/docs/lasso/4/linux.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/product_docs/docs/lasso/4/linux.mdx b/product_docs/docs/lasso/4/linux.mdx
index 043501079c2..2b83f5c6822 100644
--- a/product_docs/docs/lasso/4/linux.mdx
+++ b/product_docs/docs/lasso/4/linux.mdx
@@ -92,7 +92,7 @@ option as follows:
     ./lasso --barman-configuration /opt/barman/barman.conf
 ```
 
-## Replication Manger (repmgr) report
+## Replication Manager (repmgr) report
 
 Lasso can run on systems where repmgr is installed. In that
 case, it gathers repmgr-related information.
@@ -130,7 +130,7 @@ option as follows:
 This approach is preferred, as it guarantees Lasso will use
 the correct repmgr configuration file instead of trying to find it automatically.
 
-## Postres Enterprise Manager (PEM) report
+## Postgres Enterprise Manager (PEM) report
 
 Lasso can run on systems where PEM is installed. In that
 case, it also gathers PEM-related information, like some configuration
@@ -317,4 +317,4 @@ You can run a system-only report with the following command:
 
 ```
     ./lasso --system-only
-```
\ No newline at end of file
+```

From b876ebfbbc0a39efdce54d4068193f39e0c81ac9 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Mon, 13 Nov 2023 15:35:29 +0000
Subject: [PATCH 10/38] Typo fix in example

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/5/cli/configuring_cli.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/cli/configuring_cli.mdx b/product_docs/docs/pgd/5/cli/configuring_cli.mdx
index 8a3ba373087..37422d707d4 100644
--- a/product_docs/docs/pgd/5/cli/configuring_cli.mdx
+++ b/product_docs/docs/pgd/5/cli/configuring_cli.mdx
@@ -34,7 +34,7 @@ PGD CLI takes its database connection information from either the PGD CLI config
 You can pass the connection string directly to `pgd` using the `--dsn` option. For details, see the [sample use case](using_cli/#passing-a-database-connection-string). For example:
 
 ```shell
-pgd --dsn "host=bdr-a1 post=5432 user=enterprisedb" show-version
+pgd --dsn "host=bdr-a1 port=5432 user=enterprisedb" show-version
 ```
 
 ### Using a configuration file

From ba99a2b69d902d0827f4c7eeb61fd503be33b024 Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Tue, 31 Oct 2023 17:47:22 +0530
Subject: [PATCH 11/38] Create rel_notes for PGD v4.3.3 and add entries for CLI
 and Utilities

---
 product_docs/docs/pgd/4/rel_notes/index.mdx   |  2 ++
 .../pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx   | 19 +++++++++++++++++++
 2 files changed, 21 insertions(+)
 create mode 100644 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx

diff --git a/product_docs/docs/pgd/4/rel_notes/index.mdx b/product_docs/docs/pgd/4/rel_notes/index.mdx
index d81c4c2303d..8208c526791 100644
--- a/product_docs/docs/pgd/4/rel_notes/index.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/index.mdx
@@ -2,6 +2,7 @@
 title: "EDB Postgres Distributed Release notes"
 navTitle: "Release notes"
 navigation:
+- pgd_4.3.3_rel_notes
 - pgd_4.3.2+p1_rel_notes
 - pgd_4.3.2_rel_notes
 - pgd_4.3.1+p2_rel_notes
@@ -27,6 +28,7 @@ The EDB Postgres Distributed documentation describes the latest version of EDB P
 
 | Release Date | EDB Postgres Distributed     | BDR   | HARP  |  CLI  | TPAexec                                                                          |
 | ------------ | ---------------------------- | ----- | ----- | ----- | -------------------------------------------------------------------------------- |
+| 14 Nov 2023 | [4.3.3](pgd_4.3.3_rel_notes)| 4.3.3 | 2.3.2 | 1.1.2 | [23.24](/tpa/latest/rel_notes/tpa_23.24_rel_notes)   |
 | 17 Oct 2023 | [4.3.2+p1](pgd_4.3.2+p1_rel_notes)| 4.3.2 | 2.3.2 | 1.1.1 | [23.20](/tpa/latest/rel_notes/tpa_23.20_rel_notes)   |
 | 31 Aug 2023 | [4.3.2 ](pgd_4.3.2_rel_notes)| 4.3.2 | 2.3.1 | 1.1.1 | [23.20](/tpa/latest/rel_notes/tpa_23.20_rel_notes)   |
 | 27 Jul 2023 | [4.3.1+p2 ](pgd_4.3.1+p2_rel_notes)| 4.3.1 | 2.3.1 | 1.1.1 | [23.19](/tpa/latest/rel_notes/tpa_23.19_rel_notes)   |
diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
new file mode 100644
index 00000000000..66055c57eab
--- /dev/null
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -0,0 +1,19 @@
+---
+title: "Release notes for EDB Postgres Distributed version 4.3.3"
+navTitle: "Version 4.3.3"
+redirects:
+  - /pgd/latest/bdr/release_notes/bdr4.3.3_rel_notes/
+---
+
+EDB Postgres Distributed version 4.3.3 is a patch release of EDB Postgres Distributed 4, which includes bug fixes for issues identified in previous versions.
+
+!!! Note
+This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.10.14, 14.7.0 and later.
+!!!
+
+| Component | Version |  Type        |                                                   Description                                                           |
+| --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
+| CLI       | 1.1.2   | Enhancement  | Upgrade `pgconn` lib version to address `connect_timeout` issue in go driver (BDR-3785) |
+| CLI       | 1.1.2   | Bug fix      | Set the correct defaults for verbose flag |
+| Utilities | 1.2.0   | Enhancement  | Add support for pg_upgrade of BDR 3.7 |
+| Utilities | 1.2.0   | Bug fix      | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level (BDR-4159) |

From 41f4faabcc8aea4af40b628f9e1bd1202e6500fb Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Wed, 1 Nov 2023 15:25:35 +0530
Subject: [PATCH 12/38] Update rel_notes descriptions

---
 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index 66055c57eab..e666a0e1be0 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -13,7 +13,6 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 
 | Component | Version |  Type        |                                                   Description                                                           |
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
-| CLI       | 1.1.2   | Enhancement  | Upgrade `pgconn` lib version to address `connect_timeout` issue in go driver (BDR-3785) |
-| CLI       | 1.1.2   | Bug fix      | Set the correct defaults for verbose flag |
-| Utilities | 1.2.0   | Enhancement  | Add support for pg_upgrade of BDR 3.7 |
-| Utilities | 1.2.0   | Bug fix      | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level (BDR-4159) |
+| CLI       | 1.1.2   | Bug&nbsp;fix | Fixed `connect_timeout` issue when `sslmode=allow` or `sslmode=prefer` by upgrading database driver library version. |
+| Utilities | 1.2.0   | Enhancement  | Add support for BDR 3.7.22 and above in `bdr_pg_upgrade` |
+| Utilities | 1.2.0   | Bug&nbsp;fix | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` |

From 248c9bc16d70e83bfd75692bf1b2629d2b3e0c2c Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Wed, 1 Nov 2023 16:26:44 +0530
Subject: [PATCH 13/38] Remove entry for bdr_pg_upgrade support for 3.7

---
 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx | 1 -
 1 file changed, 1 deletion(-)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index e666a0e1be0..f9287b95ef8 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -14,5 +14,4 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 | Component | Version |  Type        |                                                   Description                                                           |
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
 | CLI       | 1.1.2   | Bug&nbsp;fix | Fixed `connect_timeout` issue when `sslmode=allow` or `sslmode=prefer` by upgrading database driver library version. |
-| Utilities | 1.2.0   | Enhancement  | Add support for BDR 3.7.22 and above in `bdr_pg_upgrade` |
 | Utilities | 1.2.0   | Bug&nbsp;fix | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` |

From a3711929b7ce56adc59139fac58525b8d8bd8c60 Mon Sep 17 00:00:00 2001
From: Petr Jelinek <petr.jelinek@enterprisedb.com>
Date: Thu, 2 Nov 2023 16:44:01 +0100
Subject: [PATCH 14/38] Update pgd_4.3.3_rel_notes.mdx

Added BDR bug fixes
---
 .../pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx    | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index f9287b95ef8..a06485d2051 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -13,5 +13,23 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 
 | Component | Version |  Type        |                                                   Description                                                           |
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
+| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. (RT97952) |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. (RT78928) |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix unsafe CAMO decisions in remote_write mode. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the taskmgr process does not ignore SIGINT. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix a bug in copying bdr.autopartition_rules during logical join. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Override bdr.ddl_replication=off in taskmgr worker. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Avoid a potential deadlock between `bdr.autopartition_wait_for_partitions()` and taskmgr|
+| BDR       | 5.3.0   | Bug&nbsp;fix | Block new EPAS automatic partitioning on PGD cluster. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Block PGD Autopartition on EPAS INTERVAL partitioned table. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix memory leak in streaming transaction processing. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Allow force parting of nodes that are already being parted normally. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to replication slot conflict. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to node_catchup_info conflict. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix row filter failure for partitions created after a table column was dropped (RT95149) |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Prevent duplicate Raft request ID generation which could break replication. |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Fix several rare memory access issues that could potentially cause crashes of workers. |
 | CLI       | 1.1.2   | Bug&nbsp;fix | Fixed `connect_timeout` issue when `sslmode=allow` or `sslmode=prefer` by upgrading database driver library version. |
 | Utilities | 1.2.0   | Bug&nbsp;fix | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` |

From dbc7c8ab7556a2dde9e8f13e58cd3c315d6132a5 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Mon, 13 Nov 2023 18:15:27 +0000
Subject: [PATCH 15/38] Late issue RT99115

---
 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index a06485d2051..f8361dceb08 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -15,6 +15,7 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
 | BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. (RT97952) |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. (RT78928) |
+| BDR       | 5.3.0   | Bug&nbsp;fix | Handle partitions with different attribute numbers when batch inserting. (RT99115) |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Fix unsafe CAMO decisions in remote_write mode. |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the taskmgr process does not ignore SIGINT. |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. |

From ca441ee6535bfac214bb2deb63f33cd68a33bc39 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Mon, 13 Nov 2023 22:41:05 +0000
Subject: [PATCH 16/38] Update
 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx

---
 product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index f8361dceb08..5276327fe9e 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -13,7 +13,7 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 
 | Component | Version |  Type        |                                                   Description                                                           |
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
-| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. (RT97952) |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. (RT97952) |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. (RT78928) |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Handle partitions with different attribute numbers when batch inserting. (RT99115) |
 | BDR       | 5.3.0   | Bug&nbsp;fix | Fix unsafe CAMO decisions in remote_write mode. |

From 547c32e0e214c16171d226b96dc811a6d03fb93f Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Tue, 14 Nov 2023 08:38:07 +0000
Subject: [PATCH 17/38] Correct version numbers add missing entry

---
 .../pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx   | 37 ++++++++++---------
 1 file changed, 19 insertions(+), 18 deletions(-)

diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
index 5276327fe9e..52665913511 100644
--- a/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
+++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.3.3_rel_notes.mdx
@@ -14,23 +14,24 @@ This version is required for EDB Postgres Advanced Server versions 12.14.18, 13.
 | Component | Version |  Type        |                                                   Description                                                           |
 | --------- | ------- | ------------ | ------------------------------------------------------------------------------------------------------------------------|
 | BDR       | 4.3.3   | Bug&nbsp;fix | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. (RT97952) |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. (RT78928) |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Handle partitions with different attribute numbers when batch inserting. (RT99115) |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix unsafe CAMO decisions in remote_write mode. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that the taskmgr process does not ignore SIGINT. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix a bug in copying bdr.autopartition_rules during logical join. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Override bdr.ddl_replication=off in taskmgr worker. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Avoid a potential deadlock between `bdr.autopartition_wait_for_partitions()` and taskmgr|
-| BDR       | 5.3.0   | Bug&nbsp;fix | Block new EPAS automatic partitioning on PGD cluster. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Block PGD Autopartition on EPAS INTERVAL partitioned table. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix memory leak in streaming transaction processing. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Allow force parting of nodes that are already being parted normally. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to replication slot conflict. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to node_catchup_info conflict. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix row filter failure for partitions created after a table column was dropped (RT95149) |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Prevent duplicate Raft request ID generation which could break replication. |
-| BDR       | 5.3.0   | Bug&nbsp;fix | Fix several rare memory access issues that could potentially cause crashes of workers. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. (RT78928) |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Handle partitions with different attribute numbers when batch inserting. (RT99115) |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix unsafe CAMO decisions in remote_write mode. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Ensure that the taskmgr process does not ignore SIGINT. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix a bug in copying bdr.autopartition_rules during logical join. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Override bdr.ddl_replication=off in taskmgr worker. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Avoid a potential deadlock between `bdr.autopartition_wait_for_partitions()` and taskmgr|
+| BDR       | 4.3.3   | Bug&nbsp;fix | Block new EPAS automatic partitioning on PGD cluster. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Allow existing automatically partitioned tables when cluster is created or upgraded. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Block PGD Autopartition on EPAS INTERVAL partitioned table. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix memory leak in streaming transaction processing. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Allow force parting of nodes that are already being parted normally. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to replication slot conflict. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix nodes getting stuck on PART_CATCHUP due to node_catchup_info conflict. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix row filter failure for partitions created after a table column was dropped (RT95149) |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Prevent duplicate Raft request ID generation which could break replication. |
+| BDR       | 4.3.3   | Bug&nbsp;fix | Fix several rare memory access issues that could potentially cause crashes of workers. |
 | CLI       | 1.1.2   | Bug&nbsp;fix | Fixed `connect_timeout` issue when `sslmode=allow` or `sslmode=prefer` by upgrading database driver library version. |
 | Utilities | 1.2.0   | Bug&nbsp;fix | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` |

From 5e835f3f1d7875e21d7b0145a42556159d3896f5 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Tue, 14 Nov 2023 09:25:38 +0000
Subject: [PATCH 18/38] Fix missing () in pg_control_init

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/tde/15/enabling_tde.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/tde/15/enabling_tde.mdx b/product_docs/docs/tde/15/enabling_tde.mdx
index 07c5903bd75..5697e5ff6f8 100644
--- a/product_docs/docs/tde/15/enabling_tde.mdx
+++ b/product_docs/docs/tde/15/enabling_tde.mdx
@@ -113,7 +113,7 @@ You can find out whether TDE is present on a server by querying the `data_encryp
 A value of 0 means TDE isn't enabled. Any nonzero value reflects the version of TDE in use. Currently, when TDE is enabled, this value is 1.
 
 ```sql
-# select data_encryption_version from pg_control_init;
+# select data_encryption_version from pg_control_init();
  data_encryption_version
 -------------------------
                        1

From bdc5fa497fbe1a57c258356da9ba4f597338bd92 Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Tue, 31 Oct 2023 19:05:33 +0530
Subject: [PATCH 19/38] Create release notes for PGD 5.3.0 and add entries for
 CLI, Proxy and Utilities

---
 product_docs/docs/pgd/5/rel_notes/index.mdx   |  2 ++
 .../pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx   | 31 +++++++++++++++++++
 2 files changed, 33 insertions(+)
 create mode 100644 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx

diff --git a/product_docs/docs/pgd/5/rel_notes/index.mdx b/product_docs/docs/pgd/5/rel_notes/index.mdx
index c5eb7e32160..a74799ec42a 100644
--- a/product_docs/docs/pgd/5/rel_notes/index.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/index.mdx
@@ -2,6 +2,7 @@
 title: "EDB Postgres Distributed Release notes"
 navTitle: "Release notes"
 navigation:
+- pgd_5.3.0_rel_notes
 - pgd_5.2.0_rel_notes
 - pgd_5.1.0_rel_notes
 - pgd_5.0.1_rel_notes
@@ -20,6 +21,7 @@ that introduced the feature.
 
 | Release Date  |   EDB Postgres Distributed   | BDR extension | PGD CLI | PGD Proxy |
 | ------------- | ---------------------------- | ------------- | ------- | --------- |
+| 14 Nov 2023  | [5.3.0](pgd_5.3.0_rel_notes) | 5.3.0         | 5.3.0   | 5.3.0     |
 | 4 Aug 2023   | [5.2.0](pgd_5.2.0_rel_notes) | 5.2.0         | 5.2.0   | 5.2.0     |
 | 16 May 2023  | [5.1.0](pgd_5.1.0_rel_notes) | 5.1.0         | 5.1.0   | 5.1.0     |
 | 21 Mar 2023  | [5.0.1](pgd_5.0.1_rel_notes) | 5.0.0         | 5.0.1   | 5.0.1     |
diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
new file mode 100644
index 00000000000..24321834318
--- /dev/null
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -0,0 +1,31 @@
+---
+title: "EDB Postgres Distributed 5.3.0 release notes"
+navTitle: "Version 5.3.0"
+---
+
+Released: 14 Nov 2023
+
+EDB Postgres Distributed version 5.3.0 is a minor version of EDB Postgres Distributed.
+
+## Highlights of EDB Postgres Distributed 5.3.0
+
+<Add the highlights bullet points here>
+
+!!! Important Recommended upgrade
+    We recommend that users of PGD 5.2 upgrade to PGD 5.3.
+
+!!! Note PostgreSQL version compatibility
+This version is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later.
+!!!
+
+
+| Component | Version | Type        | Description  |
+|-----------|---------|-------------|--------------|
+| CLI       | 5.3.0   | Bug fix     | Fix `shared_preload_libraries` verification |
+| CLI       | 5.3.0   | Bug fix     | Set the correct defaults for verbose flag |
+| CLI       | 5.3.0   | Bug fix     | Fix the replication slots check in `check-health` command in a scenario where cluster is reduced to a single node and the node is a witness node |
+| Proxy     | 5.3.0   | Enhancement | Add the default service unit file with pgd-proxy package |
+| Proxy     | 5.3.0   | Bug fix     | Always set the server conn close behaviour to discard unsent or unacknowledged data at the time of connection creation itself. Earlier, this was set only on client conn error. However, this could cause undesired behaviour specially in situation like n/w partition. (BDR-4060) |
+| Proxy     | 5.3.0   | Bug fix     | Add a retry delay to node watcher for all failed nodes (BDR-3978) |
+| Utilities | 1.2.0   | Enhancement | Add support for pg_upgrade of BDR 3.7 |
+| Utilities | 1.2.0   | Bug fix     | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level (BDR-4159) |
\ No newline at end of file

From 301807c1e72f9da2234ccfc1d27ea4b7c99ad0e1 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Wed, 1 Nov 2023 09:14:16 +0000
Subject: [PATCH 20/38] Layout refresh, current BDR 5.3 relnotes added

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 .../pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx   | 62 ++++++++++++++-----
 1 file changed, 46 insertions(+), 16 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 24321834318..54aa073cc13 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -7,25 +7,55 @@ Released: 14 Nov 2023
 
 EDB Postgres Distributed version 5.3.0 is a minor version of EDB Postgres Distributed.
 
+!!! Important Recommended upgrade
+We recommend that all users of PGD 5 upgrade to PGD 5.3.
+!!!
+
 ## Highlights of EDB Postgres Distributed 5.3.0
 
-<Add the highlights bullet points here>
+* Postgres 16 and EPAS 16 supported
 
-!!! Important Recommended upgrade
-    We recommend that users of PGD 5.2 upgrade to PGD 5.3.
+## Compatibility
 
-!!! Note PostgreSQL version compatibility
-This version is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later.
-!!!
+PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later.
+
+## Features
+
+| Component | Version | Description  | Addresses | 
+|-----------|---------|-------------|-----------|
+| PGD | 5.3.0 | Add support for PostgreSQL 16 server. | |
+
+## Enhancements
+
+| Component | Version  |Description | Addresses |
+|-----------|---------|-------------|-----------|
+| Utilities | 1.2.0   | Add support for pg_upgrade of BDR 3.7 | |
+| Proxy     | 5.3.0   | Add the default service unit file with pgd-proxy package | |
+
+
+## Bug Fixes
+
+| Component | Version |Description  | Addresses | 
+|-----------|---------|-------------|-----------|
+| BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
+| BDR       | 5.3.0   | Ensure that the taskmgr process does not ignore SIGINT. ||
+| BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||
+| BDR       | 5.3.0   | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. ||
+| BDR       | 5.3.0   | Fix a bug in copying bdr.autopartition_rules during logical join. ||
+| BDR       | 5.3.0   | Override bdr.ddl_replication=off in taskmgr worker. ||
+| BDR       | 5.3.0   | Avoid a potential deadlock between `bdr.autopartition_wait_for_partitions()` and taskmgr||
+| BDR       | 5.3.0   | Fix writer missing updates in streaming mode with TDE enabled. ||
+| BDR       | 5.3.0   | Block new EPAS automatic partitioning on PGD cluster. ||
+| BDR       | 5.3.0   | Allow existing automatically partitioned tables when cluster is created or upgraded. ||
+| BDR       | 5.3.0   | Block PGD Autopartition on EPAS INTERVAL partitioned table. ||
+| BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
+| BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
+| BDR       | 5.3.0   | Fix row filter failure for partitions created after a table column was dropped | RT95149 |
+| CLI       | 5.3.0   | Fix `shared_preload_libraries` verification  | |
+| CLI       | 5.3.0   | Set the correct defaults for verbose flag   | |
+| CLI       | 5.3.0   | Fix the replication slots check in `check-health` command in a scenario where cluster is reduced to a single node and the node is a witness node | |
+| Proxy     | 5.3.0   | Always set the server conn close behaviour to discard unsent or unacknowledged data at the time of connection creation itself. Earlier, this was set only on client conn error. However, this could cause undesired behaviour specially in situation like n/w partition. | |
+| Proxy     | 5.3.0   | Add a retry delay to node watcher for all failed nodes | |
+| Utilities | 1.2.0   | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level | |
 
 
-| Component | Version | Type        | Description  |
-|-----------|---------|-------------|--------------|
-| CLI       | 5.3.0   | Bug fix     | Fix `shared_preload_libraries` verification |
-| CLI       | 5.3.0   | Bug fix     | Set the correct defaults for verbose flag |
-| CLI       | 5.3.0   | Bug fix     | Fix the replication slots check in `check-health` command in a scenario where cluster is reduced to a single node and the node is a witness node |
-| Proxy     | 5.3.0   | Enhancement | Add the default service unit file with pgd-proxy package |
-| Proxy     | 5.3.0   | Bug fix     | Always set the server conn close behaviour to discard unsent or unacknowledged data at the time of connection creation itself. Earlier, this was set only on client conn error. However, this could cause undesired behaviour specially in situation like n/w partition. (BDR-4060) |
-| Proxy     | 5.3.0   | Bug fix     | Add a retry delay to node watcher for all failed nodes (BDR-3978) |
-| Utilities | 1.2.0   | Enhancement | Add support for pg_upgrade of BDR 3.7 |
-| Utilities | 1.2.0   | Bug fix     | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level (BDR-4159) |
\ No newline at end of file

From 35dca4b2a4d834b467c6e8a40215a9be762fab4a Mon Sep 17 00:00:00 2001
From: Jagdish Kewat <jagdish.kewat@enterprisedb.com>
Date: Wed, 1 Nov 2023 16:23:59 +0530
Subject: [PATCH 21/38] Update rel notes description

---
 .../pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx   | 21 +++++++------------
 1 file changed, 8 insertions(+), 13 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 54aa073cc13..09eef476dd3 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -21,7 +21,7 @@ PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8
 
 ## Features
 
-| Component | Version | Description  | Addresses | 
+| Component | Version | Description  | Addresses |
 |-----------|---------|-------------|-----------|
 | PGD | 5.3.0 | Add support for PostgreSQL 16 server. | |
 
@@ -29,13 +29,11 @@ PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8
 
 | Component | Version  |Description | Addresses |
 |-----------|---------|-------------|-----------|
-| Utilities | 1.2.0   | Add support for pg_upgrade of BDR 3.7 | |
-| Proxy     | 5.3.0   | Add the default service unit file with pgd-proxy package | |
-
+| Proxy     | 5.3.0   | Add the default service unit file to package | |
 
 ## Bug Fixes
 
-| Component | Version |Description  | Addresses | 
+| Component | Version |Description  | Addresses |
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
 | BDR       | 5.3.0   | Ensure that the taskmgr process does not ignore SIGINT. ||
@@ -51,11 +49,8 @@ PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8
 | BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
 | BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
 | BDR       | 5.3.0   | Fix row filter failure for partitions created after a table column was dropped | RT95149 |
-| CLI       | 5.3.0   | Fix `shared_preload_libraries` verification  | |
-| CLI       | 5.3.0   | Set the correct defaults for verbose flag   | |
-| CLI       | 5.3.0   | Fix the replication slots check in `check-health` command in a scenario where cluster is reduced to a single node and the node is a witness node | |
-| Proxy     | 5.3.0   | Always set the server conn close behaviour to discard unsent or unacknowledged data at the time of connection creation itself. Earlier, this was set only on client conn error. However, this could cause undesired behaviour specially in situation like n/w partition. | |
-| Proxy     | 5.3.0   | Add a retry delay to node watcher for all failed nodes | |
-| Utilities | 1.2.0   | Remove the pre-upgrade step which alters the CONNECTION LIMIT to 0 at database level | |
-
-
+| CLI       | 5.3.0   | Fix `verify-settings` command if the `shared_preload_libraries` GUC contains file path | |
+| CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced to a single node and it is a witness node | |
+| Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |
+| Proxy     | 5.3.0   | Fix the logs fill up issue when all nodes are down in a PGD cluster | |
+| Utilities | 1.2.0   | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |
\ No newline at end of file

From 67c680aa32f70d83453cbc363cb2278f9597d366 Mon Sep 17 00:00:00 2001
From: Markus Wanner <markus.wanner@enterprisedb.com>
Date: Wed, 1 Nov 2023 16:30:19 +0100
Subject: [PATCH 22/38] Update version compatibility notes in PGD 5.3 release
 notes

---
 .../docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx       | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 09eef476dd3..95d7a7d5989 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -17,7 +17,14 @@ We recommend that all users of PGD 5 upgrade to PGD 5.3.
 
 ## Compatibility
 
-PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8, and later.
+!!! Note PostgreSQL version compatibility
+This version requires the recently released Postgres versions 14.10, 15.4,
+or 16.1 (or later) of EDB Postgres Advanced Server or EDB Postgres Extended
+Server. No such restrictions exist for PostgreSQL Server.
+
+Package managers on Debian, RHEL, and SLES pull in the required EPAS or PGE
+upgrades with an upgrade of Postgres Distributed.
+!!!
 
 ## Features
 
@@ -30,6 +37,7 @@ PGD 5.3 is required for EDB Postgres Advanced Server versions 12.15, 13.11, 14.8
 | Component | Version  |Description | Addresses |
 |-----------|---------|-------------|-----------|
 | Proxy     | 5.3.0   | Add the default service unit file to package | |
+| BDR       | 5.3.0   | Dependencies on EPAS and PGE are now reflected in packages. | |
 
 ## Bug Fixes
 

From e29bd06d53ebbb2df566f600e4f5ec6591f16c61 Mon Sep 17 00:00:00 2001
From: Markus Wanner <markus.wanner@enterprisedb.com>
Date: Wed, 1 Nov 2023 16:37:21 +0100
Subject: [PATCH 23/38] PGD 5 docs: Update upgrade paths to 5.x

---
 product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx
index b2a0b0d8202..489deeb5943 100644
--- a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx
+++ b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx
@@ -21,8 +21,8 @@ release before upgrading to the latest version 5 release. After upgrading to
 | ---- | -- |
 | 4.3.0 | 5.0.0 or later |
 | 4.3.1 | 5.1.0 or later |
-| 4.3.2 | Upgrade to 5.3 (once it is released) |
-
+| 4.3.2 | 5.1.0 or later |
+| 4.3.3 | 5.1.0 or later |
 
 ## Upgrading from version 3.7 to version 5
 

From f105bb2d4cb47dbb9659dd43816cea659e785aa0 Mon Sep 17 00:00:00 2001
From: Rahila Syed <rahila.syed@enterprisedb.com>
Date: Thu, 2 Nov 2023 15:50:37 +0530
Subject: [PATCH 24/38] Add release note entry for change in BDR-3814

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 95d7a7d5989..a38b9c95649 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -57,6 +57,7 @@ upgrades with an upgrade of Postgres Distributed.
 | BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
 | BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
 | BDR       | 5.3.0   | Fix row filter failure for partitions created after a table column was dropped | RT95149 |
+| BDR       | 5.3.0   | Avoid aborting a group commit transaction on receiving the first abort response, the other nodes are given a chance to respond and transaction can succeed if the required responses are received ||
 | CLI       | 5.3.0   | Fix `verify-settings` command if the `shared_preload_libraries` GUC contains file path | |
 | CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced to a single node and it is a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |

From e7e6adf03019f1a92436055a6a6af0fbba11b8c9 Mon Sep 17 00:00:00 2001
From: Petr Jelinek <petr.jelinek@enterprisedb.com>
Date: Thu, 2 Nov 2023 16:33:42 +0100
Subject: [PATCH 25/38] Update pgd_5.3.0_rel_notes.mdx

Added some bug fixes that seemed missing
---
 .../docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx    | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index a38b9c95649..aefb366a5a0 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -44,6 +44,8 @@ upgrades with an upgrade of Postgres Distributed.
 | Component | Version |Description  | Addresses |
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
+| BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. | RT78928 |
+| BDR       | 5.3.0   | Fix unsafe CAMO decisions in remote_write mode. ||
 | BDR       | 5.3.0   | Ensure that the taskmgr process does not ignore SIGINT. ||
 | BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||
 | BDR       | 5.3.0   | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. ||
@@ -56,10 +58,17 @@ upgrades with an upgrade of Postgres Distributed.
 | BDR       | 5.3.0   | Block PGD Autopartition on EPAS INTERVAL partitioned table. ||
 | BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
 | BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
+| BDR       | 5.3.0   | Fix memory leak in streaming transaction processing. ||
+| BDR       | 5.3.0   | Allow force parting of nodes that are already being parted normally. ||
+| BDR       | 5.3.0   | Fix nodes getting stuck on PART_CATCHUP due to replication slot conflict. ||
+| BDR       | 5.3.0   | Fix nodes getting stuck on PART_CATCHUP due to node_catchup_info conflict. ||
 | BDR       | 5.3.0   | Fix row filter failure for partitions created after a table column was dropped | RT95149 |
 | BDR       | 5.3.0   | Avoid aborting a group commit transaction on receiving the first abort response, the other nodes are given a chance to respond and transaction can succeed if the required responses are received ||
-| CLI       | 5.3.0   | Fix `verify-settings` command if the `shared_preload_libraries` GUC contains file path | |
+| BDR       | 5.3.0   | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. ||
+| BDR       | 5.3.0   | Prevent duplicate Raft request ID generation which could break replication. ||
+| BDR       | 5.3.0   | Fix several rare memory access issues that could potentially cause crashes of workers. ||
+| CLI       | 5.3.0   | Fix `verify-settings` command if the `shared_preload_libraries` GUC contains file path ||
 | CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced to a single node and it is a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |
 | Proxy     | 5.3.0   | Fix the logs fill up issue when all nodes are down in a PGD cluster | |
-| Utilities | 1.2.0   | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |
\ No newline at end of file
+| Utilities | 1.2.0   | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |

From c421dce2798c48ae8cd5a79dde801018380beee0 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Thu, 2 Nov 2023 16:20:23 +0000
Subject: [PATCH 26/38] Apply suggestions from code review

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index aefb366a5a0..93ee6b45e2c 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -13,11 +13,11 @@ We recommend that all users of PGD 5 upgrade to PGD 5.3.
 
 ## Highlights of EDB Postgres Distributed 5.3.0
 
-* Postgres 16 and EPAS 16 supported
+* Postgres 16, PGE 16 and EPAS 16 supported
 
 ## Compatibility
 
-!!! Note PostgreSQL version compatibility
+!!! Note EDB Server version compatibility
 This version requires the recently released Postgres versions 14.10, 15.4,
 or 16.1 (or later) of EDB Postgres Advanced Server or EDB Postgres Extended
 Server. No such restrictions exist for PostgreSQL Server.

From d72afab46b473970b0886ba906d554ac2fb2f827 Mon Sep 17 00:00:00 2001
From: Petr Jelinek <petr.jelinek@enterprisedb.com>
Date: Mon, 6 Nov 2023 23:24:19 +0100
Subject: [PATCH 27/38] Update pgd_5.3.0_rel_notes.mdx

Add selrep fix
---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 93ee6b45e2c..2f4deba396e 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -57,6 +57,7 @@ upgrades with an upgrade of Postgres Distributed.
 | BDR       | 5.3.0   | Allow existing automatically partitioned tables when cluster is created or upgraded. ||
 | BDR       | 5.3.0   | Block PGD Autopartition on EPAS INTERVAL partitioned table. ||
 | BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
+| BDR       | 5.3.0   | Fix default selective replication behavior for data groups. The data groups are supposed to publish only replication sets of the group or any parent groups by default, which mirrors to what they subscribe. ||
 | BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
 | BDR       | 5.3.0   | Fix memory leak in streaming transaction processing. ||
 | BDR       | 5.3.0   | Allow force parting of nodes that are already being parted normally. ||

From c057834590da3876a32c877de8ad7d425dbabe49 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Thu, 9 Nov 2023 10:08:40 +0000
Subject: [PATCH 28/38] Add link to upgrades

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 2f4deba396e..ee029505174 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -8,7 +8,7 @@ Released: 14 Nov 2023
 EDB Postgres Distributed version 5.3.0 is a minor version of EDB Postgres Distributed.
 
 !!! Important Recommended upgrade
-We recommend that all users of PGD 5 upgrade to PGD 5.3.
+We recommend that all users of PGD 5 upgrade to PGD 5.3. See [PGD upgrades](../upgrades) for details.
 !!!
 
 ## Highlights of EDB Postgres Distributed 5.3.0

From dde34302a7971c057100c443075c0b9e68534cb5 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Thu, 9 Nov 2023 17:12:58 +0000
Subject: [PATCH 29/38] First review pass on notes for styles

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 .../pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx   | 38 ++++++++++---------
 1 file changed, 20 insertions(+), 18 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index ee029505174..1869a54d8cf 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -36,7 +36,7 @@ upgrades with an upgrade of Postgres Distributed.
 
 | Component | Version  |Description | Addresses |
 |-----------|---------|-------------|-----------|
-| Proxy     | 5.3.0   | Add the default service unit file to package | |
+| Proxy     | 5.3.0   | Added the default service unit file to package | |
 | BDR       | 5.3.0   | Dependencies on EPAS and PGE are now reflected in packages. | |
 
 ## Bug Fixes
@@ -44,32 +44,34 @@ upgrades with an upgrade of Postgres Distributed.
 | Component | Version |Description  | Addresses |
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
-| BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. | RT78928 |
-| BDR       | 5.3.0   | Fix unsafe CAMO decisions in remote_write mode. ||
-| BDR       | 5.3.0   | Ensure that the taskmgr process does not ignore SIGINT. ||
+| BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode.<sup>1</sup>  | RT78928 |
+| BDR       | 5.3.0   | Fixed unsafe CAMO decisions in remote_write mode. ||
+| BDR       | 5.3.0   | Taskmgr process now respects SIGINT. ||
 | BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||
-| BDR       | 5.3.0   | Clean up stale records in bdr.taskmgr_local_work_queue during physical join. ||
-| BDR       | 5.3.0   | Fix a bug in copying bdr.autopartition_rules during logical join. ||
+| BDR       | 5.3.0   | Physical joins now clean up stale records in bdr.taskmgr_local_work_queue. ||
+| BDR       | 5.3.0   | Fixed a bug in copying bdr.autopartition_rules during logical join. ||
 | BDR       | 5.3.0   | Override bdr.ddl_replication=off in taskmgr worker. ||
 | BDR       | 5.3.0   | Avoid a potential deadlock between `bdr.autopartition_wait_for_partitions()` and taskmgr||
-| BDR       | 5.3.0   | Fix writer missing updates in streaming mode with TDE enabled. ||
+| BDR       | 5.3.0   | Fixed writer missing updates in streaming mode with TDE enabled. ||
 | BDR       | 5.3.0   | Block new EPAS automatic partitioning on PGD cluster. ||
 | BDR       | 5.3.0   | Allow existing automatically partitioned tables when cluster is created or upgraded. ||
 | BDR       | 5.3.0   | Block PGD Autopartition on EPAS INTERVAL partitioned table. ||
 | BDR       | 5.3.0   | Ensure that replication does not break when bdr.autopartition() is invoked on a mixed version cluster, running with 3.7.23 and 4.3.3/5.3 ||
-| BDR       | 5.3.0   | Fix default selective replication behavior for data groups. The data groups are supposed to publish only replication sets of the group or any parent groups by default, which mirrors to what they subscribe. ||
-| BDR       | 5.3.0   | Fix memory leak in LCR file TDE encryption. ||
-| BDR       | 5.3.0   | Fix memory leak in streaming transaction processing. ||
+| BDR       | 5.3.0   | Fixed default selective replication behavior for data groups. The data groups are supposed to publish only replication sets of the group or any parent groups by default, which mirrors to what they subscribe. ||
+| BDR       | 5.3.0   | Fixed memory leak in LCR file TDE encryption. ||
+| BDR       | 5.3.0   | Fixed memory leak in streaming transaction processing. ||
 | BDR       | 5.3.0   | Allow force parting of nodes that are already being parted normally. ||
-| BDR       | 5.3.0   | Fix nodes getting stuck on PART_CATCHUP due to replication slot conflict. ||
-| BDR       | 5.3.0   | Fix nodes getting stuck on PART_CATCHUP due to node_catchup_info conflict. ||
-| BDR       | 5.3.0   | Fix row filter failure for partitions created after a table column was dropped | RT95149 |
+| BDR       | 5.3.0   | PART_CATCHUP is now more resilient to replication slot and node_catchup_info conflict. ||
+| BDR       | 5.3.0   | Fixed row filter failure for partitions created after a table column was dropped | RT95149 |
 | BDR       | 5.3.0   | Avoid aborting a group commit transaction on receiving the first abort response, the other nodes are given a chance to respond and transaction can succeed if the required responses are received ||
 | BDR       | 5.3.0   | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. ||
 | BDR       | 5.3.0   | Prevent duplicate Raft request ID generation which could break replication. ||
-| BDR       | 5.3.0   | Fix several rare memory access issues that could potentially cause crashes of workers. ||
-| CLI       | 5.3.0   | Fix `verify-settings` command if the `shared_preload_libraries` GUC contains file path ||
-| CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced to a single node and it is a witness node | |
+| BDR       | 5.3.0   | Fixed several rare memory access issues that could potentially cause crashes of workers. ||
+| CLI       | 5.3.0   | Fixed `verify-settings` command if the `shared_preload_libraries` GUC contains file path ||
+| CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced just a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |
-| Proxy     | 5.3.0   | Fix the logs fill up issue when all nodes are down in a PGD cluster | |
-| Utilities | 1.2.0   | Remove the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |
+| Proxy     | 5.3.0   | Fixed the logs fill up issue when all nodes are down in a PGD cluster | |
+| Utilities | 1.2.0   | Removed the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |
+
+
+1: This solves the split brain problem when deciding fate of transactions that happened during failover.

From 703aa8bd90b082b16757eed204d3f349445b69e7 Mon Sep 17 00:00:00 2001
From: Ricardo Ferreira <ricardo.ferreira@enterprisedb.com>
Date: Thu, 9 Nov 2023 17:27:01 +0000
Subject: [PATCH 30/38] Added note for BDR-4312.

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 1869a54d8cf..f3104591cae 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -67,6 +67,7 @@ upgrades with an upgrade of Postgres Distributed.
 | BDR       | 5.3.0   | Ensure that replication receiver worker reloads configuration correctly when `pg_reload_conf()` is called. ||
 | BDR       | 5.3.0   | Prevent duplicate Raft request ID generation which could break replication. ||
 | BDR       | 5.3.0   | Fixed several rare memory access issues that could potentially cause crashes of workers. ||
+| BDR       | 5.3.0   | Fixed issue where explicit 2PC transactions would abort earlier when encountering conflicts. | RT92897 |
 | CLI       | 5.3.0   | Fixed `verify-settings` command if the `shared_preload_libraries` GUC contains file path ||
 | CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced just a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |

From 4bb1df8326c97888d7c7fffd957fdc5a18bb6ab5 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Mon, 13 Nov 2023 11:20:01 +0000
Subject: [PATCH 31/38] Removed temp subscript, small rewording.

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 .../docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx     | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index f3104591cae..55452712c4e 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -8,12 +8,12 @@ Released: 14 Nov 2023
 EDB Postgres Distributed version 5.3.0 is a minor version of EDB Postgres Distributed.
 
 !!! Important Recommended upgrade
-We recommend that all users of PGD 5 upgrade to PGD 5.3. See [PGD upgrades](../upgrades) for details.
+We recommend that all users of PGD 5 upgrade to PGD 5.3. See [PGD/TPA upgrades](../upgrades/tpa_overview) for details.
 !!!
 
 ## Highlights of EDB Postgres Distributed 5.3.0
 
-* Postgres 16, PGE 16 and EPAS 16 supported
+* Support for PostgreSQL 16 server, EDB Postgres Extended Server 16 and EDB Postgres Advanced Server 16
 
 ## Compatibility
 
@@ -30,7 +30,7 @@ upgrades with an upgrade of Postgres Distributed.
 
 | Component | Version | Description  | Addresses |
 |-----------|---------|-------------|-----------|
-| PGD | 5.3.0 | Add support for PostgreSQL 16 server. | |
+| PGD | 5.3.0 | Add support for PostgreSQL 16 server, , EDB Postgres Extended Server 16 and EDB Postgres Advanced Server 16. | |
 
 ## Enhancements
 
@@ -44,7 +44,7 @@ upgrades with an upgrade of Postgres Distributed.
 | Component | Version |Description  | Addresses |
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
-| BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode.<sup>1</sup>  | RT78928 |
+| BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. | RT78928 |
 | BDR       | 5.3.0   | Fixed unsafe CAMO decisions in remote_write mode. ||
 | BDR       | 5.3.0   | Taskmgr process now respects SIGINT. ||
 | BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||
@@ -72,7 +72,5 @@ upgrades with an upgrade of Postgres Distributed.
 | CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced just a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |
 | Proxy     | 5.3.0   | Fixed the logs fill up issue when all nodes are down in a PGD cluster | |
-| Utilities | 1.2.0   | Removed the pre-upgrade step which sets the CONNECTION LIMIT to 0 at database level in `bdr_pg_upgrade` | |
+| Utilities | 1.2.0   | Removed the pre-upgrade step in `bdr_pg_upgrade` which sets the CONNECTION LIMIT to 0 at database level | |
 
-
-1: This solves the split brain problem when deciding fate of transactions that happened during failover.

From baf5671c94c6cbfe68d8324d8997c195509827ba Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Mon, 13 Nov 2023 12:02:20 +0000
Subject: [PATCH 32/38] Remove loose comma

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 55452712c4e..5936fd0d1ff 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -30,7 +30,7 @@ upgrades with an upgrade of Postgres Distributed.
 
 | Component | Version | Description  | Addresses |
 |-----------|---------|-------------|-----------|
-| PGD | 5.3.0 | Add support for PostgreSQL 16 server, , EDB Postgres Extended Server 16 and EDB Postgres Advanced Server 16. | |
+| PGD | 5.3.0 | Add support for PostgreSQL 16 server, EDB Postgres Extended Server 16 and EDB Postgres Advanced Server 16. | |
 
 ## Enhancements
 

From 6cbd15cb03e7c7e781a9cea898fee38b846aa4e7 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Mon, 13 Nov 2023 18:13:03 +0000
Subject: [PATCH 33/38] Late update

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 5936fd0d1ff..0ea16b83b00 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -45,6 +45,7 @@ upgrades with an upgrade of Postgres Distributed.
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
 | BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. | RT78928 |
+| BDR       | 5.3.0   | Handle partitions with different attribute numbers when batch inserting. | RT991155 | 
 | BDR       | 5.3.0   | Fixed unsafe CAMO decisions in remote_write mode. ||
 | BDR       | 5.3.0   | Taskmgr process now respects SIGINT. ||
 | BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||

From fb85ad31c0a3c0e66e25a796fb0aba34bca5ef38 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Mon, 13 Nov 2023 18:15:58 +0000
Subject: [PATCH 34/38] typo fix

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index 0ea16b83b00..a28d5fc4840 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -45,7 +45,7 @@ upgrades with an upgrade of Postgres Distributed.
 |-----------|---------|-------------|-----------|
 | BDR       | 5.3.0   | Ensure that the WalSender process does not request locks on the partitions, thus avoiding a deadlock with user process waiting on sync commit. | RT97952 |
 | BDR       | 5.3.0   | Only consider CAMO transactions to be asynchronous when the CAMO setup was degraded to local mode. This solves the split brain problem when deciding fate of transactions that happened during failover. | RT78928 |
-| BDR       | 5.3.0   | Handle partitions with different attribute numbers when batch inserting. | RT991155 | 
+| BDR       | 5.3.0   | Handle partitions with different attribute numbers when batch inserting. | RT99115 | 
 | BDR       | 5.3.0   | Fixed unsafe CAMO decisions in remote_write mode. ||
 | BDR       | 5.3.0   | Taskmgr process now respects SIGINT. ||
 | BDR       | 5.3.0   | Speed up manager process startup by limiting the amount of WAL read for loading commit decisions. ||

From 22be4aa564882c1a6767fc7b4c026f7d260cea69 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Tue, 14 Nov 2023 09:47:02 +0000
Subject: [PATCH 35/38] Update
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx

---
 product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
index a28d5fc4840..2c612709788 100644
--- a/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
+++ b/product_docs/docs/pgd/5/rel_notes/pgd_5.3.0_rel_notes.mdx
@@ -70,7 +70,7 @@ upgrades with an upgrade of Postgres Distributed.
 | BDR       | 5.3.0   | Fixed several rare memory access issues that could potentially cause crashes of workers. ||
 | BDR       | 5.3.0   | Fixed issue where explicit 2PC transactions would abort earlier when encountering conflicts. | RT92897 |
 | CLI       | 5.3.0   | Fixed `verify-settings` command if the `shared_preload_libraries` GUC contains file path ||
-| CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced just a witness node | |
+| CLI       | 5.3.0   | Show replslots status as `Critical` in `check-health` command when PGD cluster is reduced to just a witness node | |
 | Proxy     | 5.3.0   | Always set the server connection close behavior (setLinger(0)), earlier it was set only on client error | |
 | Proxy     | 5.3.0   | Fixed the logs fill up issue when all nodes are down in a PGD cluster | |
 | Utilities | 1.2.0   | Removed the pre-upgrade step in `bdr_pg_upgrade` which sets the CONNECTION LIMIT to 0 at database level | |

From ddd9b0e302cdb2508ae3e9d92e4a7475dbcc56b2 Mon Sep 17 00:00:00 2001
From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com>
Date: Thu, 19 Oct 2023 13:15:09 -0400
Subject: [PATCH 36/38] edits to Migration Portal conten

---
 .../mp_4.6.0_rel_notes.mdx                    | 25 +++++++++----------
 .../migration_portal/4/known_issues_notes.mdx |  6 ++---
 2 files changed, 15 insertions(+), 16 deletions(-)

diff --git a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx
index 4f68e42b212..f31c8b414c8 100644
--- a/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx
+++ b/product_docs/docs/migration_portal/4/01_mp_release_notes/mp_4.6.0_rel_notes.mdx
@@ -10,25 +10,24 @@ New features, enhancements, bug fixes, and other changes in Migration Portal 4.6
 |     Type     |                                                                                                            Description                                                                                                            |
 | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Enhancement  | Improved performance of the schema parsing phase for large schema files that contain a large number of Oracle objects.                                                                                                            |
-| Enhancement  | Migration Portal now supports the assessment and migration of the `DEFAULT` profile.                                                                                                                                              |
-| Enhancement  | A new repair handler (ERH-2104) has been added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument.                                                                                             |
-| Enhancement  | A new repair handler (ERH-2105) has been added that encloses parentheses around the value of the `IN` clause inside `SELECT` statements.                                                                                          |
-| Bug&nbsp;Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable names updated in the `REFERENCING` clause by the repair handler were not correspondingly updated in the `WHEN` clause of the trigger definition.           |
+| Enhancement  | Migration Portal now supports assessing and migrating the `DEFAULT` profile.                                                                                                                                              |
+| Enhancement  | A new repair handler (ERH-2104) was added that replaces `XMLTable` with `XMLParse` if the `XMLTable` call has a single argument.                                                                                             |
+| Enhancement  | A new repair handler (ERH-2105) was added that puts parentheses around the value of the `IN` clause inside `SELECT` statements.                                                                                          |
+| Bug&nbsp;Fix | Fixed the ERH-2030 repair handler issue where the NEW and OLD variable names updated in the `REFERENCING` clause by the repair handler weren't also updated in the `WHEN` clause of the trigger definition.           |
 | Bug&nbsp;Fix | Fixed the ERH-2065 repair handler to remove the `INMEMORY` and `NO INMEMORY` clauses from the `SUBPARTITION TEMPLATE` clause.                                                                                                     |
-| Bug&nbsp;Fix | Fixed the ERH-2002 repair handler issue where it was not being applied in some scenarios.                                                                                                                                         |
-| Bug&nbsp;Fix | Fixed the ERH-2009 repair handler issue where it was not being applied in some scenarios.                                                                                                                                         |
-| Bug&nbsp;Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects was not handled in the parsing phase.                                                                                          |
-| Bug&nbsp;Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements were not getting removed from the uploaded source DDL scripts.                                                                                                      |
-| Bug&nbsp;Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it is supported in EDB Postgres Advanced Server.                                                                                    |
+| Bug&nbsp;Fix | Fixed the ERH-2002 repair handler issue where it wasn't being applied in some scenarios.                                                                                                                                         |
+| Bug&nbsp;Fix | Fixed the ERH-2009 repair handler issue where it wasn't being applied in some scenarios.                                                                                                                                         |
+| Bug&nbsp;Fix | Fixed the issue where the occurrence of the `UTL_HTTP.END_OF_BODY` exception inside PL/SQL objects wasn't handled in the parsing phase.                                                                                          |
+| Bug&nbsp;Fix | Fixed the issue where `GRANT EXECUTE ON DIRECTORY` statements weren't getting removed from the uploaded source DDL scripts.                                                                                                      |
+| Bug&nbsp;Fix | Fixed the issue where the `XMLRoot` function was incorrectly flagged as incompatible although it's supported in EDB Postgres Advanced Server.                                                                                    |
 | Bug&nbsp;Fix | Fixed the issue where an assessment fails because of an `OutOfMemoryError` exception in some scenarios.                                                                                                                           |
 | Bug&nbsp;Fix | Fixed parsing issues related to the usage of the `REMARK`, `HOST` and `PROMPT` keywords in schema files.                                                                                                                          |
-| Bug&nbsp;Fix | Fixed the issue where column names inside check constraints were not getting double-quoted when the **Use Oracle's default case for schema migration** option was selected for the project.                                       |
-| Bug&nbsp;Fix | Fixed the EDB DDL Extractor script so that it performs the permission check  prior to performing the Oracle version check and actual schema extraction.                                                                           |
+| Bug&nbsp;Fix | Fixed the issue where column names inside check constraints weren't double-quoted when the **Use Oracle's default case for schema migration** option was selected for the project.                                       |
+| Bug&nbsp;Fix | Fixed the EDB DDL Extractor script so that it performs the permission check prior to performing the Oracle version check and actual schema extraction.                                                                           |
 | Bug&nbsp;Fix | Updated the DDL parser to comment out `GRANT RESOURCE` statements generated for roles without a schema.                                                                                                                           |
 
-## End-of-support notice ##
+## End-of-support notice
 
 EDB Postgres Advanced Server version 11 standard support is ending by November 20, 2023. Support for EDB Postgres Advanced Sever version 11 was removed from Migration Portal on May 20, 2023 to ensure that no new EDB Postgres Advanced Server version 11 projects were created after this date.
 
 To maximize the length of available support and to take advantage of new features, particularly those that provide added compatibility with Oracle, we recommend selecting the latest EDB Postgres Advanced Server version as the target of a Migration Portal project. See the [EDB Platform Compatibility page](https://www.enterprisedb.com/resources/platform-compatibility) for more information on the support periods for each EDB Postgres Advanced Server major version.
-
diff --git a/product_docs/docs/migration_portal/4/known_issues_notes.mdx b/product_docs/docs/migration_portal/4/known_issues_notes.mdx
index 9e30dc94648..ecf6ef68ca4 100644
--- a/product_docs/docs/migration_portal/4/known_issues_notes.mdx
+++ b/product_docs/docs/migration_portal/4/known_issues_notes.mdx
@@ -4,7 +4,7 @@ redirects:
  - /migration_portal/latest/04_mp_migrating_database/01_mp_schema_extraction/known_issues_notes/
 ---
 
-This page lists known issues, limitations, and notes for:
+These are the known issues, limitations, and notes for:
 
  - [Migration Portal](#migration-portal)  
  - [EDB DDL Extractor](#edb-ddl-extractor) 
@@ -53,10 +53,10 @@ When migrating users, the Migration Portal does not migrate the users' passwords
 
 #### Profiles
 
-The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits.  EDB Postgres Advanced Server only supports the Oracle password related limits.  Resource limits are extracted with the profiles, but the Migration Portal only uploads, assesses, and migrates the password limits.  Also, the `DEFAULT` profile may have been overridden in the Oracle database with new limit values. The EDB DDL Extractor extracts `ALTER PROFILE` statements for `DEFAULT` profiles that are overridden in the Oracle database, and the Migration Portal attempts to apply these statements in the target EDB Postgres Advanced Server database. If the schema is being migrated to an EDB Postgres Advanced Server instance with existing users and databases, we recommend that the settings of the `ALTER PROFILE DEFAULT` statement be verified and updated, if necessary, before migrating the DDL to the target database.
+The Migration Portal migrates non-`DEFAULT` profiles assigned to the schema users. Oracle profiles include both password and resource limits. EDB Postgres Advanced Server supports only the Oracle password-related limits.  Resource limits are extracted with the profiles, but the Migration Portal uploads, assesses, and migrates only the password limits.  Also, the `DEFAULT` profile might be overridden in the Oracle database with new limit values. The EDB DDL Extractor extracts `ALTER PROFILE` statements for `DEFAULT` profiles that are overridden in the Oracle database, and the Migration Portal attempts to apply these statements in the target EDB Postgres Advanced Server database. If the schema is being migrated to an EDB Postgres Advanced Server instance with existing users and databases, we recommend that the settings of the `ALTER PROFILE DEFAULT` statement be verified and updated, if necessary, before migrating the DDL to the target database.
 
 !!! Note
-    Starting with version 4.3.0, the Migration Portal supports assessment of users, roles, profiles, and grants. However for the projects created using an earlier version (earlier than 4.3.0) of the Migration Portal, this capability is not supported. In order to assess the users, roles, profiles, and grants, use the latest version of the EDB DDL Extractor and create a new project.
+    Starting with version 4.3.0, the Migration Portal supports assessment of users, roles, profiles, and grants. However, for the projects created using a version earlier than 4.3.0 of the Migration Portal, this capability isn't supported. To assess the users, roles, profiles, and grants, use the latest version of the EDB DDL Extractor and create a new project.
 
 
 ### Using Oracle default case

From 137d451dd372cea04ccb0e584b7b042100e646ae Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Tue, 14 Nov 2023 12:05:31 +0000
Subject: [PATCH 37/38] Mop up fixes post test deploy

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/3.7/bdr/release-notes.mdx   | 2 +-
 product_docs/docs/pgd/5/overview/index.mdx        | 2 +-
 product_docs/docs/pgd/5/upgrades/tpa_overview.mdx | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
index 578b9c874ee..bd6442eca68 100644
--- a/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
+++ b/product_docs/docs/pgd/3.7/bdr/release-notes.mdx
@@ -77,7 +77,7 @@ This is a maintenance release for BDR 3.7 that includes minor
 improvements as well as fixes for issues identified in previous
 versions.
 
-Also check the release notes for [pglogical 3.7.21](/pgd/3.7/pglogical/release-notes/#pglogical-372PG1) for resolved issues
+Also check the release notes for [pglogical 3.7.21](/pgd/3.7/pglogical/release-notes/#pglogical-3721) for resolved issues
 that affect BDR as well.
 
 
diff --git a/product_docs/docs/pgd/5/overview/index.mdx b/product_docs/docs/pgd/5/overview/index.mdx
index 3e7553a1cf9..0a6ba064fef 100644
--- a/product_docs/docs/pgd/5/overview/index.mdx
+++ b/product_docs/docs/pgd/5/overview/index.mdx
@@ -81,7 +81,7 @@ In the future, one node will be elected as the main replicator to other groups,
 
 ### Supported Postgres database servers
 
-PGD is compatible with [PostgreSQL](https://www.postgresql.org/), [EDB Postgres Extended Server](https://techsupport.enterprisedb.com/customer_portal/sw/2ndqpostgres/) and [EDB Postgres Advanced Server](/epas/latest) and is deployed as a standard Postgres extension named BDR. See the [Compatibility matrix](../#compatibility-matrix) for details of supported version combinations.
+PGD is compatible with [PostgreSQL](https://www.postgresql.org/), [EDB Postgres Extended Server](https://techsupport.enterprisedb.com/customer_portal/sw/2ndqpostgres/) and [EDB Postgres Advanced Server](/epas/latest) and is deployed as a standard Postgres extension named BDR. See  [Compatibility](../#compatibility) for details of supported version combinations.
 
 Some key PGD features depend on certain core capabilities being available in the target Postgres database server. Therefore, PGD users must also adopt the Postgres database server distribution that's best suited to their business needs. For example, if having the PGD feature Commit At Most Once (CAMO) is mission critical to your use case, don't adopt the community PostgreSQL distribution. It doesn't have the core capability required to handle CAMO. See the full feature matrix compatibility in [Choosing a Postgres distribution](../choosing_server/).
 
diff --git a/product_docs/docs/pgd/5/upgrades/tpa_overview.mdx b/product_docs/docs/pgd/5/upgrades/tpa_overview.mdx
index dbfada53178..eee519b6fca 100644
--- a/product_docs/docs/pgd/5/upgrades/tpa_overview.mdx
+++ b/product_docs/docs/pgd/5/upgrades/tpa_overview.mdx
@@ -3,7 +3,7 @@ title: Upgrading PGD clusters with TPA
 ---
 
 !!! Note No Postgres Major Version upgrades
-TPA does not currently support major version upgrades of Postgres. The techniques outlined in this section can perform minor version upgrades of the PGD software and minor version upgrades of Postgres. To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](bdr_pg_upgrades).
+TPA does not currently support major version upgrades of Postgres. The techniques outlined in this section can perform minor version upgrades of the PGD software and minor version upgrades of Postgres. To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](bdr_pg_upgrade).
 !!!
 
 If you have used TPA to install your cluster, you can also use TPA to upgrade your cluster. You can read more, in detail, about the capabilities of TPA upgrades in the [Upgrading your cluster](/tpa/latest/tpaexec-upgrade/) section of the TPA manual.

From 538a14fe7a5fd60448d605983d25c2e3bf9acd50 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
Date: Tue, 14 Nov 2023 13:20:20 +0000
Subject: [PATCH 38/38] Added missing 3.7 relnotes

Signed-off-by: Dj Walker-Morgan <dj.walker-morgan@enterprisedb.com>
---
 product_docs/docs/pgd/3.7/pglogical/release-notes.mdx | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
index 7cc7497875d..e613c9ac8b2 100644
--- a/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
+++ b/product_docs/docs/pgd/3.7/pglogical/release-notes.mdx
@@ -12,8 +12,16 @@ improvements as well as fixes for issues identified previously.
 
 ### Resolved Issues
 
+- Fix row filter failure for partitions created after a table column was dropped (RT95149).
+
 ### Upgrades
 
+This release supports upgrading from following versions of pglogical:
+
+ - 3.7.9 and higher
+ - 3.6.29 and higher
+ - 2.4.0 and 2.4.
+
 ## pglogical 3.7.22
 
 This is a maintenance release for pglogical 3.7 which includes minor