Posts by Gerry Narvaja
For very personal reasons that don’t belong in this article, I decided a few weeks ago that it’s time for me to move on. The year and a half that I worked for Pythian have been a wonderful experience, and this is article is my tribute to this great company.
The title of the Launchpad page already reflects the change. What remains to be done is: a) change the name of the Perl script and documentation; and b) change the Launchpad URL. It is likely that I will change the name of the script when I release version 1.x (see below). I’m not sure of all the implications in Bazaar regarding the URL change, so that task will have to wait for now. Now a little more info on the status of the project.
This week the Log Buffer is a little more challenging for two reasons: a) Oracle Open World 2009 and b) the controversy around Monty Widenius’ opposition to Oracle owning MySQL due to the Sun acquisition, so let’s go straight to the articles.
What Was Going On Around 2:30pm? This is a question a customer asked us. To answer it we ran MySAR for a few days and queried the results for analysis. Looking at the data, we determined that the number of INSERT operations was significantly higher than any other, so we queried for the Com_insert status values. Com_insert is a counter that accumulates the number of INSERTs issued since the last server start (or since the last FLUSH STATUS command). For details on the variables available check Chapter 1. mysqld Options/Variables Reference.
One day, while looking into slave lag problem, the idea of MySAR popped into my head and a few hours later I was using its first incarnation. I was able to relate the server’s I/O activity peaks with these lags and in turn, discovered that it was caused by a great number of INSERT statements coming in in waves. It was an encouraging outcome for what was nothing more than a proof of concept.
Welcome to the 161st edition of Log Buffer, the weekly review of database blogs … and the first one under my penmanship.
Implementing SphinxSE into MySQL proved to be easier than it seemed in the beginning, although it took some time to compile and install everything. With a creative use of views, it could potentially be implemented right away in legacy applications, offering numerous advantages.
I just filed a very annoying bug when trying to compile with plugin engines using the 5.1.xx source tarball. I am trying to test SphinxSE as a plugin instead of getting it statically linked and came across an annoying bug. When using the configure –with-plugins option only once, the engine is statically linked. When using it twice, the first engine is created as a plugin, and the 2nd one is linked statically. Here are a couple of examples..
Lenz Grimmer recently wrote two blogs about password security on MySQL. Both are worth reading in detail. You’ll find them in Basic MySQL Security: Providing passwords on the command line and More on MySQL password security. Although I wrote a comment on the latter one, there is one point I thought was worth its own blog. Here we go…
If you review the recent years of Oracle’s history, you’ll see that its purchase of Sun makes perfect sense. Oracle has tried to get in the OS business (Oracle Ubreakable Linux), the hardware business with their different partnerships (e.g.: Hewlett Packard Partner Relationship), and even into the MySQL business back when they bought InnoBase (Oracle and Innobase).