|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.2 2006/11/2015:07:13 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.3 2006/11/2021:26:22 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability">
|
4 | 4 | <title>High Availability and Load Balancing</title>
|
|
98 | 98 | disk array fails or becomes corrupt, the primary and standby
|
99 | 99 | servers are both nonfunctional. Another issue is that the
|
100 | 100 | standby server should never access the shared storage while
|
101 |
| - the primary server is running. |
| 101 | + the primary server is running. It is also possible to use |
| 102 | + some type of file system mirroring to keep the standby server |
| 103 | + current, but the mirroring must be done in a way that the |
| 104 | + standby server has a consistent copy of the file system. |
102 | 105 | </para>
|
103 | 106 | </listitem>
|
104 | 107 | </varlistentry>
|
|