<?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: TMP_TABLE_SIZE and MAX_HEAP_TABLE_SIZE</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/</link>
	<description>Everything about MySQL Performance</description>
	<pubDate>Tue, 02 Dec 2008 12:43:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: rajeesh</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-193871</link>
		<dc:creator>rajeesh</dc:creator>
		<pubDate>Thu, 15 Nov 2007 10:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-193871</guid>
		<description>tmp_table_size=45M , if its increse or decrese what will the effect of mysql database</description>
		<content:encoded><![CDATA[<p>tmp_table_size=45M , if its increse or decrese what will the effect of mysql database</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hjalmars it-blogg &#187; MySQL-tweaking</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-169996</link>
		<dc:creator>Hjalmars it-blogg &#187; MySQL-tweaking</dc:creator>
		<pubDate>Wed, 19 Sep 2007 20:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-169996</guid>
		<description>[...] så mycket information jag kan om ämnet genom att läsa mysqls optimeringskapitel, forumtrådar, blogginlägg, tricks och tricks [...]</description>
		<content:encoded><![CDATA[<p>[...] så mycket information jag kan om ämnet genom att läsa mysqls optimeringskapitel, forumtrådar, blogginlägg, tricks och tricks [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-35418</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 23 Jan 2007 20:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-35418</guid>
		<description>Thank you James,

I see it got added there. As MySQL old timer I did not get back to that page for other than new variables as I remember meaning about them. 

The quote I gave was from this url:

http://dev.mysql.com/doc/refman/5.0/en/memory-storage-engine.html

I guess I would expect working do be different in this place to.

It is probably hard to keep such large document synchronized.</description>
		<content:encoded><![CDATA[<p>Thank you James,</p>
<p>I see it got added there. As MySQL old timer I did not get back to that page for other than new variables as I remember meaning about them. </p>
<p>The quote I gave was from this url:</p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/memory-storage-engine.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/memory-storage-engine.html</a></p>
<p>I guess I would expect working do be different in this place to.</p>
<p>It is probably hard to keep such large document synchronized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Holt</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-35416</link>
		<dc:creator>James Holt</dc:creator>
		<pubDate>Tue, 23 Jan 2007 19:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-35416</guid>
		<description>Peter, reading this I thought I recalled reading about it in the docs somewhere.  
I looked around and found it here: 

http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
(scroll down to tmp_table_size)

Not defending the behavior by any stretch; it is highly anti-intuitive.

-James Holt</description>
		<content:encoded><![CDATA[<p>Peter, reading this I thought I recalled reading about it in the docs somewhere.<br />
I looked around and found it here: </p>
<p><a href="http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html</a><br />
(scroll down to tmp_table_size)</p>
<p>Not defending the behavior by any stretch; it is highly anti-intuitive.</p>
<p>-James Holt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Day</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34553</link>
		<dc:creator>James Day</dc:creator>
		<pubDate>Mon, 22 Jan 2007 06:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34553</guid>
		<description>Peter, thanks for mentioning this. I expect that the plan will be changed now Sergei knows that it would break backwards compatibility. A new synonym for tmp_table_size that is the memory limit and a new variable for disk size would do the job without breaking existing setups. Then tmp_table_size can be deprecated.</description>
		<content:encoded><![CDATA[<p>Peter, thanks for mentioning this. I expect that the plan will be changed now Sergei knows that it would break backwards compatibility. A new synonym for tmp_table_size that is the memory limit and a new variable for disk size would do the job without breaking existing setups. Then tmp_table_size can be deprecated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34308</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sun, 21 Jan 2007 22:44:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34308</guid>
		<description>Thank you for looking into in Sergei

While fixing bug I just would make sure there are limited behavior changes compared to old timers expectations.</description>
		<content:encoded><![CDATA[<p>Thank you for looking into in Sergei</p>
<p>While fixing bug I just would make sure there are limited behavior changes compared to old timers expectations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergei Golubchik</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34307</link>
		<dc:creator>Sergei Golubchik</dc:creator>
		<pubDate>Sun, 21 Jan 2007 22:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34307</guid>
		<description>I saw that in the code. But now, after testing, I see that, indeed, tmp_table_size doesn't limit the size of on-disk tables (table-&#62;s-&#62;max_rows is set to limit it, but it's not copied to ci-&#62;max_rows for mi_create to see it) - it must be a bug too.</description>
		<content:encoded><![CDATA[<p>I saw that in the code. But now, after testing, I see that, indeed, tmp_table_size doesn&#8217;t limit the size of on-disk tables (table-&gt;s-&gt;max_rows is set to limit it, but it&#8217;s not copied to ci-&gt;max_rows for mi_create to see it) - it must be a bug too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34300</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sun, 21 Jan 2007 21:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34300</guid>
		<description>Sergei,

Yes I know lower value was used but it was not documented - I quoted the manual and config files give you the same idea - want larger in memory tables increase tmp_table_size. 

Now regarding "Also tmp_table_size was used to limit the size of the temporary table - no matter whether it’s in memory or on disk."   Where does this come from ? 

I constantly see temporary tables sized in gigabytes while tmp_table_size is set to 32M or similar. 

If that would be correct fix would be reasonable but it is not.  Simply test it :)</description>
		<content:encoded><![CDATA[<p>Sergei,</p>
<p>Yes I know lower value was used but it was not documented - I quoted the manual and config files give you the same idea - want larger in memory tables increase tmp_table_size. </p>
<p>Now regarding &#8220;Also tmp_table_size was used to limit the size of the temporary table - no matter whether it’s in memory or on disk.&#8221;   Where does this come from ? </p>
<p>I constantly see temporary tables sized in gigabytes while tmp_table_size is set to 32M or similar. </p>
<p>If that would be correct fix would be reasonable but it is not.  Simply test it <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergei Golubchik</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34165</link>
		<dc:creator>Sergei Golubchik</dc:creator>
		<pubDate>Sun, 21 Jan 2007 12:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-34165</guid>
		<description>The description is slightly wrong.
The lower value from tmp_table_size and use max_heap_table_size was used to define when temporary table was converted from memory to disk.
Also tmp_table_size was used to limit the size of the temporary table - no matter whether it's in memory or on disk.
And max_heap_table_size was also used to limit the size of explicitly created HEAP tables.

The fix is to introduce another variable memory_tmp_table_size and use it instead of the "lower value ...", to define when a temporary table is converted to MyISAM. Thus max_heap_table_size will have no effect on temporary tables, and tmp_table_size keeps its "upper boundary" meaning.</description>
		<content:encoded><![CDATA[<p>The description is slightly wrong.<br />
The lower value from tmp_table_size and use max_heap_table_size was used to define when temporary table was converted from memory to disk.<br />
Also tmp_table_size was used to limit the size of the temporary table - no matter whether it&#8217;s in memory or on disk.<br />
And max_heap_table_size was also used to limit the size of explicitly created HEAP tables.</p>
<p>The fix is to introduce another variable memory_tmp_table_size and use it instead of the &#8220;lower value &#8230;&#8221;, to define when a temporary table is converted to MyISAM. Thus max_heap_table_size will have no effect on temporary tables, and tmp_table_size keeps its &#8220;upper boundary&#8221; meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-33914</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sun, 21 Jan 2007 00:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/19/tmp_table_size-and-max_heap_table_size/#comment-33914</guid>
		<description>Yes quite possible. 

In fact I remember there were few other cases when non documented parameters are taken into consideration</description>
		<content:encoded><![CDATA[<p>Yes quite possible. </p>
<p>In fact I remember there were few other cases when non documented parameters are taken into consideration</p>
]]></content:encoded>
	</item>
</channel>
</rss>
