Posts by Nicklas Westerlund
In this second MySQL User Group meeting, we’ll again focus on general best practices and free discussions, in order to share our knowledge as much as we can. The last meeting was in Mellieha and it was a success — we had a good turnout and some very interesting discussions. Darren, one of our members, blogged about our meeting and so did I in one of my previous posts. If you’d like to learn more about MySQL, or if you’re a DBA (doesn’t matter which level) I encourage you to email us (and sign up to our mailing list) at malta (at) ug.mysql.org. Or subscribe here. You can also, as always, email me directly at: westerlund (at) pythian.com
So, you have a binlog. You want to find out something specific that happened inside of it. What to do? mysqlbinlog has some neat features, which I thought we would look at here. I should first explain what mysqlbinlog really is. It is a tool that lets you analyze and view the binlogs/relaylogs from mysql, which are stored in binary format. This tool converts them to plaintext, so that they’re human-readable. For the first tip, let’s start with the –read-from-remote-server option, which allows you to examine a binlog on a master server in order, perhaps, to dump it onto your slave and compare master/slave logs for potential problems*.
After I moved back to Europe and Malta in order to set up our operations here, I was approached by a old friend of mine who wanted to know how to add a UNIQUE constraint and remove duplicates on a table, while keeping the newest records. He had been trying with ALTER TABLE but ran into problems as the older values were taken. To help him out, I first solved it based on his original idea, and then figured I would post a small note about the solution here.
So, the Malta MySQL User Group has had its first ever meet-up today, and it was a success! he evening proceeded with a introduction of ourselves, our interest in MySQL, and mainly talk about weird bugs that we had encountered during our careers. Oh, we also discussed Kickfire a bit, and it does indeed sound like a very interesting product, which I’d love to try out one day. Overall, I am very satisfied with this meeting and the turnout.
In this article, I will be looking at are online tools*, rather than the other (very useful) tools that are offline–such as myisamchk or setting innodb_force_recovery and starting up the server–both of which can sometimes save our skins. I’ll cover offline methods in another post, as they are outside of the scope for this post.
That’s right. MySQL now has a user group in Paradise. I am always looking into connecting with other MySQL professionals, to share the laughs and tears, and to enjoy what we love working with every day, MySQL. I have always wanted to bring us all together, and I thought that this would have a good chance of doing so.We will be having our first meeting in Mellieha, and please RSVP to me personally via email, westerlund (at) pythian.com if you want to attend.
So, how does one gather statistics on indexes? With InnoDB it’s one thing, with MyISAM it’s another thing. This post however, will focus on MyISAM. There are various ways, each having their own drawbacks and positive sides.
‘ve joined Pythian and thought I would present myself and give my initial opinions on Pythian as a employer. So far, I really enjoy everything that Pythian has, excellent co-workers, great spirits, nice work environment and fun challenges. Plus this will be my first time ever in Canada, so that’s something I will show too, I just hope it’s not that cold during July.