|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.11 2006/11/1708:46:53 meskes Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.12 2006/11/1709:00:03 neilc Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="failover"> |
4 | 4 | <title>Failover, Replication, Load Balancing, and Clustering Options</title> |
|
121 | 121 |
|
122 | 122 | <para> |
123 | 123 | A master/slave replication setup sends all data modification |
124 | | - queries to the master server. The master serverasynchonously |
| 124 | + queries to the master server. The master serverasynchronously |
125 | 125 | sends data changes to the slave server. The slave can answer |
126 | 126 | read-only queries while the master server is running. The |
127 | 127 | slave server is ideal for data warehouse queries. |
|
