From 62953a7f81e92f2399dd711074df5857a1a6cfaa Mon Sep 17 00:00:00 2001 From: Artur Zakirov Date: Fri, 24 Mar 2017 14:24:29 +0300 Subject: [PATCH] Default --archive-timeout is 300 seconds --- backup.c | 2 +- doc/pg_probackup.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/backup.c b/backup.c index d35e2f7d..ce789c47 100644 --- a/backup.c +++ b/backup.c @@ -31,7 +31,7 @@ static int server_version = 0; /* Wait timeout for WAL segment archiving */ -uint32 archive_timeout = 0; +uint32 archive_timeout = 300; static bool in_backup = false; /* TODO: more robust logic */ static int standby_message_timeout = 10 * 1000; /* 10 sec = default */ diff --git a/doc/pg_probackup.md b/doc/pg_probackup.md index 35729217..4567620b 100644 --- a/doc/pg_probackup.md +++ b/doc/pg_probackup.md @@ -412,7 +412,7 @@ Makes an autonomous backup that includes all necessary WAL files, by streaming t --archive-timeout -Wait timeout for WAL segment archiving. `pg_probackup` waits after `pg_start_backup()` and `pg_stop_backup()` executing when WAL segments with necessary LSN will be archived. For backup from master WAL segment will be archived fast, because master instance switch WAL segment during backup. For backup from standby `pg_probackup` will wait a long time, because standby instance cannot switch WAL segment. By default timeout is infinite. +Wait timeout for WAL segment archiving. `pg_probackup` waits after `pg_start_backup()` and `pg_stop_backup()` executing when WAL segments with necessary LSN will be archived. For backup from master WAL segment will be archived fast, because master instance switch WAL segment during backup. For backup from standby `pg_probackup` will wait a long time, because standby instance cannot switch WAL segment. By default timeout is 300 seconds. -S _slot\_name_ --slot=_slot\_name_