|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.7 2006/11/2121:37:33 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.8 2006/11/2122:48:33 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability and Load Balancing</title> |
@@ -197,8 +197,8 @@ protocol to make nodes agree on a serializable transactional order. |
197 | 197 | is best for mostly read workloads, though its big advantage |
198 | 198 | is that any server can accept write requests — there is |
199 | 199 | no need to partition workloads between master and slave servers, |
200 | | - and because the changes are sent from one server to another, |
201 | | - there isnot a problem with non-deterministic functions like |
| 200 | + and because thedatachanges are sent from one server to another, |
| 201 | + there isno problem with non-deterministic functions like |
202 | 202 | <function>random()</>. |
203 | 203 | </para> |
204 | 204 |
|
|