<?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>The Pythian Blog &#187; Singer Wang</title>
	<atom:link href="http://www.pythian.com/news/author/singerwang/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:54:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Silent MyISAM Table Definition Changes and mysqldump</title>
		<link>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/</link>
		<comments>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/#comments</comments>
		<pubDate>Thu, 16 Jun 2011 21:02:40 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[myisam]]></category>
		<category><![CDATA[mysqldump]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=22695</guid>
		<description><![CDATA[The other day while trying to move a schema from one MySQL server to another, I encountered a very odd issue. The schema to be moved contained both MyISAM and InnoDB tables, so the only option I had was to dump the schema using mysqldump on the source server and import it on the destination [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/22695/silent-myisam-table-definition-changes-and-mysqldump/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Beware of starting slaves from the position in the master.info file</title>
		<link>http://www.pythian.com/news/19679/beware-of-starting-slaves-from-position-in-the-master-info-file/</link>
		<comments>http://www.pythian.com/news/19679/beware-of-starting-slaves-from-position-in-the-master-info-file/#comments</comments>
		<pubDate>Thu, 13 Jan 2011 02:01:46 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[slaves]]></category>
		<category><![CDATA[tricks]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=19679</guid>
		<description><![CDATA[I&#8217;ve seen many a good DBA make the master of starting slaves from the position in the master.info file, most recently this week, that I want to bring it to everyone&#8217;s attention. Of course I mean the underlying issue and not the names of the DBA because that would be cruel. In the typical scenario [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/19679/beware-of-starting-slaves-from-position-in-the-master-info-file/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>When the ALTER TABLE privilege is not enough to run ALTER TABLE</title>
		<link>http://www.pythian.com/news/9007/when-the-alter-table-privilege-is-not-enough-to-run-alter-table/</link>
		<comments>http://www.pythian.com/news/9007/when-the-alter-table-privilege-is-not-enough-to-run-alter-table/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 15:06:44 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[alter]]></category>
		<category><![CDATA[alter table]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[grant]]></category>
		<category><![CDATA[privilege]]></category>
		<category><![CDATA[Pythian]]></category>
		<category><![CDATA[rename]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=9007</guid>
		<description><![CDATA[I recently granted ALTER access in MySQL so a user could run the ALTER TABLE command . However after I granted the necessary privileges, the user was still not able to perform the tasks needed. Reproducing the issue using a test instance, I granted a test user the required privileges and MySQL reported no errors [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/9007/when-the-alter-table-privilege-is-not-enough-to-run-alter-table/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GPL/ASL/BSD License Misconceptions and MySQL</title>
		<link>http://www.pythian.com/news/6893/gplaslbsd-license-misconceptions-and-mysql/</link>
		<comments>http://www.pythian.com/news/6893/gplaslbsd-license-misconceptions-and-mysql/#comments</comments>
		<pubDate>Thu, 31 Dec 2009 20:43:55 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Oracle]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[ASL]]></category>
		<category><![CDATA[bsd]]></category>
		<category><![CDATA[GNU Public License]]></category>
		<category><![CDATA[gpl]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=6893</guid>
		<description><![CDATA[Having been a free software user and supporter for many years, I am disheartened by some of the comments made in the MySQL/Oracle debate regarding the GNU Public License (GPL) and other licenses. There is much throwing around of misconceptions and untruths about licenses and their differences. In this blog, I shall take on some [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/6893/gplaslbsd-license-misconceptions-and-mysql/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>MySQL on Debian and Ubuntu</title>
		<link>http://www.pythian.com/news/3794/mysql-on-debian-and-ubuntu/</link>
		<comments>http://www.pythian.com/news/3794/mysql-on-debian-and-ubuntu/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 22:12:23 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[mysqld_safe]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[Pythian]]></category>
		<category><![CDATA[startup]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=3794</guid>
		<description><![CDATA[Debian Linux (the underlying foundation of Ubuntu) manages the startup/shutdown of MySQL quite differently from the ways I am used to. I am a long-time user of both the MySQL binary provided by Red Hat/SuSE (along with Fedora and clones like CentOS and Oracle Enterprise Linux) and the official binary from mysql.com. After the successful [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/3794/mysql-on-debian-and-ubuntu/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>MySQL 5.1 and InnoDB Hot Backup Gotcha</title>
		<link>http://www.pythian.com/news/3734/mysql-51-and-innodb-hot-backup-gotcha/</link>
		<comments>http://www.pythian.com/news/3734/mysql-51-and-innodb-hot-backup-gotcha/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 21:10:05 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[backups]]></category>
		<category><![CDATA[CSV]]></category>
		<category><![CDATA[innobackup.pl]]></category>
		<category><![CDATA[innobackupex.pl]]></category>
		<category><![CDATA[Innobase]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[innodb hot backup]]></category>
		<category><![CDATA[mysql 5.1]]></category>
		<category><![CDATA[Percona]]></category>
		<category><![CDATA[Pythian]]></category>
		<category><![CDATA[xtrabackup]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=3734</guid>
		<description><![CDATA[Recently while we were building a slave with a newer version of MySQL 5.1 from an InnoDB Hot backup, the following error occurred when we ran mysql_upgrade: mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Running 'mysql_fix_privilege_tables'... ERROR 13 (HY000) at line 311: Can't get stat of './mysql/general_log.CSV' (Errcode: 2) ERROR [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/3734/mysql-51-and-innodb-hot-backup-gotcha/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>InnoDB Hot Backup Utility Bug</title>
		<link>http://www.pythian.com/news/1500/innodb-hot-backup-utility-bug/</link>
		<comments>http://www.pythian.com/news/1500/innodb-hot-backup-utility-bug/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 17:51:47 +0000</pubDate>
		<dc:creator>Singer Wang</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[backups]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[innodb hot backup]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1500/innodb-hot-backup-utility-bug</guid>
		<description><![CDATA[If you are using InnoDB Hot Backup utility and the innobackup.pl wrapper script, be very careful if you are not running backups under the system mysql user. There is a bug which causes InnoDB Hot Backup to sometimes report a successful backup when it actually failed. The last few dozen lines of the output was [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1500/innodb-hot-backup-utility-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

