From: martin.brown
Date: November 24 2008 11:30am
Subject: svn commit - mysqldoc@docsrva: r12633 - trunk/dynamic-docs/faq
List-Archive: http://lists.mysql.com/commits/59667
Message-Id: <200811241130.mAOBUhHl023954@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Author: mcbrown
Date: 2008-11-24 12:30:43 +0100 (Mon, 24 Nov 2008)
New Revision: 12633

Log:
Minor tweak to the FAQ for read-only backends


Modified:
   trunk/dynamic-docs/faq/mysql-proxy.xml


Modified: trunk/dynamic-docs/faq/mysql-proxy.xml
===================================================================
--- trunk/dynamic-docs/faq/mysql-proxy.xml	2008-11-24 11:21:15 UTC (rev 12632)
+++ trunk/dynamic-docs/faq/mysql-proxy.xml	2008-11-24 11:30:43 UTC (rev 12633)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 17; 1987 bytes

@@ -12,29 +12,24 @@
     <faqquestion>
 
       <para>
-        In load balancing, how can I separate reads from writes? Is a
-        backend-server a remote MySQL machine ? You would think so, but
-        from another post in this forum, it looks like the separation of
-        reads from writes has not been implemented yet, so I am not
-        clear as to the distinction between backend-servers and
-        read-only servers.
+        In load balancing, how can I separate reads from writes?
       </para>
-<programlisting>$ mysql-proxy \
---proxy-backend-addresses=10.0.1.2:3306 \
---proxy-backend-addresses=10.0.1.3:3306 &amp;</programlisting>
-      <para>
-        I don't see how this works for writes, as they have to go to the
-        master server.
-      </para>
 
     </faqquestion>
     <faqanswer>
 
       <para>
-        In version 0.6.0 there is no separation between read and writes
-        and it is up the user to make sure that only reads are sent to
-        the proxy. In the next releases we will add connection pooling
-        and read/write splitting to make this more useful. See also
+        There is no automatic separation of queries that perform reads
+        or writes to the different backend servers. However, you can
+        specify to <command>mysql-proxy</command> that one or more of
+        the 'backend' MyuSQL servers are read-only.
+      </para>
+<programlisting>$ mysql-proxy \
+--proxy-backend-addresses=10.0.1.2:3306 \
+--proxy-read-only-backend-addresses=10.0.1.3:3306 &amp;</programlisting>
+      <para>
+        In the next releases we will add connection pooling and
+        read/write splitting to make this more useful. See also
         <xref linkend="load-balancer"/>.
       </para>