<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Making MySQL Replication Parallel</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/01/30/making-mysql-replication-parallel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/01/30/making-mysql-replication-parallel/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jon</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/30/making-mysql-replication-parallel/comment-page-1/#comment-750202</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 19 Apr 2010 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/30/making-mysql-replication-parallel/#comment-750202</guid>
		<description>This is a narrow use case, but I could see it being useful.  Let replication be single threaded per schema.  Add the ability to configure MySQL to not permit multi schema transactions and then allow multiple replication threads, each configured to deal with transactions for a single schema.</description>
		<content:encoded><![CDATA[<p>This is a narrow use case, but I could see it being useful.  Let replication be single threaded per schema.  Add the ability to configure MySQL to not permit multi schema transactions and then allow multiple replication threads, each configured to deal with transactions for a single schema.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

