database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Clarify that streaming replication can be both async and sync

Browse Source 
Josh Kupershmidt
This commit is contained in:
Magnus Hagander 2013-01-20 16:10:12 +01:00
parent 26d905a12d
commit 0a2da5282a
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/high-availability.sgml
View File

@ -738,13 +738,14 @@ archive_cleanup_command = 'pg_archivecleanup /path/to/archive %r'
</para> </para>
<para> <para>
Streaming replication is asynchronous, so there is still a small delay Streaming replication is asynchronous by default
between committing a transaction in the primary and for the changes to (see <xref linkend="synchronous-replication">), in which case there is
become visible in the standby. The delay is however much smaller than with a small delay between committing a transaction in the primary and the
file-based log shipping, typically under one second assuming the standby changes becoming visible in the standby. This delay is however much
is powerful enough to keep up with the load. With streaming replication, smaller than with file-based log shipping, typically under one second
<varname>archive_timeout</> is not required to reduce the data loss assuming the standby is powerful enough to keep up with the load. With
window. streaming replication, <varname>archive_timeout</> is not required to
reduce the data loss window.
</para> </para>
<para> <para>