aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2006-11-20 21:26:22 +0000
committerBruce Momjian <bruce@momjian.us>2006-11-20 21:26:22 +0000
commitb8c01d9dac25e28775a9bdb478443b9fc5359ce7 (patch)
tree74800c01565881e2e382c15e4e44069bae9c8690
parentfb2619859c4202246ddfc114527f410d14ea6d8e (diff)
downloadpostgresql-b8c01d9dac25e28775a9bdb478443b9fc5359ce7.tar.gz
postgresql-b8c01d9dac25e28775a9bdb478443b9fc5359ce7.zip
Add mention that Shared Disk Failover can use file system mirroring of
the mirroring is consistent.
-rw-r--r--doc/src/sgml/high-availability.sgml7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 69d5ebc84d2..03d266dc865 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.2 2006/11/20 15:07:13 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.3 2006/11/20 21:26:22 momjian Exp $ -->
<chapter id="high-availability">
<title>High Availability and Load Balancing</title>
@@ -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>