git.postgresql.org Git - postgresql.git/commitdiff

git projects / postgresql.git / commitdiff

docs: make max_wal_senders higher to handle disconnects

2014年4月16日 19:06:17 +0000 (15:06 -0400)

committer Bruce Momjian <bruce@momjian.us>

2014年4月16日 19:06:49 +0000 (15:06 -0400)

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

doc/src/sgml/config.sgml patch | blob | blame | history

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml

index 1c25ded436d1cd0c97e2872df718e910b5c1d4b9..17ef25b5f6a20f023bbf67f68ce23ece72a6ea4e 100644 (file)

--- 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.

This is the main PostgreSQL git repository.

RSS Atom