MySQL releases with Percona patchsets
Percona has a strong team of MySQL developers and consultants on board, so we decided to prepare MySQL releases with our patches and third-party patches which we think are very useful. We actually use these internally and for our customers.
Current releases include:
- microslow patch (enables microsecond resolution in slow logs)
- execution plan (show info about query execution in slow log)
- InnoDB statistic (show extended InnoDB usage during query execution in slow log)
- Google’s patches with user statistics, and statistics about tables and indexes usage
You can find more info about some of our patches here:
http://www.mysqlperformanceblog.com/2008/04/20/updated-msl-microslow-patch-installation-walk-through/
Some features were sponsored by customers and we are allowed to publish them under GPL and some we developed for internal needs.
We prepared 5.0.62 release (based on MySQL Enterprise 5.0.62 source, taken from http://mirror.provenscaling.com/mysql/enterprise/source/5.0/) and 5.1.26-rc release, and they are currently available only as source .tar.gz, but we will provide public access to our YUM repository with binaries, RedHat/CentOS and Suse RPMS / SRPMS when they’re available. Here are links to the source releases:
mysql-5.0.62-percona.tar.bz2 md5:0d8a37e09eca93cde6170866293a82ff
mysql-5.1.26-percona.tar.bz2 md5:0574b38755786a97bc476058051cbe82
You can find the individual patches here:
http://www.mysqlperformanceblog.com/mysql-patches/
Besides standard 5.1, we are going to make releases with the InnoDB plugin version compiled in (not as a plugin), as the current system with independent InnoDB binaries does not seem handy for us.
We have couple of ideas what else we can develop and include in our releases, but also your comments are very welcome.
We are still investigating Launchpad features, there is our -percona branch, but it is outdated at this moment. Probably our next releases will be based on Launchpad branches, we still need to decide how it fits into our development model.
Disclaimer: Although we use tested releases as best as we can, and use them internally, we do not claim they are bug-free, and you should use them only if you know what you are doing.
del.icio.us
digg25 Comments
Have you considered putting your tree up on Launchpad?
Comment :: July 16, 2008 @ 10:09 pm
Thanks for this! It’s a nice to have access to a patchset that someone can vet far more thoroughly than I can.
Do you ever build deb/deb-src packages?
Comment :: July 16, 2008 @ 10:28 pm
Mark,
As I mentioned, we are looking into Launchpad, but our developers use mercurial queues to manage patches, so we think how we can use Launchpad.
Comment :: July 16, 2008 @ 10:41 pm
John,
We do not have debian servers, and debian also is rarely used by our customers, so we have no plans to build deb right now, but may reconsider that if there will be many requests for.
Comment :: July 16, 2008 @ 10:44 pm
Good stuff, I’ll certainly be looking at your builds, I’ll wait for the binaries. CentOS 5 64 bit for me.
Comment :: July 16, 2008 @ 11:31 pm
Hi,
I have created/modified some small packages myself, but mysql is too complex for me to do it.
I would also vote for Debian packages
Comment :: July 17, 2008 @ 1:08 am
“We have couple of ideas what else we can develop and include in our releases, but also your comments are very welcome.”
PBXT, Sphinx ?
Comment :: July 17, 2008 @ 1:09 am
Any plans for a windows binary?
Comment :: July 17, 2008 @ 1:45 am
Another vote for Debian packages
Comment :: July 17, 2008 @ 2:42 am
This is excellent news.
I’ll put in another vote for 64-bit RHEL/CentOS 5.
I understand that you can’t have every hardware platform and ever Distro/OS for testing available. For Debian, et all, maybe you can find someone willing to make the packages based on your source and ship them back in.
Comment :: July 17, 2008 @ 5:50 am
We do not plan Windows binaries at all unless we have serious requests for.
As for Debian probably we can cooperate with contributors. Our patches also will be available via hg queue so it will not be hard to extract them and prepare deb-src.
Comment :: July 17, 2008 @ 11:51 am
Excellent.
Comment :: July 17, 2008 @ 8:35 pm
Very interesting.
another vote for debian btw…
Comment :: July 18, 2008 @ 12:15 am
Nice!
.. and another Debian vote
Comment :: July 18, 2008 @ 6:43 am
This is excellent news and great for users who want performance critical features but don’t want to patch and build MySQL. SHOW USER_STATISTICS is my favorite patch so far, does this include it?
Comment :: July 18, 2008 @ 8:22 am
Mark,
Yes, it contains
SHOW USER_STATISTICS / INDEX_STATISTICS / TABLE_STATISTICS.
We are going to make this info available via INFORMATION_SCHEMA.
Comment :: July 18, 2008 @ 9:23 am
I am recompiling for CentOS 5.2, using centos.org specs files from mysql-5.0.45-7.el5.src. If everything goes well I will do it for 64-bit currently on 32-bit.
Comment :: July 18, 2008 @ 5:47 pm
I am SERIOUSLY requesting Windows binaries
You guys are great!
Comment :: July 21, 2008 @ 7:05 am
If guys want debian packages 5.1.26-rc with theses patches I can provide them.
Simple question : Is there any documentation about innodb_stat patch ? How do we use it ?
Comment :: July 23, 2008 @ 3:10 am
Thanks Cyril. Can’t wait to see the debian package
Comment :: July 23, 2008 @ 7:09 am
@Michael -> I don’t think they’re going to make windows binaries for free. If you do need windows binaries, call them and buy their commercial consulting service.
Comment :: July 23, 2008 @ 7:10 am
And yes, I vote for another Debian package
Comment :: July 23, 2008 @ 7:11 am
Debian package vote
Comment :: July 29, 2008 @ 2:43 am
Thx a million for this patched version. It makes it a lot easier to find the mysql turbo switch for your custom application.
Comment :: July 30, 2008 @ 1:25 am
Sweet…..
Consider this a debian vote.
Comment :: August 1, 2008 @ 8:34 pm