Today we glad to announce release 1.0.3-4 of our XtraDB storage engine.

Here is a list of enhancements in this release:

• Move to MySQL 5.1.33
• Move to InnoDB plugin 1.0.3
• more reliable replication, innodb_overwrite_relay_log_info patch now included in the release
• fix assertions for …

I've started using Xtrabackup to backup MySQL on my MacBook. Here's an example of a quick backup and restore:

1. Download the latest .tar.gz from Percona:

$ cd /tmp
$ wget http://www.percona.com/mysql/xtrabackup/0.5/xtrabackup-0.5-macos.x86_64.tar.gz
$ tar -xzf xtrabackup-*-macos.x86_64.tar.gz
$ cd xtrabackup*

2. This directory should contain innobackupex-1.5.1 and xtrabackup. You need to install these into a directory that appears in your $PATH. In my case, I am going to group it install it where my MySQL binaries are located (/usr/local/mysql/bin):

$ ls
innobackupex-1.5.1 xtrabackup
$ cp * /usr/local/mysql/bin/

3. Create a directory where you want your backup to go. In …

I've started using Xtrabackup to backup MySQL on my MacBook. Here's an example of a quick backup and restore:

1. Download the latest .tar.gz from Percona:

$ cd /tmp
$ wget http://www.percona.com/mysql/xtrabackup/0.5/xtrabackup-0.5-macos.x86_64.tar.gz
$ tar -xzf xtrabackup-*-macos.x86_64.tar.gz
$ cd xtrabackup*

2. This directory should contain innobackupex-1.5.1 and xtrabackup. You need to install these into a directory that appears in your $PATH. In my case, I am going to group it install it where my MySQL binaries are located (/usr/local/mysql/bin):

$ ls
innobackupex-1.5.1 xtrabackup
$ cp * /usr/local/mysql/bin/

3. Create a directory where you want your backup to go. In …

What’s going on at your favorite open-source database developer mailing list? Non-scientific memory of what I’ve been seeing lately:

• The Drizzle list is talking about test coverage and completeness, and schedulers.
• The MySQL internals list has recently been dominated with talk about coding standards.
• The PostgreSQL hackers list is talking about a ton of stuff. I don’t even try to keep up.
• The Percona launchpad list is talking about bugs, xtrabackup, and more bugs and patches for them. There’s also a Percona Google Group …

Percona presented two talks at PHP Quebec last week - one on A Tour of MySQL High Availability, and another on Performance Tuning MySQL. There was a great reaction to showcasing some of the quick-wins that can be found by using the Percona patches. Unfortunately, the one thing that I forgot to mention in the slides is that the patches are Open Source and free to use.

Entry posted by morgan | 4 comments

Add to: | …

We had too many requests for deb builds of Percona releases so I could not ignore that and added scripts to build binaries on our Ubuntu 8.10 box. It's going to be only 64bit releases (32bit is dead, isn't it?), and I tested binaries on Debian Lenny system and it seems working fine.

So I prepared binaries for our Build13 (which I actually did not announce to not spam PlanetMySQL a lot, I will figure out another channel for announcements), and you can get it there http://www.percona.com/mysql/5.0.77-b13/deb/, and your feedback is welcome!

As for changes for Build13 it contains InnoDB Data Dictionary restriction patch, which I mentioned before (http://www.mysqlperformanceblog.com/2009/02/11/limiting-innodb-data-dictionary/).

Speaking of deb …

Today we announce release 1.0.2-3 of our XtraDB storage engine.

Here is a list of enhancements:

• Move to MySQL 5.1.31
• Scalability fix — ability to use several rollback segments

Increasing the number of rseg may be helpful for CPU scale of write-intentional workloads. See benchmark results.

I just returned from a MySQL Federal Migration Boot Camp, jointly presented by Carahsoft and Sun/MySQL. It was a half-day seminar on the topic of migrating applications to MySQL, targeted to the US Government sector. Specifically, most of the audience seemed to be running Oracle, though there were some users of other systems (Microsoft SQL Server, Sybase, Informix, etc).

Ronald Bradford presented the whole thing. I thought he did a great job giving a fair and balanced look at topics such as what types of applications are good candidates for migration, what gotchas you might encounter, etc. I’m sure someone looking at migrating in earnest would benefit from a whole day’s discussion (or a more focused engagement with a consultant), but I thought it was a great way to help people figure out whether …

I have a Google Alert on “percona”. (And many other things — great way to keep tabs on competitors, what people are saying about you, etc.)

I’ve been seeing increasing amounts of this type of thing:

MySQL server version: 5.0.67-percona-3 CATEGORY QUERY: SELECT wp_term_taxonomy.count as ‘count’, wp_terms.term_id, wp_terms.name, wp_terms.slug, wp_term_taxonomy.parent, wp_term_taxonomy.description FROM wp_terms, wp_term_taxonomy WHERE …

Go to the page in question (sorry, I won’t link it) and you don’t see “percona” anywhere on it. View the source and you do. It’s WordPress debugging output.

I’m glad to see the anecdotal evidence of more and more active use of the Percona server builds, but at the same time, it’s kind of like finding out that your best friend made it onto the Jerry Springer Show. Sometimes I think …

Percona is hiring. We've added several experts recently and we're growing at a fast but sustainable pace. The demand for our services is strong, and we have openings for more experts in the next couple of months.

Let me explain a little about what we're looking for at the moment. While we do have a career path for less experienced people, right now we are looking for people who are top-level, senior experts in LAMP/Open-Source performance and scalability. Most of our work involves MySQL (at least peripherally, usually centrally) but not all of it; and we are looking for a PostgreSQL expert as well as systems administration and operations skills. If you're also an expert in a related technology (e.g. Hadoop, popular cloud platforms, or some other component that you might expect to see at the Percona Performance Conference) we'd like to …