s2> fails. s4> is an asynchronous standby since
its name is not in the list.
+ The synchronous states of standby servers can be viewed using
+ the pg_stat_replication view.
+
will increase according to the length of time the standby has been down.
The standby is only able to become a synchronous standby
once it has reached streaming> state.
+ This state can be viewed using
+ the pg_stat_replication view.
|
state>
text>
- Current WAL sender state
+ Current WAL sender state.
+ Possible values are:
+
+
+ startup>: This WAL sender is starting up.
+
+
+
+ catchup>: This WAL sender's connected standby is
+ catching up with the primary.
+
+
+
+ streaming>: This WAL sender is streaming changes
+ after its connected standby server has caught up with the primary.
+
+
+
+ backup>: This WAL sender is sending a backup.
+
+
+
+
|
sent_location>
|
sync_state>
text>
- Synchronous state of this standby server
+ Synchronous state of this standby server.
+ Possible values are:
+
+
+ async>: This standby server is asynchronous.
+
+
+
+ potential>: This standby server is now asynchronous,
+ but can potentially become synchronous if one of current
+ synchronous ones fails.
+
+
+
+ sync>: This standby server is synchronous.
+
+
+
+