From 9c5334650085d441324e0f4fd9f8db12657b25c7 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 16 Apr 2014 15:06:17 -0400 Subject: [PATCH] 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 --- doc/src/sgml/config.sgml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) 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 - . This parameter can only + . 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. wal_level must be set to archive or higher to allow connections from standby servers.