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

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема pgsql: Add GUC to control the time to wait before retrieving WAL after
Дата
Msg-id E1YPrcK-0002AB-JT@gemulon.postgresql.org
обсуждение исходный текст
Список 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(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: pgsql: Fix potential deadlock with libpq non-blocking mode.
Следующее
От: Andres Freund
Дата:
Сообщение: pgsql: Guard against spurious signals in LockBufferForCleanup.