Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9c53346

Browse files
committed
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
1 parent cbb5e23 commit 9c53346

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

doc/src/sgml/config.sgml

+5-1
Original file line numberDiff line numberDiff line change
@@ -2388,7 +2388,11 @@ include 'filename'
23882388
processes). The default is zero, meaning replication is
23892389
disabled. WAL sender processes count towards the total number
23902390
of connections, so the parameter cannot be set higher than
2391-
<xref linkend="guc-max-connections">. This parameter can only
2391+
<xref linkend="guc-max-connections">. Abrupt streaming client
2392+
disconnection might cause an orphaned connection slot until
2393+
a timeout is reached, so this parameter should be set slightly
2394+
higher than the maximum number of expected clients so disconnected
2395+
clients can immediately reconnect. This parameter can only
23922396
be set at server start. <varname>wal_level</> must be set to
23932397
<literal>archive</> or higher to allow connections from standby
23942398
servers.

0 commit comments

Comments
 (0)