|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.66 2010/05/02 02:10:32 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.67 2010/05/03 09:15:17 heikki Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability">
|
4 | 4 | <title>High Availability, Load Balancing, and Replication</title>
|
@@ -1156,7 +1156,7 @@ if (!triggered)
|
1156 | 1156 | so there will be a measurable delay between primary and standby. Running the
|
1157 | 1157 | same query nearly simultaneously on both primary and standby might therefore
|
1158 | 1158 | return differing results. We say that data on the standby is
|
1159 |
| - <literal>eventually consistent</literal> with the primary. |
| 1159 | + <firstterm>eventually consistent</firstterm> with the primary. |
1160 | 1160 | Queries executed on the standby will be correct with regard to the transactions
|
1161 | 1161 | that had been recovered at the start of the query, or start of first statement
|
1162 | 1162 | in the case of serializable transactions. In comparison with the primary,
|
|