Posts Categorized: MySQL
f you are using InnoDB Hot Backup and a recent version of mysqld (at least 5.0.67 or higher, including 5.1.30, though it may be later versions), your backup will run fine and output OK! at the end, as it should. Except for one thing. The binary log file and position do not appear in their rightful place. Here’s a snippet of the output from the backup…The bug is an artifact of the eventual deprecation of TYPE in favor of ENGINE. There’s no reason for ibbackup to continue to use TYPE; while the product works well, it is much more expensive than it warrants.
Last week, I was at the NetApp office in North Sydney for the presentation on NetApp SnapManager for Oracle. It was good opportunity to learn more about NetApp snapshots while working on a project for one of our clients in Sydney. It was an especially interesting topic as I have some experience using Veritas Checkpoints. I learned that NetApp can provide access to the same LUNs via either Fiber-Channel (FC) or iSCSI. And this is when the interesting argument surfaced.
Welcome to the 134th edition of Log Buffer, the weekly review of database blogs. There’s no time to lose, so let’s begin—with MySQL.
At the January 2009 Boston User Group I presented a session on the new partitioning feature in MySQL 5.1. I go through how to define partitions, how partitioning makes queries faster, the different types of partitioning and when to use each type, and the restrictions and limitations of partitioning. The slides and video are available here.
I had the chance to review the new Query Analyzer program from Sun over the last few days. I am very interested in how it performs as I have previously not had a chance to see the program in action (or the Enterprise Monitor program either for that matter). So, before getting into what the Query Analyzer can (and cannot) do let’s look at what Sun says it does.
Hello and welcome to the 133rd edition of Log Buffer, the weekly review of database blogs.
One very helpful use of the technique Sheeri described in Remote connections without leaving the mysql shell is making sure that replication is working properly. According to the MySQL Reference Manual’s section on SHOW SLAVE STATUS Syntax, it shows information corresponding to the slave thread in the slave server. When replication is broken, however, or not working properly due to network issues between master and slave, this information may not be accurate. This has improved over recent releases, but it’s still not perfect. The question, then, is: how to be 100% sure (or as close as you can get to 100%) that replication is running fine? The answer, as offered by Sheeri: use CONNECT.
So, a colleague ran into issues booking the Santa Clara Hyatt Regency Hotel—apparently there were no rooms with 2 double beds left for the MySQL 2009 Conference and Expo.
I realized tonight exactly why MySQL’s default behavior of silent truncation bothers me. It reminds me of people who use a ticketing system and close every ticket as soon as they are done working on the issue instead of actually asking the other party if they are satisfied, because closing more tickets make it look like they’re doing more work.
You probably know that mysql -h host_or_ip can connect you to a remote host. But did you know that you can change the host you are connected to from within mysql? The undocumented (as far as I can tell, in the MySQL manual and in the “help” on the mysql command line) CONNECT statement can help.