<?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: Great work Innodb Team</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/</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: arun</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-767171</link>
		<dc:creator>arun</dc:creator>
		<pubDate>Wed, 16 Jun 2010 17:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-767171</guid>
		<description>that means whoever wants more stability should use the builtin version and whoever wants better performance, ease of upgrade should use Innodb plugin.</description>
		<content:encoded><![CDATA[<p>that means whoever wants more stability should use the builtin version and whoever wants better performance, ease of upgrade should use Innodb plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-695950</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Mon, 14 Dec 2009 15:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-695950</guid>
		<description>peter,

Yes, we&#039;re trying to improve the manual on that front. Thanks for noticing. :-)</description>
		<content:encoded><![CDATA[<p>peter,</p>
<p>Yes, we&#8217;re trying to improve the manual on that front. Thanks for noticing. <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-692233</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 08 Dec 2009 06:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-692233</guid>
		<description>Thanks for clarification Paul,

At least I see much more documentation about plugin in the MySQL documentation.</description>
		<content:encoded><![CDATA[<p>Thanks for clarification Paul,</p>
<p>At least I see much more documentation about plugin in the MySQL documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-688614</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Wed, 02 Dec 2009 03:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-688614</guid>
		<description>The MySQL manual does contain some information about InnoDB Plugin, but the Plugin manual is not merged into the MySQL manual.

InnoDB Plugin has indeed replaced the built-in InnoDB in MySQL 5.4, as of 5.4.2:
http://dev.mysql.com/doc/refman/5.4/en/news-5-4-2.html

However, there were a number of configuration default value changes in early 5.4.x releases, so skip directly to the most recent of these, 5.4.3:
http://dev.mysql.com/doc/refman/5.4/en/news-5-4-3.html

Upcoming MySQL 5.5.0 also has InnoDB Plugin as the built-in InnoDB, and it will have InnoDB Plugin 1.0.5. (5.4.x has 1.0.4).</description>
		<content:encoded><![CDATA[<p>The MySQL manual does contain some information about InnoDB Plugin, but the Plugin manual is not merged into the MySQL manual.</p>
<p>InnoDB Plugin has indeed replaced the built-in InnoDB in MySQL 5.4, as of 5.4.2:<br />
<a href="http://dev.mysql.com/doc/refman/5.4/en/news-5-4-2.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.4/en/news-5-4-2.html</a></p>
<p>However, there were a number of configuration default value changes in early 5.4.x releases, so skip directly to the most recent of these, 5.4.3:<br />
<a href="http://dev.mysql.com/doc/refman/5.4/en/news-5-4-3.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.4/en/news-5-4-3.html</a></p>
<p>Upcoming MySQL 5.5.0 also has InnoDB Plugin as the built-in InnoDB, and it will have InnoDB Plugin 1.0.5. (5.4.x has 1.0.4).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-688360</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 01 Dec 2009 17:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-688360</guid>
		<description>Kim,

MySQL 5.1 is &quot;Stable&quot; for quite a some time.  The Innodb Plugin is a a lot of new code and simply replacing build in Innodb with plugin can compromise stability and surely introduce number of behavior changes which are not intended to happen in &quot;Stable&quot; release.

So giving the Option of easily enabling Innodb plugin in MySQL 5.1 is a great solution which allows people who value stability the most to stay using BuiltIn Innodb and people who like Features and Performance to use Innodb Plugin.

I would expect if Innodb plugin goes to &quot;GA&quot; state soon and proves working well in 5.1 series we will see BuiltIn Innodb replaced by Plugin in next major MySQL release.</description>
		<content:encoded><![CDATA[<p>Kim,</p>
<p>MySQL 5.1 is &#8220;Stable&#8221; for quite a some time.  The Innodb Plugin is a a lot of new code and simply replacing build in Innodb with plugin can compromise stability and surely introduce number of behavior changes which are not intended to happen in &#8220;Stable&#8221; release.</p>
<p>So giving the Option of easily enabling Innodb plugin in MySQL 5.1 is a great solution which allows people who value stability the most to stay using BuiltIn Innodb and people who like Features and Performance to use Innodb Plugin.</p>
<p>I would expect if Innodb plugin goes to &#8220;GA&#8221; state soon and proves working well in 5.1 series we will see BuiltIn Innodb replaced by Plugin in next major MySQL release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-688182</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Tue, 01 Dec 2009 12:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-688182</guid>
		<description>It just seems innodb plugin has more feature / optimizations than the built-in innodb engine. 
Now mysql ships with both innodb and innodb plugin, should innodb be considered stable release of innodb while innodb plugin is 
newest version of innodb?

If they are both the same, I dont know why you would want to ship both. 

I can see the whole idea about pluggable engines, where you dont have to patch mysql source code to install an experimental 
or unofficial storage engine to mysql.</description>
		<content:encoded><![CDATA[<p>It just seems innodb plugin has more feature / optimizations than the built-in innodb engine.<br />
Now mysql ships with both innodb and innodb plugin, should innodb be considered stable release of innodb while innodb plugin is<br />
newest version of innodb?</p>
<p>If they are both the same, I dont know why you would want to ship both. </p>
<p>I can see the whole idea about pluggable engines, where you dont have to patch mysql source code to install an experimental<br />
or unofficial storage engine to mysql.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-688167</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Tue, 01 Dec 2009 10:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-688167</guid>
		<description>The pluging is not built inside the MySQL database, you can update it without recompiling/updating your whole setup. You can test multiple plugins with different version too, ensuring maximum compatibility and stability.</description>
		<content:encoded><![CDATA[<p>The pluging is not built inside the MySQL database, you can update it without recompiling/updating your whole setup. You can test multiple plugins with different version too, ensuring maximum compatibility and stability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim</title>
		<link>http://www.mysqlperformanceblog.com/2009/11/30/great-work-innodb-team/comment-page-1/#comment-688083</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Tue, 01 Dec 2009 08:16:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1793#comment-688083</guid>
		<description>What is the major difference between innodb and innodb plugin?, Thought they both were build from the same code base.</description>
		<content:encoded><![CDATA[<p>What is the major difference between innodb and innodb plugin?, Thought they both were build from the same code base.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

