<?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>Pablowe &#187; MySQL</title>
	<atom:link href="http://www.pablowe.net/category/mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pablowe.net</link>
	<description>%&#62; random tech;</description>
	<lastBuildDate>Fri, 30 Sep 2011 16:54:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Installing HandlerSocket on RHEL 6 + Percona-Server 5.5 in Five(ish) Easy Steps</title>
		<link>http://www.pablowe.net/2011/09/installing-handlersocket-on-rhel-6-percona-server-5-5-in-fiveish-easy-steps/</link>
		<comments>http://www.pablowe.net/2011/09/installing-handlersocket-on-rhel-6-percona-server-5-5-in-fiveish-easy-steps/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 19:59:41 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Random Tech]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=767</guid>
		<description><![CDATA[As a followup to my previous post on installing HandlerSocket on CentOS 5 + Percona-Server 5.1, I&#8217;ve been asked to provide an updated HOWTO for RHEL 6 + Percona-Server 5.5. Although very similar to the original steps, there are some new traps (RHEL 6 comes with SELinux enabled) and there are some new ec2 gotchas! [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/09/installing-handlersocket-on-rhel-6-percona-server-5-5-in-fiveish-easy-steps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HandlerSocket execute_multi Curiosities</title>
		<link>http://www.pablowe.net/2011/04/handlersocket-execute_multi-curiosities/</link>
		<comments>http://www.pablowe.net/2011/04/handlersocket-execute_multi-curiosities/#comments</comments>
		<pubDate>Mon, 04 Apr 2011 21:13:05 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[NoSQL]]></category>
		<category><![CDATA[Random Tech]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=715</guid>
		<description><![CDATA[A post on the HandlerSocket-dev mailing list the other day got me thinking about the performance of MySQL&#8217;s IN() construct versus HandlerSocket&#8217;s execute_multi. So I started a little test, using MySQL 5.5 + HandlerSocket&#8217;s latest commits: mysql> CREATE TABLE `test`.`t1` ( -> `id` int unsigned NOT NULL AUTO_INCREMENT, -> `val` char(32) NOT NULL, -> PRIMARY [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/04/handlersocket-execute_multi-curiosities/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>HandlerSocket Edge Cases</title>
		<link>http://www.pablowe.net/2011/03/handlersocket-edge-cases/</link>
		<comments>http://www.pablowe.net/2011/03/handlersocket-edge-cases/#comments</comments>
		<pubDate>Mon, 28 Mar 2011 17:24:57 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Random Tech]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=671</guid>
		<description><![CDATA[A couple of weeks ago at the San Francisco MySQL Meetup, I gave a talk on HandlerSocket and got a couple of questions that, while I thought I knew the answer, I had never actually verified by testing. So, for the attendees who asked, here are the questions and answers: Can you use HandlerSocket on [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/03/handlersocket-edge-cases/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speaking about HandlerSocket at the next SF MySQL Meetup</title>
		<link>http://www.pablowe.net/2011/03/im-speaking-about-handlersocket-at-the-next-sf-mysql-meetup/</link>
		<comments>http://www.pablowe.net/2011/03/im-speaking-about-handlersocket-at-the-next-sf-mysql-meetup/#comments</comments>
		<pubDate>Mon, 14 Mar 2011 21:25:32 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[Anouncement]]></category>
		<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[NoSQL]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=661</guid>
		<description><![CDATA[[shameless plug] I&#8217;ll be at the next SF MySQL Meetup giving a talk on HandlerSocket called &#8220;NoSQL in MySQL: HandlerSocket plugin demystified&#8221;. We&#8217;ll ask, and answer, the following questions: What is HandlerSocket? Where does HandlerSocket fit in my application stack? Why would I want to use HandlerSocket? How do I use Handlersocket? We&#8217;ll walk through [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/03/im-speaking-about-handlersocket-at-the-next-sf-mysql-meetup/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Nagios Checks for HandlerSocket</title>
		<link>http://www.pablowe.net/2011/02/nagios-checks-for-handlersocket/</link>
		<comments>http://www.pablowe.net/2011/02/nagios-checks-for-handlersocket/#comments</comments>
		<pubDate>Fri, 11 Feb 2011 21:08:06 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Nagios]]></category>
		<category><![CDATA[Random Tech]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=638</guid>
		<description><![CDATA[I&#8217;ve written some new Nagios checks for HandlerSocket. check_handlersocket is a part of http://code.google.com/p/check-mysql-all/, and is meant to be called locally on the HandlerSocket server (usually via NRPE), but the perl-Net-HandlerSocket module must be installed. Feedback is welcome, usage is as follows: Usage: check_handlersocket -K [options] Options: -K, --check= The check to run --columns= Comma-separated [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/02/nagios-checks-for-handlersocket/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What The Community DOESN&#8217;T Know About InnoDB in MySQL 5.5</title>
		<link>http://www.pablowe.net/2011/01/what-the-community-doesnt-know-about-innodb-in-mysql-5-5/</link>
		<comments>http://www.pablowe.net/2011/01/what-the-community-doesnt-know-about-innodb-in-mysql-5-5/#comments</comments>
		<pubDate>Sat, 29 Jan 2011 23:52:18 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[MySQL]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=607</guid>
		<description><![CDATA[MySQL 5.5 introduced a number of InnoDB startup options and system variables. I did a quick Google search for each parameter mentioned on the official page and was a little surprised by the results (full results at the bottom of this post). There are a few clear variables with exponentially lower results indicating one of [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/01/what-the-community-doesnt-know-about-innodb-in-mysql-5-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installing HandlerSocket on CentOS 5 + Percona-Server in Five Easy Steps</title>
		<link>http://www.pablowe.net/2011/01/installing-handlersocket-on-centos-5-percona-server-in-five-easy-steps/</link>
		<comments>http://www.pablowe.net/2011/01/installing-handlersocket-on-centos-5-percona-server-in-five-easy-steps/#comments</comments>
		<pubDate>Thu, 06 Jan 2011 18:55:24 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[NoSQL]]></category>
		<category><![CDATA[Random Tech]]></category>
		<category><![CDATA[Install HandlerSocket]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=592</guid>
		<description><![CDATA[I&#8217;ve been spending a lot of time working on HandlerSocket these days, so I&#8217;ll be posting tidbits on this a bit more frequently than in the past. This first post is a quick one to help people get a test environment up and running quickly so they can do their functional testing. The title is [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/01/installing-handlersocket-on-centos-5-percona-server-in-five-easy-steps/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 6</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 22:35:22 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=527</guid>
		<description><![CDATA[Requirement 6 of PCI DSS v1.2 states that in order to be compliant, an organization must: &#8220;Develop and maintain secure systems and applications&#8221; &#8220;Unscrupulous individuals use security vulnerabilities to gain privileged access to systems. Many of these vulnerabilities are fixed by vendor- provided security patches, which must be installed by the entities that manage the [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL &#8211; Requirement 4</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 19:14:45 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Administration]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[MySQL Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=513</guid>
		<description><![CDATA[Requirement 4 of PCI DSS v1.2 states that we must: &#8220;Encrypt transmission of cardholder data across open, public networks&#8221; Specifically, &#8220;Sensitive information must be encrypted during transmission over networks that are easily accessed by malicious individuals. Misconfigured wireless networks and vulnerabilities in legacy encryption and authentication protocols can be continued targets of malicious individuals who [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS &amp; MySQL: Requirement 3</title>
		<link>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/</link>
		<comments>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 14:27:51 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=447</guid>
		<description><![CDATA[Requirement 3 of the PCI DSS v1.2 is: &#8220;Protect Stored Cardholder Data&#8221; As vague as that sounds, the PCI DSS enumerates exactly what that covers: Data Element Storage Permitted Protection Required PCI DSS Req 3.4 Primary Account Number Yes Yes Yes Cardholder Name* Yes Yes No Service Code* Yes Yes No Expiration Date* Yes Yes [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2010/04/pci-dss-mysql-requirement-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

