Add mention that Shared Disk Failover can use file system mirroring of

the mirroring is consistent.

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 69d5ebc84d2cc543735826325f8bab3fe5a4f483..03d266dc8657214d6121007cee2b87b8cf617c05 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  High Availability and Load Balancing
@@ -98,7 +98,10 @@
     disk array fails or becomes corrupt, the primary and standby
     servers are both nonfunctional.  Another issue is that the
     standby server should never access the shared storage while
-    the primary server is running.
+    the primary server is running.  It is also possible to use
+    some type of file system mirroring to keep the standby server
+    current, but the mirroring must be done in a way that the
+    standby server has a consistent copy of the file system.