April 28, 2009

XtraDB storage engine release 1.0.3-5

Posted by Evgeniy Stepchenko |

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

Here is a list of enhancements in this release:

Percona XtraDB 1.0.3-5 available in source and several binary packages.

XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.

Posted by Evgeniy Stepchenko @ 8:42 am :: xtradb  
Print This Post Print This Post book mark XtraDB storage engine release 1.0.3-5 in del.icio.usdel.icio.us :: submit XtraDB storage engine release 1.0.3-5 to digg.comdigg  
Comment RSS  
Related posts: :XtraDB storage engine release 1.0.4-8::XtraDB storage engine release 1.0.3-7::XtraDB has been commited to MariaDB:
 

8 Comments »

  1. 1. Mark Callaghan

    Percona rocks! I am thrilled that you switched to the Google rw-lock patch because that is in the InnoDB plugin and you can add value elsewhere. Is XtraDB derived from the InnoDB plugin?

    Comment :: April 28, 2009 @ 8:57 am

  2. 2. Didier Spezia

    If I understand correctly the versioning scheme, XtraDB X.Y.Z-n is derived from InnoDB plugin X.Y.Z.

    Comment :: April 28, 2009 @ 9:42 am

  3. 3. Vadim

    Mark,

    XtraDB is derived from InnoDB-plugin

    Comment :: April 28, 2009 @ 10:14 am

  4. 4. Vadim

    Didier,

    Yes, we keep in version the version of InnoDB-plugin it was derived from.

    Comment :: April 28, 2009 @ 10:14 am

  5. 5. Jacques

    BTW, as far as I can tell syslog logging is broken in 5.1.34 (upstream); because of changes in the my_which function in the mysqld_safe driver script. Not very happy with upstream’s QA in this case…

    Anyway, revert this:

    http://bazaar.launchpad.net/~mysql/mysql-server/mysql-5.1/revision/2806.38.2

    or quick fix:

    /usr/bin/mysqld_safe

    change line 70 to:

    for dir in $PATH

    instead of

    for dir in “$PATH”

    Comment :: April 29, 2009 @ 9:44 pm

  6. 6. Fuji

    First of all – awesome work is being done here and have used this blog multiple times to optimize my servers. Thanks a lot guys

    1) Do you happen to have comparisions of xtraDB vs MYISAM for read speeds?

    2) For some reason I am having the darnest time getting documentation of XtraDB installtion etc. the launchpad sends me here and the wiki doesnt seem to have much

    Comment :: June 23, 2009 @ 11:35 am

  7. 7. Eyal Sorek

    Hi,

    I downloaded mysql 5.1.34 rpm’s 64 bit for redhat 5 with XtraDB 1.0.3-5 and installed them and it work nice and smooth.
    I tried to build from the source RPM equivalent 32bit RPM’s and failed.
    Are there any equivalent 32bit RPM’s for Redhat 5 ?
    Any other suggestions how to build with rpmbuild equivalent 32bit RPM’s for Redhat 5 ?

    Thanks,
    Eyal Sorek

    Comment :: July 14, 2009 @ 9:45 am

  8. 8. Eyal

    Hi,

    Another question – Is this combination of mysql 5.1.34 redhat 5 with XtraDB 1.0.3-5 is GA ?
    Are there known production installation using it in RH 64 bit ?

    Thanks,
    Eyal

    Comment :: July 14, 2009 @ 1:31 pm

 

Subscribe without commenting

Trackbacks/Pingbacks