From 2ef7a985fb9077aabeb480a23732c4d6ddb89ce5 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Mon, 23 Nov 2015 09:13:44 -0500
Subject: [PATCH] doc: Add more documentation about wal_retrieve_retry_interval
from Michael Paquier
---
doc/src/sgml/config.sgml | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 6e14851f696..392eb700b0c 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3054,6 +3054,17 @@ include_dir 'conf.d'
<filename>postgresql.conf</> file or on the server command line.
The default value is 5 seconds. Units are milliseconds if not specified.
</para>
+ <para>
+ This parameter is useful in configurations where a node in recovery
+ needs to control the amount of time to wait for new WAL data to be
+ available. For example, in archive recovery, it is possible to
+ make the recovery more responsive in the detection of a new WAL
+ log file by reducing the value of this parameter. On a system with
+ low WAL activity, increasing it reduces the amount of requests necessary
+ to access WAL archives, something useful for example in cloud
+ environments where the amount of times an infrastructure is accessed
+ is taken into account.
+ </para>
</listitem>
</varlistentry>
--
GitLab