From 561485709673f4bc05240e891dd9056bdedbbcbc Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Tue, 3 May 2011 11:34:27 -0300
Subject: [PATCH] Improve description of read/write traffic scalability
Greg Smith, after a suggestion of James Bruce
---
doc/src/sgml/high-availability.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 5972a45555f..5bb45fea7e9 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -188,9 +188,10 @@ protocol to make nodes agree on a serializable transactional order.
<para>
With statement-based replication middleware, a program intercepts
every SQL query and sends it to one or all servers. Each server
- operates independently. Read-write queries are sent to all servers,
- while read-only queries can be sent to just one server, allowing
- the read workload to be distributed.
+ operates independently. Read-write queries must be sent to all servers,
+ so that every server receives any changes. But read-only queries can be
+ sent to just one server, allowing the read workload to be distributed
+ among them.
</para>
<para>
--
GitLab