Merge pull request #2147 from EnterpriseDB/content/bdr/3.7.14/import

Import BDR 3.7.14 docs

product_docs/docs/bdr/3.7/functions.mdx

@@ -56,9 +56,7 @@ Upon session initialization, this is set to the node id the client is
 connected to.  This allows an application to figure out what node it
 is connected to even behind a transparent proxy.
 
-It is also used in combination with CAMO, see the
-[Connection pools and proxies](camo#connection-pools-and-proxies)
-section.
+It is also used in combination with CAMO, see the [Connection pools and proxies](camo#connection-pools-and-proxies) section.
 
 ### bdr.last_committed_lsn
 

product_docs/docs/bdr/3.7/index.mdx

@@ -114,5 +114,3 @@ Some features are only available on particular versions of Postgres server.
 
 Features that are currently available only with EDB Postgres Extended are
 expected to be available with EDB Postgres Advanced 14.
-
-This documentation is for the Enterprise Edition of BDR3.

product_docs/docs/bdr/3.7/known-issues.mdx

@@ -54,11 +54,3 @@ unique identifier.
 -   Decoding Worker feature does not work with CAMO/EAGER
 
 -   Decoding Worker works only with the default replication sets
-
--   When Decoding Worker is enabled in BDR node group and a BDR  node is shutdown
-    in fast mode immediately after starting it, the shutdown may not complete
-    because WAL sender does not exit. This happens because WAL sender waits for
-    WAL decoder to start and WAL decoder may never start since the node is
-    shutting down. The situation can be worked around by using an immediate
-    shutdown or waiting for WAL decoder to start. The WAL decoder process is
-    reported in `pglogical.workers` as well as `pg_stat_activity` catalogs.

product_docs/docs/bdr/3.7/release-notes.mdx

@@ -5,6 +5,84 @@ originalFilePath: release-notes.md
 
 ---
 
+## BDR 3.7.14
+
+This is a maintenance release for BDR 3.7 which includes minor
+improvements as well as fixes for issues identified in previous
+versions.
+
+Check also release notes for pglogical 3.7.14 for resolved issues
+which affect BDR as well.
+
+### Improvements
+
+-   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
+    throttle down repeated attempts to reconnect and checks to once per
+    minute.
+
+-   Ensure CAMO configuration is checked again after a reconnect (EE)
+
+-   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)  
+    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)  
+    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
+    Mode back to CAMO protected (to prevent toggling forth and back due
+    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)  
+    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  
+    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 
+    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 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
+
+### Upgrades
+
+This release supports upgrading from following versions of BDR:
+
+-   3.7.9 and higher
+-   3.6.29
+
+## BDR 3.7.13.1
+
+This is a hotfix release for BDR 3.7.13.
+
+### Resolved Issues
+
+-   Fix potential FATAL error when using global DML locking with CAMO (BDR-1675, BDR-1655)
+
+-   Fix lag calculation for CAMO local mode delay (BDR-1681)
+
 ## BDR 3.7.13
 
 This is a maintenance release for BDR 3.7 which includes minor improvements

product_docs/docs/bdr/3.7/scaling.mdx

@@ -4,8 +4,6 @@ originalFilePath: scaling.md
 
 ---
 
-AutoPartition provides automatic management of partitioned tables.
-
 AutoPartition allows tables to grow easily to large sizes by automatic
 partitioning management. This utilizes the additional features of BDR
 such as low-conflict locking of creating and dropping partitions.

product_docs/docs/bdr/3.7/twophase.mdx

@@ -63,13 +63,4 @@ the second phase from the same node:
 
 ```sql
 COMMIT PREPARED 'some-global-id';
-<<<<<<< HEAD
-```
-
-=======
-
-```
-
->>>>>>> 28b38c3c5e30126e05b09e23103e68e4f874b621
-
 ```