<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Jeremy Cole</title>
	<atom:link href="http://blog.jcole.us/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jcole.us</link>
	<description>Geek, electronics nerd, database nerd, father of three.</description>
	<lastBuildDate>Thu, 16 May 2013 12:49:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on InnoDB Tidbit: The doublewrite buffer wastes 32 pages (512 KiB) by [MySQL 5.6] double write buffer的几个关键函数 &#124; Simple Life</title>
		<link>http://blog.jcole.us/2013/05/05/innodb-tidbit-the-doublewrite-buffer-wastes-32-pages-512-kib/#comment-2654</link>
		<dc:creator><![CDATA[[MySQL 5.6] double write buffer的几个关键函数 &#124; Simple Life]]></dc:creator>
		<pubDate>Thu, 16 May 2013 12:49:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1088#comment-2654</guid>
		<description><![CDATA[[&#8230;] 另外jeremy cole 提到dblwr buffer的一个有趣的现象，传送门：http://blog.jcole.us/2013/05/05/innodb-tidbit-the-doublewrite-buffer-wastes-32-pages-512-kib/ [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] 另外jeremy cole 提到dblwr buffer的一个有趣的现象，传送门：http://blog.jcole.us/2013/05/05/innodb-tidbit-the-doublewrite-buffer-wastes-32-pages-512-kib/ [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by Suresh Kuna</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2649</link>
		<dc:creator><![CDATA[Suresh Kuna]]></dc:creator>
		<pubDate>Wed, 15 May 2013 15:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2649</guid>
		<description><![CDATA[Nice, good to know the internal things of cluster index, Thank Jeremy C]]></description>
		<content:encoded><![CDATA[<p>Nice, good to know the internal things of cluster index, Thank Jeremy C</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by Justin Swanhart</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2645</link>
		<dc:creator><![CDATA[Justin Swanhart]]></dc:creator>
		<pubDate>Sun, 12 May 2013 06:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2645</guid>
		<description><![CDATA[Because a mutex is held while increasing the key instead of using atomic increment.  The mutex has to be held by DDL operations and can be held for a long time (relatively) during table drop operations.  So a drop of table X could result in a mutex wait during insert on table Y.]]></description>
		<content:encoded><![CDATA[<p>Because a mutex is held while increasing the key instead of using atomic increment.  The mutex has to be held by DDL operations and can be held for a long time (relatively) during table drop operations.  So a drop of table X could result in a mutex wait during insert on table Y.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by Cream</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2644</link>
		<dc:creator><![CDATA[Cream]]></dc:creator>
		<pubDate>Sun, 12 May 2013 02:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2644</guid>
		<description><![CDATA[Why we could  experience random insert during operations like dropping (unrelated) tables? The ROW_ID is increases monotonically, so is there any situation that the next ROW_ID less than current max ROW_ID?]]></description>
		<content:encoded><![CDATA[<p>Why we could  experience random insert during operations like dropping (unrelated) tables? The ROW_ID is increases monotonically, so is there any situation that the next ROW_ID less than current max ROW_ID?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On efficiently geo-referencing IPs with MaxMind GeoIP and MySQL GIS by zetaz</title>
		<link>http://blog.jcole.us/2007/11/24/on-efficiently-geo-referencing-ips-with-maxmind-geoip-and-mysql-gis/#comment-2640</link>
		<dc:creator><![CDATA[zetaz]]></dc:creator>
		<pubDate>Fri, 10 May 2013 14:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://jcole.us/blog/archives/2007/11/24/on-efficiently-geo-referencing-ips-with-maxmind-geoip-and-mysql-gis/#comment-2640</guid>
		<description><![CDATA[hello
first thank you for this very interesting tread.
I have some times, very big log files (50 000  lines) and want to use the maxmind database to know where the ip come from.
the scrypt proposed by Andy Skelton  seems to be very nice but i don&#039;t know how to use it with a table containing all the IP ( the IP are in IP V4 flavor)
for the more i&#039;m really a newby in MySQL

so what i need.
For each IP in my iplog table i need as a result , the Ip itself + the country + region + city.

thank you for your help]]></description>
		<content:encoded><![CDATA[<p>hello<br />
first thank you for this very interesting tread.<br />
I have some times, very big log files (50 000  lines) and want to use the maxmind database to know where the ip come from.<br />
the scrypt proposed by Andy Skelton  seems to be very nice but i don&#8217;t know how to use it with a table containing all the IP ( the IP are in IP V4 flavor)<br />
for the more i&#8217;m really a newby in MySQL</p>
<p>so what i need.<br />
For each IP in my iplog table i need as a result , the Ip itself + the country + region + city.</p>
<p>thank you for your help</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by InnoDB without PRIMARY KEY &#124; Open Query blog</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2638</link>
		<dc:creator><![CDATA[InnoDB without PRIMARY KEY &#124; Open Query blog]]></dc:creator>
		<pubDate>Fri, 10 May 2013 10:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2638</guid>
		<description><![CDATA[[&#8230;] code caught he was definitely interested in exploring the issue. The result is this blog post: http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/ for your enlightenment and [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] code caught he was definitely interested in exploring the issue. The result is this blog post: http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/ for your enlightenment and [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on InnoDB by InnoDB Tidbit: The doublewrite buffer wastes 32 pages (512 KiB) &#8211; Jeremy Cole</title>
		<link>http://blog.jcole.us/innodb/#comment-2595</link>
		<dc:creator><![CDATA[InnoDB Tidbit: The doublewrite buffer wastes 32 pages (512 KiB) &#8211; Jeremy Cole]]></dc:creator>
		<pubDate>Sun, 05 May 2013 19:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?page_id=906#comment-2595</guid>
		<description><![CDATA[[...] InnoDB [...]]]></description>
		<content:encoded><![CDATA[<p>[...] InnoDB [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MySQL Community Contributor of the Year 2013 by Jinny</title>
		<link>http://blog.jcole.us/2013/04/25/mysql-community-contributor-of-the-year-2013/#comment-2576</link>
		<dc:creator><![CDATA[Jinny]]></dc:creator>
		<pubDate>Fri, 03 May 2013 12:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1049#comment-2576</guid>
		<description><![CDATA[Congratulation! you deserved it. Keep doing your great job to make MySQL better.]]></description>
		<content:encoded><![CDATA[<p>Congratulation! you deserved it. Keep doing your great job to make MySQL better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by Jeremy Cole</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2572</link>
		<dc:creator><![CDATA[Jeremy Cole]]></dc:creator>
		<pubDate>Fri, 03 May 2013 06:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2572</guid>
		<description><![CDATA[No, I don&#039;t know of any reason it couldn&#039;t be changed to use a per-table sequence. I would think it would be fairly easy actually.]]></description>
		<content:encoded><![CDATA[<p>No, I don&#8217;t know of any reason it couldn&#8217;t be changed to use a per-table sequence. I would think it would be fairly easy actually.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How does InnoDB behave without a Primary Key? by Justin Swanhart</title>
		<link>http://blog.jcole.us/2013/05/02/how-does-innodb-behave-without-a-primary-key/#comment-2571</link>
		<dc:creator><![CDATA[Justin Swanhart]]></dc:creator>
		<pubDate>Fri, 03 May 2013 06:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jcole.us/?p=1060#comment-2571</guid>
		<description><![CDATA[Very interesting.  I too assumed that generation was via a per-table sequence.  Is there a reason you can think of that a sequence could not be maintained per-table?  

I ask, because it is very common to have partitioned tables without primary or unique keys.]]></description>
		<content:encoded><![CDATA[<p>Very interesting.  I too assumed that generation was via a per-table sequence.  Is there a reason you can think of that a sequence could not be maintained per-table?  </p>
<p>I ask, because it is very common to have partitioned tables without primary or unique keys.</p>
]]></content:encoded>
	</item>
</channel>
</rss>