Skip to content

Commit 1b6c7b1

Browse files
committed
Change "literal" tag to the more appropriate "firstterm", when describing
what "eventually consistent" means.
1 parent f359516 commit 1b6c7b1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/high-availability.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
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 $ -->
22

33
<chapter id="high-availability">
44
<title>High Availability, Load Balancing, and Replication</title>
@@ -1156,7 +1156,7 @@ if (!triggered)
11561156
so there will be a measurable delay between primary and standby. Running the
11571157
same query nearly simultaneously on both primary and standby might therefore
11581158
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.
11601160
Queries executed on the standby will be correct with regard to the transactions
11611161
that had been recovered at the start of the query, or start of first statement
11621162
in the case of serializable transactions. In comparison with the primary,

0 commit comments

Comments
 (0)