Commit 9c533465 authored by Bruce Momjian's avatar Bruce Momjian

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
parent cbb5e23b
...@@ -2388,7 +2388,11 @@ include 'filename' ...@@ -2388,7 +2388,11 @@ include 'filename'
processes). The default is zero, meaning replication is processes). The default is zero, meaning replication is
disabled. WAL sender processes count towards the total number disabled. WAL sender processes count towards the total number
of connections, so the parameter cannot be set higher than 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 be set at server start. <varname>wal_level</> must be set to
<literal>archive</> or higher to allow connections from standby <literal>archive</> or higher to allow connections from standby
servers. servers.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment