Commit 6e8e7cc5 authored by Simon Riggs's avatar Simon Riggs

Update docs to say you need fsync to make sync rep work fast.

parent 8df08c84
...@@ -947,7 +947,7 @@ synchronous_replication = on ...@@ -947,7 +947,7 @@ synchronous_replication = on
<para> <para>
After a commit record has been written to disk on the primary the After a commit record has been written to disk on the primary the
WAL record is then sent to the standby. The standby sends reply WAL record is then sent to the standby. The standby sends reply
messages each time a new batch of WAL data is received, unless messages each time a new batch of WAL data is written to disk, unless
<varname>wal_receiver_status_interval</> is set to zero on the standby. <varname>wal_receiver_status_interval</> is set to zero on the standby.
If the standby is the first matching standby, as specified in If the standby is the first matching standby, as specified in
<varname>synchronous_standby_names</> on the primary, the reply <varname>synchronous_standby_names</> on the primary, the reply
...@@ -1013,6 +1013,12 @@ synchronous_replication = on ...@@ -1013,6 +1013,12 @@ synchronous_replication = on
the rate of generation of WAL data. the rate of generation of WAL data.
</para> </para>
<para>
Replies are only sent when WAL is written to disk, so setting
<varname>fsync</> to <literal>off</> on the standby will significantly
reduce performance of synchronous replication and should be avoided.
</para>
</sect3> </sect3>
<sect3 id="synchronous-replication-ha"> <sect3 id="synchronous-replication-ha">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment