Dear community,
Today we are pleased to announce release 6 of XtraDB – the result of 2 months hard work.
The release includes following new features:
- MySQL 5.1.36 as a base release
- New patch
1innodb_recovery_patches.patch
- Experimental adaptive checkpoint method estimate
- innodb_stats – the implementation of the fix forMySQL Bug#30423
- expand-import Support of import InnoDB / XtraDB tables from another server
- split-bufpool-mutex-3 New patch to split buffer pool mutex
- g-style-io-thread Google’s fixes to InnoDB IO threads
- dict-size-limit Limit of internal data dictionary
Fixed bugs:
- MySQL Bugs: #39793: Foreign keys not constructed when column has a ‘#’ in a comment or default value
- Bug #395784 in Percona-XtraDB: “main.innodb_xtradb_bug317074 internal check fails on 5.1.36â€
- Bug #395778 in Percona-XtraDB: “main.innodb-analyze internal check failed on 5.1.36â€
- Bug #391189 in Percona-XtraDB: “main.innodb_bug36172 mysq test fails with innodb_stat.patch appliedâ€
- Bug #388884 in Percona-XtraDB: “patching fails on 5.1.35â€
The builds for RedHat4,5 and Debian are located on https://www.percona.com/mysql/xtradb/5.1.36-6/
The latest source code of XtraDB, including development branch you can find on LaunchPAD.
Please report any bugs found on Bugs in Percona XtraDB Storage Engine for MySQL.
For general questions use our Pecona-discussions group, and for development question Percona-dev group.
For support, commercial and sponsorship inquiries contact Percona
About the Author
Aleksandr KuzminskyAleksandr is a consultant and data recovery specialist. He is a former Percona employee.
Hi Aleksander,
These packages still have the dependency failure/conflict I filed here: https://bugs.launchpad.net/percona-patches/+bug/386054
It somewhat defeats the purpose of having a CentOS/RHEL package if the package is going to cause a dependency conflict with things in base.
Any idea when these will be published at https://www.percona.com/docs/wiki/percona-xtradb:info:xtradb_downloads ?
Thanks!!!
CJ
Just tried the expand-import feature. It worked as in I can issue queries against the newly imported table and the data appears to be correct, but my log is filled with tons of errors like:
090723 14:39:50 InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 13016:7746928, should be 13364:7746928!
Billy,
can you post all your steps to bug report on Launchpad ? Thanks!
Is XtraDB usable as MySQL Cluster data node?
And if the engine is not usable (but ndb), could there be some general performance gains, i.e. caused by some of the (kernel) patches?
A similar question has been asked on Stack Overflow, maybe you guys can give a usable answer:
http://stackoverflow.com/questions/399415/mysql-cluster-with-mysql-innodb-persistent-store