diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2015-11-23 09:13:44 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2015-11-23 09:13:44 -0500 |
| commit | f1824e55137fc7a30d5ac11aafdaba533fc1a6b5 (patch) | |
| tree | 452df8ca6da3b467d95f1200286cced6432067ef | |
| parent | 5f5e68b087e557fcddb7d28b096eead417623375 (diff) | |
| download | postgresql-f1824e55137fc7a30d5ac11aafdaba533fc1a6b5.tar.gz postgresql-f1824e55137fc7a30d5ac11aafdaba533fc1a6b5.zip | |
doc: Add more documentation about wal_retrieve_retry_interval
from Michael Paquier
| -rw-r--r-- | doc/src/sgml/config.sgml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 5a25b0308ed..c8445c51997 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3035,6 +3035,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> |