mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-03-07 19:47:50 +08:00
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
This commit is contained in:
parent
cbb5e23bfa
commit
9c53346500
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user