<?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: Mirrored Binlogs</title>
	<atom:link href="http://ourdelta.org/docs/mirror-binlog/feed" rel="self" type="application/rss+xml" />
	<link>http://ourdelta.org</link>
	<description>Enhanced, packaged convenience for MySQL and MariaDB</description>
	<lastBuildDate>Thu, 30 Jun 2011 03:40:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: arjen</title>
		<link>http://ourdelta.org/docs/mirror-binlog#comment-124</link>
		<dc:creator>arjen</dc:creator>
		<pubDate>Wed, 17 Dec 2008 10:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://ourdelta.org/?page_id=165#comment-124</guid>
		<description>@Michael: The MySQL community has not been exactly quiet. Heck, I was even vocal when I was at MySQL AB. Anyway, to get a good insight in the regular goings&#039; on you could follow planetmysql.org and you will quickly notice that the community is anything but silent on saying what they think, and acting on it.</description>
		<content:encoded><![CDATA[<p>@Michael: The MySQL community has not been exactly quiet. Heck, I was even vocal when I was at MySQL AB. Anyway, to get a good insight in the regular goings&#8217; on you could follow planetmysql.org and you will quickly notice that the community is anything but silent on saying what they think, and acting on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Renner</title>
		<link>http://ourdelta.org/docs/mirror-binlog#comment-123</link>
		<dc:creator>Michael Renner</dc:creator>
		<pubDate>Wed, 17 Dec 2008 09:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://ourdelta.org/?page_id=165#comment-123</guid>
		<description>Arjen,

thanks for your reply. By no means I want to criticize the work you are doing here, it was long overdue and I see it as a chance for the project to regain credibility. It is a major shame though, that this work wasn&#039;t started by MySQL Management either in the AB or now at Sun.

What I&#039;m missing is a somewhat critical and/or challenging stance to the product you use daily.

I&#039;m a heavy Linux, Debian and PostgreSQL user (and contributor) and have used a fair share of different Open Source Software in the infrastructure I managed. I am never short of criticism for any of the tools I use and even contributed to, because I know that as great as they might be in a specific area, there are enough use cases where they are suboptimal or plain and outright fail.

And this is one of the things I miss from the MySQL Community at large (generalizing here); the only critical voice I heard so far was the one from Monty Widenius, who held nice presentations about the status quo a year or two ago, and now started to be more public about his insights.

To summarize:

When the fish stinks, it usually means it&#039;s (grown) bad. And if a whole lot of fish in a given area stink, it usually hints on systemic/architectural problems and not isolated bugs or user problems.

best regards,
Michael</description>
		<content:encoded><![CDATA[<p>Arjen,</p>
<p>thanks for your reply. By no means I want to criticize the work you are doing here, it was long overdue and I see it as a chance for the project to regain credibility. It is a major shame though, that this work wasn&#8217;t started by MySQL Management either in the AB or now at Sun.</p>
<p>What I&#8217;m missing is a somewhat critical and/or challenging stance to the product you use daily.</p>
<p>I&#8217;m a heavy Linux, Debian and PostgreSQL user (and contributor) and have used a fair share of different Open Source Software in the infrastructure I managed. I am never short of criticism for any of the tools I use and even contributed to, because I know that as great as they might be in a specific area, there are enough use cases where they are suboptimal or plain and outright fail.</p>
<p>And this is one of the things I miss from the MySQL Community at large (generalizing here); the only critical voice I heard so far was the one from Monty Widenius, who held nice presentations about the status quo a year or two ago, and now started to be more public about his insights.</p>
<p>To summarize:</p>
<p>When the fish stinks, it usually means it&#8217;s (grown) bad. And if a whole lot of fish in a given area stink, it usually hints on systemic/architectural problems and not isolated bugs or user problems.</p>
<p>best regards,<br />
Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: arjen</title>
		<link>http://ourdelta.org/docs/mirror-binlog#comment-118</link>
		<dc:creator>arjen</dc:creator>
		<pubDate>Wed, 17 Dec 2008 00:54:35 +0000</pubDate>
		<guid isPermaLink="false">http://ourdelta.org/?page_id=165#comment-118</guid>
		<description>@Michael: yep those are Mark Callaghan&#039;s words. Of course replication also has its issues but it works really well in a huge number of places. Obviously skill and monitoring come into it, too.

MySQL is the most widely used and publicly documented database product, at least in the OSS and mainstream deployment space; so obviously there&#039;s more info out there about things that can cause hassles, and also there&#039;ll be more people experiencing those hassles.
Doesn&#039;t mean it&#039;s like that for everybody. But it&#039;s good to hear the good as well as the bad, then people can make more educated decisions.

What I&#039;ve found doing Open Query training and support is that many replication issues simply arise from misconceptions about how it works, being unfamiliar with particular aspects and features and trying to abuse other features to do something inappropriate, and so on. Like any tool, knowing how to handle it helps a great deal and often prevents trouble.</description>
		<content:encoded><![CDATA[<p>@Michael: yep those are Mark Callaghan&#8217;s words. Of course replication also has its issues but it works really well in a huge number of places. Obviously skill and monitoring come into it, too.</p>
<p>MySQL is the most widely used and publicly documented database product, at least in the OSS and mainstream deployment space; so obviously there&#8217;s more info out there about things that can cause hassles, and also there&#8217;ll be more people experiencing those hassles.<br />
Doesn&#8217;t mean it&#8217;s like that for everybody. But it&#8217;s good to hear the good as well as the bad, then people can make more educated decisions.</p>
<p>What I&#8217;ve found doing Open Query training and support is that many replication issues simply arise from misconceptions about how it works, being unfamiliar with particular aspects and features and trying to abuse other features to do something inappropriate, and so on. Like any tool, knowing how to handle it helps a great deal and often prevents trouble.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Renner</title>
		<link>http://ourdelta.org/docs/mirror-binlog#comment-117</link>
		<dc:creator>Michael Renner</dc:creator>
		<pubDate>Tue, 16 Dec 2008 23:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://ourdelta.org/?page_id=165#comment-117</guid>
		<description>&quot;MySQL replication is great. It is efficient, stable and easy to use.&quot;

I am at loss of words.

Heading for the tip:

http://bugs.mysql.com/search.php?search_for=replication&amp;status=All&amp;severity=&amp;limit=10&amp;order_by=id&amp;cmd=display&amp;direction=DESC&amp;bug_type=&amp;os=0&amp;phpver=&amp;bug_age=0

http://dev.mysql.com/doc/refman/5.1/en/replication-features.html (the &quot;Features &amp; Issues&quot; is a rather kinky way to put it)

And there is probably much much more below the surface. But I guess if the Stockholm&#039;s is advanced enough, you can&#039;t tell the difference anymore.</description>
		<content:encoded><![CDATA[<p>&#8220;MySQL replication is great. It is efficient, stable and easy to use.&#8221;</p>
<p>I am at loss of words.</p>
<p>Heading for the tip:</p>
<p><a href="http://bugs.mysql.com/search.php?search_for=replication&#038;status=All&#038;severity=&#038;limit=10&#038;order_by=id&#038;cmd=display&#038;direction=DESC&#038;bug_type=&#038;os=0&#038;phpver=&#038;bug_age=0" rel="nofollow">http://bugs.mysql.com/search.php?search_for=replication&#038;status=All&#038;severity=&#038;limit=10&#038;order_by=id&#038;cmd=display&#038;direction=DESC&#038;bug_type=&#038;os=0&#038;phpver=&#038;bug_age=0</a></p>
<p><a href="http://dev.mysql.com/doc/refman/5.1/en/replication-features.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/replication-features.html</a> (the &#8220;Features &amp; Issues&#8221; is a rather kinky way to put it)</p>
<p>And there is probably much much more below the surface. But I guess if the Stockholm&#8217;s is advanced enough, you can&#8217;t tell the difference anymore.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

