database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-03 09:13:20 +03:00
Code Activity

Change "literal" tag to the more appropriate "firstterm", when describing

Browse Source 
what "eventually consistent" means.
This commit is contained in:
Heikki Linnakangas
2010-05-03 09:15:17 +00:00
parent f35951619c
commit 1b6c7b1c0b
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/high-availability.sgml
View File

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