From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 16 Apr 2014 19:06:17 +0000 (-0400)
Subject: docs:  make max_wal_senders higher to handle disconnects
X-Git-Tag: REL9_4_BETA1~161
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9c5334650085d441324e0f4fd9f8db12657b25c7;p=postgresql

docs:  make max_wal_senders higher to handle disconnects

Document abrupt streaming client disconnection might leave slots in use,
so max_wal_senders should be slightly higher than needed to allow for
immediate reconnection.

Per mention by Magnus
---

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 1c25ded436..17ef25b5f6 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2388,7 +2388,11 @@ include 'filename'
         processes). The default is zero, meaning replication is
         disabled. WAL sender processes count towards the total number
         of connections, so the parameter cannot be set higher than
-        <xref linkend="guc-max-connections">.  This parameter can only
+        <xref linkend="guc-max-connections">.  Abrupt streaming client
+        disconnection might cause an orphaned connection slot until
+        a timeout is reached, so this parameter should be set slightly
+        higher than the maximum number of expected clients so disconnected
+        clients can immediately reconnect.  This parameter can only
         be set at server start. <varname>wal_level</> must be set to
         <literal>archive</> or higher to allow connections from standby
         servers.