|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.50 2010/02/2508:57:47 heikki Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.51 2010/02/2509:16:42 heikki Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
@@ -769,7 +769,7 @@ if (!triggered) |
769 | 769 | </para> |
770 | 770 |
|
771 | 771 | <para> |
772 | | - Streaming replication is asynchronous, so there isstilll a small delay |
| 772 | + Streaming replication is asynchronous, so there isstill a small delay |
773 | 773 | between committing a transaction in the primary and for the changes to |
774 | 774 | become visible in the standby. The delay is however much smaller than with |
775 | 775 | file-based log shipping, typically under one second assuming the standby |
|