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 dc589edc290ff4ab788ad89deaf7f767812d6029..17d9b6771482bb8a93c1614b78dbc43fa4e5a11d 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -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.
    </para>
   </listitem>
  </varlistentry>