From: Simon Riggs Date: Thu, 1 Oct 2009 15:18:07 +0000 (+0100) Subject: Document recommendation to set max_standby_delay = 0 during archive recovery. X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=83a5012806029330c519ac59bca74a289acd92ac;p=users%2Fsimon%2Fpostgres.git Document recommendation to set max_standby_delay = 0 during archive recovery. --- diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 15aea6209d..e29c3f8b98 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -2531,8 +2531,6 @@ LOG: database system is ready to accept read only connections - - max_standby_delay (string) @@ -2541,9 +2539,12 @@ LOG: database system is ready to accept read only connections queries that conflict with incoming data changes. Valid settings are -1, meaning wait forever, or a wait time of 0 or more seconds. If a conflict should occur the server will delay up to this - amount before it begins trying to resolve things less amicably, - described in . The - max_standby_delay may be set at server start + amount before it begins trying to resolve things less amicably, as + described in . Typically, + this parameter makes sense only during replication, so when + performing an archive recovery to recover from data loss a + parameter setting of 0 is recommended. + The max_standby_delay may be set at server start or it may be dynamically adjusted using pg_recovery_max_standby_delay described in .