summaryrefslogtreecommitdiff
path: root/doc/src/sgml/release-9.1.sgml
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-10-11 17:39:52 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-10-11 17:48:08 +0300
commit6f60fdd7015b032bf49273c99f80913d57eac284 (patch)
treeef9a5602c01617665815503a45dc1ea3b379e757 /doc/src/sgml/release-9.1.sgml
parent8521d131941be5a177270bc428fa8e684cd645b5 (diff)
downloadpostgresql-6f60fdd7015b032bf49273c99f80913d57eac284.tar.gz
Improve replication connection timeouts.
Rename replication_timeout to wal_sender_timeout, and add a new setting called wal_receiver_timeout that does the same at the walreceiver side. There was previously no timeout in walreceiver, so if the network went down, for example, the walreceiver could take a long time to notice that the connection was lost. Now with the two settings, both sides of a replication connection will detect a broken connection similarly. It is no longer necessary to manually set wal_receiver_status_interval to a value smaller than the timeout. Both wal sender and receiver now automatically send a "ping" message if more than 1/2 of the configured timeout has elapsed, and it hasn't received any messages from the other end. Amit Kapila, heavily edited by me.
Diffstat (limited to 'doc/src/sgml/release-9.1.sgml')
-rw-r--r--doc/src/sgml/release-9.1.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml
index 6bc1c8c90e..5fbdd7a195 100644
--- a/doc/src/sgml/release-9.1.sgml
+++ b/doc/src/sgml/release-9.1.sgml
@@ -3322,7 +3322,7 @@
<listitem>
<para>
Add
- <link linkend="guc-replication-timeout"><varname>replication_timeout</></link>
+ <varname>replication_timeout</>
setting (Fujii Masao, Heikki Linnakangas)
</para>