aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2013-01-20 16:10:12 +0100
committerMagnus Hagander <magnus@hagander.net>2013-01-20 16:11:19 +0100
commit04edfb10a60cad0a1efa5a0c0bef9b88a2fd5eba (patch)
tree8938a6a2f8e761e7b5784859bd63f425dbd4fa01
parent8c0b2afa38bbdf016c876e74371feee3c00b9f09 (diff)
downloadpostgresql-04edfb10a60cad0a1efa5a0c0bef9b88a2fd5eba.tar.gz
postgresql-04edfb10a60cad0a1efa5a0c0bef9b88a2fd5eba.zip
Clarify that streaming replication can be both async and sync
Josh Kupershmidt
-rw-r--r--doc/src/sgml/high-availability.sgml15
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index f811d297d8b..605749d70c4 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -738,13 +738,14 @@ archive_cleanup_command = 'pg_archivecleanup /path/to/archive %r'
</para>
<para>
- Streaming replication is asynchronous, so there is still a small delay
- between committing a transaction in the primary and for the changes to
- become visible in the standby. The delay is however much smaller than with
- file-based log shipping, typically under one second assuming the standby
- is powerful enough to keep up with the load. With streaming replication,
- <varname>archive_timeout</> is not required to reduce the data loss
- window.
+ Streaming replication is asynchronous by default
+ (see <xref linkend="synchronous-replication">), in which case there is
+ a small delay between committing a transaction in the primary and the
+ changes becoming visible in the standby. This delay is however much
+ smaller than with file-based log shipping, typically under one second
+ assuming the standby is powerful enough to keep up with the load. With
+ streaming replication, <varname>archive_timeout</> is not required to
+ reduce the data loss window.
</para>
<para>