<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>All things Sysadmin &#187; MySQL</title>
	<atom:link href="http://northernmost.org/blog/category/all-things-mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://northernmost.org/blog</link>
	<description>Just another manic Monday</description>
	<lastBuildDate>Wed, 26 May 2010 13:21:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Don&#8217;t fix, work around &#8211; MySQL</title>
		<link>http://northernmost.org/blog/dont-fix-work-around-mysql/</link>
		<comments>http://northernmost.org/blog/dont-fix-work-around-mysql/#comments</comments>
		<pubDate>Sun, 26 Oct 2008 20:06:15 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[scaling]]></category>
		<category><![CDATA[sun]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=167</guid>
		<description><![CDATA[Sun decided to not go down the route of reviewing and accepting the patches, but are now suggesting - are you sitting down? - running multiple instances on the same hardware. ]]></description>
		<wfw:commentRss>http://northernmost.org/blog/dont-fix-work-around-mysql/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Resyncing slaves with slaves</title>
		<link>http://northernmost.org/blog/resyncing-slaves-with-slaves/</link>
		<comments>http://northernmost.org/blog/resyncing-slaves-with-slaves/#comments</comments>
		<pubDate>Sat, 05 Jul 2008 02:44:17 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[resync slave]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=31</guid>
		<description><![CDATA[When dealing with replicated setups with two or more slaves sharing a master, it appears as if a lot of people overlook the obvious. You don't need to take your master down to resync a slave. I was hoping I wouldn't need to post about this, but I see people taking down their masters when they have perfectly healthy slaves way too often to let it slip. 
]]></description>
		<wfw:commentRss>http://northernmost.org/blog/resyncing-slaves-with-slaves/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MySQL load balancing with mylbhelper</title>
		<link>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/</link>
		<comments>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/#comments</comments>
		<pubDate>Sun, 29 Jun 2008 02:59:10 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Sundry sysadmin]]></category>
		<category><![CDATA[hardware load balancing]]></category>
		<category><![CDATA[mylbhelper]]></category>
		<category><![CDATA[mysql load balancing]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=30</guid>
		<description><![CDATA[A customer of ours was in this particular situation. They had a very decent hardware load balancer for their webservers with capacity to spare. So they ended up load balancing the mysql instances through the same device and using a piece of software I've written called <a href="http://mylbhelper.northernmost.org">mylbhelper</a>. 
]]></description>
		<wfw:commentRss>http://northernmost.org/blog/mysql-load-balancing-with-mylbhelper/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Tool tip: mysqlsniffer</title>
		<link>http://northernmost.org/blog/tool-tip-mysqlsniff/</link>
		<comments>http://northernmost.org/blog/tool-tip-mysqlsniff/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 23:59:52 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[mysqlsniff]]></category>
		<category><![CDATA[querysniffer]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=29</guid>
		<description><![CDATA[mysqlsniff is a tool that I find very useful and utilise a lot, but it doesn't seem to be so widely known as it deserves to be. It's pretty much general_log light without a restart!]]></description>
		<wfw:commentRss>http://northernmost.org/blog/tool-tip-mysqlsniff/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wet dream finally coming through?</title>
		<link>http://northernmost.org/blog/wet-dream-finally-coming-through/</link>
		<comments>http://northernmost.org/blog/wet-dream-finally-coming-through/#comments</comments>
		<pubDate>Tue, 03 Jun 2008 22:17:34 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[maatkit]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[self healing replication]]></category>
		<category><![CDATA[summer of code]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=28</guid>
		<description><![CDATA[My major beef with it is that it's not self-healing. Sure, you can monitor, script and re-jig things to a certain extent. But this is why I was thrilled when read the MySQL Forge suggestions for Google Summer of Code. One of the suggestions is to enable self-healing replication using components, or at least concepts, from maatkit and Google's MMRM.  ]]></description>
		<wfw:commentRss>http://northernmost.org/blog/wet-dream-finally-coming-through/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>paramy &#8211; import dumps in a flash</title>
		<link>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/</link>
		<comments>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/#comments</comments>
		<pubDate>Fri, 30 May 2008 21:35:35 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[data import]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[paramy]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=27</guid>
		<description><![CDATA[Basically it's a multithreaded client. Most servers these days have, or certainly should have, multiple disks and multiple CPU cores and reasonably fast storage. So using a single threaded client to insert those hundreds of thousands or millions of records doesn't make that much sense today. There's quite a lot of time to save. I've ran some tests on MySQL 5.1.24 and compared the results with those from the stock mysql client.

]]></description>
		<wfw:commentRss>http://northernmost.org/blog/paramy-import-dumps-in-a-flash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>InnoDB plugin compression with benchmarks</title>
		<link>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/</link>
		<comments>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/#comments</comments>
		<pubDate>Thu, 29 May 2008 19:57:51 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=26</guid>
		<description><![CDATA[InnoDB Plugin compression levels and their performance examined.]]></description>
		<wfw:commentRss>http://northernmost.org/blog/innodb-plugin-compression-with-benchmarks/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The cost of table locking and index flushing in MySQL</title>
		<link>http://northernmost.org/blog/the-cost-of-table-locking-and-index-flushing-in-mysql/</link>
		<comments>http://northernmost.org/blog/the-cost-of-table-locking-and-index-flushing-in-mysql/#comments</comments>
		<pubDate>Tue, 06 May 2008 17:24:53 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[explicit locking]]></category>
		<category><![CDATA[index flushing]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[table locking]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=25</guid>
		<description><![CDATA[This post may not apply to the large majority of applications out there, but I think it&#8217;s interesting enough. When doing sequential bulk inserts into MyISAM tables, you may think you&#8217;re getting rather good performance number wise. On low end commodity hardware with not too wide tables, you very easily get up into the thousands per [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/the-cost-of-table-locking-and-index-flushing-in-mysql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL&#8217;s non-GPL adventure</title>
		<link>http://northernmost.org/blog/mysqls-non-gpl-adventure/</link>
		<comments>http://northernmost.org/blog/mysqls-non-gpl-adventure/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 08:28:23 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=23</guid>
		<description><![CDATA[I&#8217;m a bit late on this piece of news, and it&#8217;s been treated by more or less everyone who owns a blog. The news in short is that MySQL has decided to not release their online backup tool/driver to the masses. It will only be available to paying Enterprise customers. A lot of people have [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/mysqls-non-gpl-adventure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Proxy on RHEL5</title>
		<link>http://northernmost.org/blog/mysql-proxy-on-rhel5/</link>
		<comments>http://northernmost.org/blog/mysql-proxy-on-rhel5/#comments</comments>
		<pubDate>Thu, 10 Apr 2008 22:42:24 +0000</pubDate>
		<dc:creator>Erik Ljungstrom</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[lua]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[mysql_proxy]]></category>
		<category><![CDATA[rhel 5]]></category>

		<guid isPermaLink="false">http://northernmost.org/blog/?p=21</guid>
		<description><![CDATA[Just a little timesaver; When attempting to install mysql proxy on RHEL5, you will most likely soon be staring at this message: ... checking for LUA... checking for LUA... configure: error: Package requirements (lua5.1 &#62;= 5.1) were not met: No package 'lua5.1' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a [...]]]></description>
		<wfw:commentRss>http://northernmost.org/blog/mysql-proxy-on-rhel5/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
