Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 7ab9305

Browse files
committed
Document max_standby_delay=-1 option, now that it's allowed again.
1 parent 4ec700a commit 7ab9305

File tree

2 files changed

+8
-6
lines changed

2 files changed

+8
-6
lines changed

doc/src/sgml/config.sgml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.254 2010/02/25 19:20:38 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.255 2010/02/27 09:29:20 heikki Exp $ -->
22

33
<chapter Id="runtime-config">
44
<title>Server Configuration</title>
@@ -1868,9 +1868,8 @@ archive_command = 'copy "%p" "C:\\server\\archivedir\\%f"' # Windows
18681868
described in <xref linkend="hot-standby-conflict">. Typically,
18691869
this parameter makes sense only during replication, so when
18701870
performing an archive recovery to recover from data loss a very high
1871-
parameter setting is recommended. The default is 30 seconds.
1872-
There is no wait-forever setting because of the potential for deadlock
1873-
which that setting would introduce.
1871+
parameter setting or -1 which means wait forever is recommended.
1872+
The default is 30 seconds.
18741873
This parameter can only be set in the <filename>postgresql.conf</>
18751874
file or on the server command line.
18761875
</para>

doc/src/sgml/high-availability.sgml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.51 2010/02/25 09:16:42 heikki Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.52 2010/02/27 09:29:20 heikki Exp $ -->
22

33
<chapter id="high-availability">
44
<title>High Availability, Load Balancing, and Replication</title>
@@ -1521,7 +1521,10 @@ LOG: database system is ready to accept read only connections
15211521
<varname>max_standby_delay</> or even set it to zero, though that is a
15221522
very aggressive setting. If the standby server is tasked as an additional
15231523
server for decision support queries then it might be acceptable to set this
1524-
to a value of many hours (in seconds).
1524+
to a value of many hours (in seconds). It is also possible to set
1525+
<varname>max_standby_delay</> to -1 which means wait forever for queries
1526+
to complete, if there are conflicts; this will be useful when performing
1527+
an archive recovery from a backup.
15251528
</para>
15261529

15271530
<para>

0 commit comments

Comments
 (0)