@@ -873,7 +873,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
873873 might indicate that the master server is under heavy load, while
874874 differences between <literal>sent_location</> and
875875 <function>pg_last_xlog_receive_location</> on the standby might indicate
876- network delay, or that thethe standby is under heavy load.
876+ network delay, or that the standby is under heavy load.
877877 </para>
878878 </sect3>
879879
@@ -952,7 +952,7 @@ synchronous_replication = on
952952 If the standby is the first matching standby, as specified in
953953 <varname>synchronous_standby_names</> on the primary, the reply
954954 messages from that standby will be used to wake users waiting for
955- confirmation the commit record has been received. These parameters
955+ confirmationthat the commit record has been received. These parameters
956956 allow the administrator to specify which standby servers should be
957957 synchronous standbys. Note that the configuration of synchronous
958958 replication is mainly on the master.
@@ -1002,10 +1002,10 @@ synchronous_replication = on
10021002
10031003 <para>
10041004 With synchronous replication options specified at the application level
1005- (on the primary) we can offersync rep for the most important changes,
1006- without slowing down the bulk of the total workload. Application level
1007- options are an important and practical tool for allowing the benefits of
1008- synchronous replication for high performance applications.
1005+ (on the primary) we can offersynchronous replication for the most
1006+ important changes, without slowing down the bulk of the total workload.
1007+ Application level options are an important and practical tool for allowing
1008+ the benefits of synchronous replication for high performance applications.
10091009 </para>
10101010
10111011 <para>
@@ -1029,7 +1029,7 @@ synchronous_replication = on
10291029 your last remaining sync standby. This can be achieved by naming multiple
10301030 potential synchronous standbys using <varname>synchronous_standby_names</>.
10311031 The first named standby will be used as the synchronous standby. Standbys
1032- listed after this willtakeover the role of synchronous standby if the
1032+ listed after this willtake over the role of synchronous standby if the
10331033 first one should fail.
10341034 </para>
10351035
@@ -1039,7 +1039,7 @@ synchronous_replication = on
10391039 the lag between standby and primary reaches zero for the first time
10401040 we move to real-time <literal>STREAMING</> state.
10411041 The catch-up duration may be long immediately after the standby has
1042- been created. If the standby isshutdown , then the catch-up period
1042+ been created. If the standby isshut down , then the catch-up period
10431043 will increase according to the length of time the standby has been down.
10441044 The standby is only able to become a synchronous standby
10451045 once it has reached <literal>STREAMING</> state.
@@ -1060,12 +1060,13 @@ synchronous_replication = on
10601060
10611061 <para>
10621062 If you really do lose your last standby server then you should disable
1063- <varname>synchronous_standby_names</> and restart the primary server.
1063+ <varname>synchronous_standby_names</> and reload the configuration file
1064+ on the primary server.
10641065 </para>
10651066
10661067 <para>
1067- If the primary is isolated from remaining standbysevers you should
1068- failover to the best candidate of those other remaining standby servers.
1068+ If the primary is isolated from remaining standbyservers you should
1069+ fail over to the best candidate of those other remaining standby servers.
10691070 </para>
10701071
10711072 <para>
@@ -1130,7 +1131,7 @@ synchronous_replication = on
11301131 and might stay down. To return to normal operation, a standby server
11311132 must be recreated,
11321133 either on the former primary system when it comes up, or on a third,
1133- possibly new, system. Once complete the primary and standby can be
1134+ possibly new, system. Once complete, the primary and standby can be
11341135 considered to have switched roles. Some people choose to use a third
11351136 server to provide backup for the new primary until the new standby
11361137 server is recreated,
@@ -1155,8 +1156,7 @@ synchronous_replication = on
11551156 <command>pg_ctl promote</> to fail over, <varname>trigger_file</> is
11561157 not required. If you're setting up the reporting servers that are
11571158 only used to offload read-only queries from the primary, not for high
1158- availability purposes, you don't need to exit recovery in the standby
1159- and promote it to a master.
1159+ availability purposes, you don't need to promote it.
11601160 </para>
11611161 </sect1>
11621162