<?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"
	>
<channel>
	<title>Comments on: SHOW PROFILES in MySQL 5.1</title>
	<atom:link href="http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/</link>
	<description>Wizardry and community</description>
	<pubDate>Wed, 25 Nov 2009 00:32:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Jeremy Cole</title>
		<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-7</link>
		<dc:creator>Jeremy Cole</dc:creator>
		<pubDate>Thu, 15 Nov 2007 19:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-7</guid>
		<description>Hi Giuseppe,

No offense was taken.  Actually, I just looked at the code you provided as 5.1.23.  There are basically no changes from 5.0... The only diffs are because of changes in 5.1, and a new macro COMMUNITY_SERVER.  What do you mean 80% of the code has changed?

The thd-&#62;proc_info to thd_proc_info() macro change is obvious, and yes this accounts for actually closer to 99% of the patch size by line, but it is for the most part a trivial search and replace.  The macro should have been implemented in 5.1 a long long time ago actually.

I would not say that the implementation has "evolved" at all...

Regards,

Jeremy</description>
		<content:encoded><![CDATA[<p>Hi Giuseppe,</p>
<p>No offense was taken.  Actually, I just looked at the code you provided as 5.1.23.  There are basically no changes from 5.0&#8230; The only diffs are because of changes in 5.1, and a new macro COMMUNITY_SERVER.  What do you mean 80% of the code has changed?</p>
<p>The thd-&gt;proc_info to thd_proc_info() macro change is obvious, and yes this accounts for actually closer to 99% of the patch size by line, but it is for the most part a trivial search and replace.  The macro should have been implemented in 5.1 a long long time ago actually.</p>
<p>I would not say that the implementation has &#8220;evolved&#8221; at all&#8230;</p>
<p>Regards,</p>
<p>Jeremy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmax</title>
		<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-5</link>
		<dc:creator>gmax</dc:creator>
		<pubDate>Thu, 15 Nov 2007 09:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-5</guid>
		<description>Hi Jeremy,
No disrespect intended for your coding skills.
I was just pointing out that SHOW PROFILES implementation has evolved.
The feature is quite complex and it has impact on mostly everything. It was almost inevitable that, as the code base changed since its original proposal, the patch needed adjustments.

That said, I hope you will help out with the testing, perhaps by making some more binaries available from dorsalsource.org.

Cheers

Giuseppe</description>
		<content:encoded><![CDATA[<p>Hi Jeremy,<br />
No disrespect intended for your coding skills.<br />
I was just pointing out that SHOW PROFILES implementation has evolved.<br />
The feature is quite complex and it has impact on mostly everything. It was almost inevitable that, as the code base changed since its original proposal, the patch needed adjustments.</p>
<p>That said, I hope you will help out with the testing, perhaps by making some more binaries available from dorsalsource.org.</p>
<p>Cheers</p>
<p>Giuseppe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gmax</title>
		<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-4</link>
		<dc:creator>gmax</dc:creator>
		<pubDate>Thu, 15 Nov 2007 07:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-4</guid>
		<description>Kevin, 
yes, ported means that it will make it to the official binaries and into bitkeeper. But note that I said. "if approved". 
Currently, the code is under review.
Giuseppe</description>
		<content:encoded><![CDATA[<p>Kevin,<br />
yes, ported means that it will make it to the official binaries and into bitkeeper. But note that I said. &#8220;if approved&#8221;.<br />
Currently, the code is under review.<br />
Giuseppe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Burton</title>
		<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-3</link>
		<dc:creator>Kevin Burton</dc:creator>
		<pubDate>Thu, 15 Nov 2007 06:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-3</guid>
		<description>Ported meaning it's going to make it into official binaries and into bitkeeper?

Kevin</description>
		<content:encoded><![CDATA[<p>Ported meaning it&#8217;s going to make it into official binaries and into bitkeeper?</p>
<p>Kevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Cole</title>
		<link>http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-2</link>
		<dc:creator>Jeremy Cole</dc:creator>
		<pubDate>Thu, 15 Nov 2007 00:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/gmax/2007/11/14/show-profiles-in-mysql-51/#comment-2</guid>
		<description>Hi Giuseppe,

To be fair, not much of my original code was left in what went into 5.0, either.  Chad reworked the patch, as the original one I provided was more of a proof of concept, and MySQL couldn't get their act together enough for me to finish it up myself.  I only originally asked for the macro patch to be subsumed so that I could work on the real features without going insane.  Instead, MySQL took the entire patchset in its half baked state and Chad fixed it up.

Regards,

Jeremy</description>
		<content:encoded><![CDATA[<p>Hi Giuseppe,</p>
<p>To be fair, not much of my original code was left in what went into 5.0, either.  Chad reworked the patch, as the original one I provided was more of a proof of concept, and MySQL couldn&#8217;t get their act together enough for me to finish it up myself.  I only originally asked for the macro patch to be subsumed so that I could work on the real features without going insane.  Instead, MySQL took the entire patchset in its half baked state and Chad fixed it up.</p>
<p>Regards,</p>
<p>Jeremy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
