Author: Singer Wang

Percona Live MySQL Conference 2012 – Day 1 Review

Day 1 is the first official day of the Percona Live MySQL Conference. It began with two mini keynotes by Peter Zaitev and Baron Schwarz of Percona talking about the history of MySQL and his beginnings in the open source movement, respectively. It was very nostalgic, and I’m sure it brought a tear to a few people’s eyes.

Read More >

Percona Live MySQL Conference 2012 – Day 0 Review

Day 0 of the MySQL Conference was a day unlike any other day. It was, in fact, tutorial day. While regular days of the Percona Live MySQL Conference feature 50 minute sessions, usually split into a 40 minute talk and a 5-10 minute question period, tutorials are 3-hour-long sessions (with a generous 10 minute break in the middle for those that wish to go to the WC) that provide an in-depth dive into some aspect of MySQL.

Read More >

Security Around MySQL @ Percona Live MySQL Conference 2012

In about 4 hours at 2PM PDT, I’ll be giving my talk “Security Around MySQL” at Ballroom A at the Percona Live MySQL Conference 2012. It’s a summary and guide of practical and easy-to-implement security tips around MySQL and the application. These tips were all gleamed from my years at start-ups (some of which I worked on and some which I founded) and from my experience at Pythian.

Read More >

Silent MyISAM Table Definition Changes and mysqldump

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 server. I did some digging and found that the problem was that the MyISAM engine silently changed the table definition without any indications. Here are some solutions.

Read More >

Beware Starting Slaves in the Position in the master.info file

I’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’s attention.

Read More >

When the ALTER TABLE privilege is not enough to run ALTER TABLE

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. Then I realized what the issue was and how to fix it.

Read More >

GPL/ASL/BSD License Misconceptions and MySQL

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 of the bigger misconceptions.

Read More >

MySQL on Debian and Ubuntu

When MySQL is first installed on Ubuntu/Debian, this problem never occurs because the package as part of the post installation process randomly creates a password for the debian-sys-maint user, creates the user in MySQL (during the initial installation the root MySQL user has no password so is able to login as root), and creates the /etc/mysql/debian-my.cnf file on the system. So what’s the solution? Well, there are ways to deal with it.

Read More >

MySQL 5.1 and InnoDB Hot Backup Gotcha

Recently while we were building a slave with a newer version of MySQL 5.1 from an InnoDB Hot backup an error occurred The problem is, in MySQL 5.1, it is possible to log the slow query log and general log to tables in the mysql schema. These tables are created by default as CSV tables for performance reasons, even if MySQL is set not to log to tables. CSV tables, however, are not copied as part of the InnoDB Hot Backup process, creating this error. Here is the fix to get the slave working

Read More >

InnoDB Hot Backup Utility Bug

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.

Read More >