0.7.0 is (finally) around the corner. We are only pushing some last minute build-fixes, but otherwise we are done.

If you want to help us getting a good 0.7.0 release out, please test the snapshot RPMs we did build with the help of OpenSuSEs build-service.

At http://software.opensuse.org/search?baseproject=ALL&p=1&q=mysql-proxy-snapshot you will always find the latest snaptshot packages that we build from the latest launchpad code (everything > r640 is current). We have native binaries for Fedora 9 and 10 and OpenSuSE 11.0 and 11.1 right now.

If everything goes well, we should have a 0.7.0 release …

We added some new features to our backup tool, namely:

• Now we can handle log file taken during backup with size exceeding 4GB, it may happen if backup takes too long and you have a lot of updates on InnoDB tables
• Progress meter during recovery step, now you can see what percentage of log file was handled

PLAIN TEXT CODE:

1. InnoDB: Doing recovery: scanned up to log sequence number 1316 3688693248 (34 %)
2. ...
3. InnoDB: Doing recovery: scanned up to log sequence number 1316 4113366528 (68 %)
4. InnoDB: Doing recovery: scanned up to log sequence number 1316 4117548544 (68 %)

Also we did extensive testing and fixed bugs, so now we consider current state as feature complete and with beta-release stability.

You can …

This latest change also means that MySQL Sandbox will be available through the CPAN (Comprehensive Perl Archive Network, for the uninitiated).
The next step will be to include this package in Linux distros (Ubuntu, …

I released the second beta of MySQLdb-1.2.3 over the weekend. So far I've gotten a fair number of downloads but not a lot of feedback. I did find out though what small tweaking is required to build on Windows. It's also in the Python Package Index, so if you can also install using easy_install MySQL-python. Once I make the final release of 1.2.3, I'll put up more eggs for fringe operating systems (Mac OS X, Windows).

This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …

This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …

This task involves QA engineers, Build engineers, the Maintenance team, with help and cooperation from …

We are coming with next version of xtrabackup - online backup solution for MySQL 5.0 / 5.1 and InnoDB standard version, plugin modification and XtraDB. We still consider it as alpha version, though it shows perfect stable results in our tests.

Let me address two often asked question about xtrabackup:
1) Does it work only with XtraDB or with InnoDB also ?
A: xtrabackup is designed to work with standard version of InnoDB in MySQL 5.0. MySQL 5.1 + standard InnoDB / InnoDB-plugin also are supported. It can fully work as drop-in replacement of innodbackup tool and InnoDB Hot Backup online backup.

2) Do we need to run patched MySQL, because the build instruction mentions the patch for MySQL ?
A: xtrabackup can be run with any version of MySQL: community release, enterprise release, percona builds, ourdelta distributions. You do not need to patch …

Our MySQL integration code (wsrep: https://launchpad.net/codership-mysql) was lagging behind from MySQL 5.1 release cycle and we needed to catch up eventually. MySQL/Galera Demo-1 was built on top of MySQL 5.1.30 and since then both 5.1.31 and 5.1.32 have been published.

read more

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 …