From fc78b30a2957dc23391a5c078427616914112708 Mon Sep 17 00:00:00 2001
From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com>
Date: Fri, 5 Jan 2024 13:46:39 +0000
Subject: [PATCH] Added note on bogus deprecation message.

---
 product_docs/docs/pgd/3.7/bdr/configuration.mdx | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/product_docs/docs/pgd/3.7/bdr/configuration.mdx b/product_docs/docs/pgd/3.7/bdr/configuration.mdx
index cd7d78f67b7..84bb7433b0a 100644
--- a/product_docs/docs/pgd/3.7/bdr/configuration.mdx
+++ b/product_docs/docs/pgd/3.7/bdr/configuration.mdx
@@ -429,10 +429,14 @@ Unless noted otherwise, values may be set by any user at any time.
      Measure round trip time of a bdr consensus request and log an
      `INFO` message if the time exceeds this parameter. Default value
      of this parameter is 5000 ms.
--   `bdr.raft_group_max_connections` - The maximum number of connections
+-   `bdr.group_max_connections` - The maximum number of connections
      across all BDR groups for a Postgres server. These connections carry
      bdr consensus requests between the groups' nodes. Default value of this
      parameter is 100 connections. May only be set at Postgres server start.
+     BDR 3.7.13 and later will emit a warning when setting this variable
+     that it is deprecated and bdr.raft_group_max_connections should be used.
+     Ignore this warning and continue to use bdr.group_max_connections (until
+     you upgrade to BDR 4 and later).
 -   `bdr.backwards_compatibility` - Specifies the version to be
     backwards-compatible to, in the same numerical format as used by
     `bdr.bdr_version_num`, e.g. `30618`.  Enables exact behavior of a