<?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: Using btree indexes to speed up MySQL MEMORY (HEAP) table deletes	</title>
	<atom:link href="https://www.brandonchecketts.com/archives/using-btree-indexes-to-speed-up-mysql-memory-heap-table-deletes/feed" rel="self" type="application/rss+xml" />
	<link>https://www.brandonchecketts.com/archives/using-btree-indexes-to-speed-up-mysql-memory-heap-table-deletes</link>
	<description>Web Programming, Linux System Administation, and Entrepreneurship in Athens Georgia</description>
	<lastBuildDate>Tue, 08 Oct 2024 17:53:36 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>
	<item>
		<title>
		By: Brandon		</title>
		<link>https://www.brandonchecketts.com/archives/using-btree-indexes-to-speed-up-mysql-memory-heap-table-deletes/comment-page-1#comment-344</link>

		<dc:creator><![CDATA[Brandon]]></dc:creator>
		<pubDate>Thu, 26 Jul 2007 13:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.brandonchecketts.com/archives/using-btree-indexes-to-speed-up-mysql-memory-heap-table-deletes#comment-344</guid>

					<description><![CDATA[I&#039;ve been monitoring this table and noticed that it just continually grows in size.  Upon investigating, I found a &lt;a href=&quot;https://bugs.mysql.com/bug.php?id=18160&quot; rel=&quot;nofollow&quot;&gt;MySQL Bug&lt;/a&gt; report that confirms the problem and says that it is fixed in 5.0.23.  Evidently it is not a problem with the actual memory usage, just how MySQL calculates the usage.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been monitoring this table and noticed that it just continually grows in size.  Upon investigating, I found a <a href="https://bugs.mysql.com/bug.php?id=18160" rel="nofollow">MySQL Bug</a> report that confirms the problem and says that it is fixed in 5.0.23.  Evidently it is not a problem with the actual memory usage, just how MySQL calculates the usage.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
