|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.67 2010/05/03 09:15:17 heikki Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.68 2010/05/13 14:16:41 mha Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability">
|
4 | 4 | <title>High Availability, Load Balancing, and Replication</title>
|
@@ -201,7 +201,7 @@ protocol to make nodes agree on a serializable transactional order.
|
201 | 201 | must query such values from a single server and then use those
|
202 | 202 | values in write queries. Another option is to use this replication
|
203 | 203 | option with a traditional master-slave setup, i.e. data modification
|
204 |
| - queries are sent only to the master and arepropogated to the |
| 204 | + queries are sent only to the master and arepropagated to the |
205 | 205 | slaves via master-slave replication, not by the replication
|
206 | 206 | middleware. Care must also be taken that all
|
207 | 207 | transactions either commit or abort on all servers, perhaps
|
@@ -1559,7 +1559,7 @@ if (!triggered)
|
1559 | 1559 | node itself. And you are still getting the benefit of off-loading the
|
1560 | 1560 | execution onto the standby. <varname>max_standby_delay</> should
|
1561 | 1561 | not be used in this case because delayed WAL files might already
|
1562 |
| - contain entries that invalidate the currentshapshot. |
| 1562 | + contain entries that invalidate the currentsnapshot. |
1563 | 1563 | </para>
|
1564 | 1564 |
|
1565 | 1565 | <para>
|
@@ -1823,7 +1823,7 @@ LOG: database system is ready to accept read only connections
|
1823 | 1823 | </para>
|
1824 | 1824 |
|
1825 | 1825 | <para>
|
1826 |
| - Thestatististics collector is active during recovery. All scans, reads, blocks, |
| 1826 | + Thestatistics collector is active during recovery. All scans, reads, blocks, |
1827 | 1827 | index usage, etc., will be recorded normally on the standby. Replayed
|
1828 | 1828 | actions will not duplicate their effects on primary, so replaying an
|
1829 | 1829 | insert will not increment the Inserts column of pg_stat_user_tables.
|
|