EmergencyEMERGENCY? Get 24/7 Help Now!

XtraDB storage engine release 1.0.3-6

 | July 20, 2009 |  Posted In: Percona Software

PREVIOUS POST
NEXT POST

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
  • 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:

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

PREVIOUS POST
NEXT POST
Aleksandr Kuzminsky

Aleksandr is a consultant and data recovery specialist. He is a former Percona employee.

6 Comments

  • 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!

Leave a Reply

 
 

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.

No, thank you. Please do not ask me again.