pgsql: Add GUC to control the time to wait before retrieving WAL after

From: Fujii Masao <fujii(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add GUC to control the time to wait before retrieving WAL after
Date: 2015-02-23 11:56:04
Message-ID: E1YPrcK-0002AB-JT@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

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.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5d2b45e3f78a85639f30431181c06d4c3221c5a1

Modified Files
--------------
doc/src/sgml/config.sgml | 18 ++++++++++++
src/backend/access/transam/xlog.c | 37 ++++++++++++++++---------
src/backend/utils/misc/guc.c | 12 ++++++++
src/backend/utils/misc/postgresql.conf.sample | 2 ++
src/include/access/xlog.h | 1 +
5 files changed, 57 insertions(+), 13 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2015-02-23 15:25:54 pgsql: Guard against spurious signals in LockBufferForCleanup.
Previous Message Heikki Linnakangas 2015-02-23 11:38:57 pgsql: Fix potential deadlock with libpq non-blocking mode.