database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Add GUC to control the time to wait before retrieving WAL after failed attempt.

Browse Source 
Previously when the standby server failed to retrieve WAL files from any sources
(i.e., streaming replication, local pg_xlog directory or WAL archive), it always
waited for five seconds (hard-coded) before the next attempt. For example,
this is problematic in warm-standby because restore_command can fail
every five seconds even while new WAL file is expected to be unavailable for
a long time and flood the log files with its error messages.

This commit adds new parameter, wal_retrieve_retry_interval, to control that
wait time.

Alexey Vasiliev and Michael Paquier, reviewed by Andres Freund and me.
This commit is contained in:
Fujii Masao
2015-02-23 20:55:17 +09:00
parent 2a3f6e368b
commit 5d2b45e3f7
5 changed files with 57 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/src/sgml/config.sgml
View File

@ -2985,6 +2985,24 @@ include_dir 'conf.d'
</listitem>
</varlistentry>
<varlistentry id="guc-wal-retrieve-retry-interval" xreflabel="wal_retrieve_retry_interval">
<term><varname>wal_retrieve_retry_interval</varname> (<type>integer</type>)
<indexterm>
<primary><varname>wal_retrieve_retry_interval</> configuration parameter</primary>
</indexterm>
</term>
<listitem>
<para>
Specify how long the standby server should wait when WAL data is not
available from any sources (streaming replication,
local <filename>pg_xlog</> or WAL archive) before retrying to
retrieve WAL data. This parameter can only be set in the
<filename>postgresql.conf</> file or on the server command line.
The default value is 5 seconds. Units are milliseconds if not specified.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>