Default --archive-timeout is 300 seconds

Artur Zakirov · Artur Zakirov · commit 62953a7f81e9 · 2017-03-24T14:24:29.000+03:00
diff --git 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
@@ -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_
