June 11, 2009

The feature I love in TokuDB

Posted by Vadim |

Playing with TokuDB updates I noticed in SHOW PROCESSLIST unsual for MySQL State.

CODE:
  1. mysql> show processlist;
  2. +----+------+-----------+--------+---------+------+---------------------------+-----------------------------+
  3. | Id | User | Host      | db     | Command | Time | State                     | Info                        |
  4. +----+------+-----------+--------+---------+------+---------------------------+-----------------------------+
  5. 3 | root | localhost | sbtest | Query   |   30 | Updated about 764000 rows | update sbtest set email=zip |
  6. ...
  7. mysql> show processlist;
  8. +----+------+-----------+--------+---------+------+----------------------------+-----------------------------+
  9. | Id | User | Host      | db     | Command | Time | State                      | Info                        |
  10. +----+------+-----------+--------+---------+------+----------------------------+-----------------------------+
  11. 3 | root | localhost | sbtest | Query   |   79 | Updated about 1900000 rows | update sbtest set email=zip |
  12. ...

(Do not look in stupid UPDATE query, it's just for testing :) )

So looking in SHOW PROCESSLIST you can see progress of query execution.

I would want to see it in standard MySQL and InnoDB more than all these triggers and stored routines! Probably will implement this in XtraDB.

5.0.77 / 5.0.82 -build16 Percona binaries

Posted by Aleksandr Kuzminsky |

Dear community,

We are pleased to announce the build16 of MySQL server® with Percona patches.

Since the build13 there was a couple of customer specific releases, which explains cutover in numbering and a pause between the builds. Also we prepared build for both 5.0.77 and 5.0.82 versions.

Since that time new patches were added:

  • profiling_slow.patch
  • This patch adds information from SHOW PROFILE to query information in slow.log output.
    profiling_server. This variable ( ON / OFF ) enables profiling of all queries (in all connections).
    profiling_use_getrusage. This variable ( ON / OFF ) enables usage of getrusage function in profiling.
    Be careful, enabling profiling_server may cause performance degradation, especially with profiling_use_getrusage.

  • innodb_extra_rseg.patch
  • innodb_extra_rsegments. The number of extra user rollback segments created when new db is created.
    New information_schema table innodb_rseg shows information about all rollback segments

  • innodb_thread_concurrency_timer_based.patch

This patch provides the configuration variable backport from MySQL 5.4.

Fixed bugs:

You can download binaries (RPMS x86_64) and sources with patches here
http://www.percona.com/mysql/5.0.77-b16/
http://www.percona.com/mysql/5.0.82-b16/

The Percona patches live on Launchpad : https://launchpad.net/percona-patches and you can report bug to Launchpad bug system:
https://launchpad.net/percona-patches/+filebug. The documentation is available on our Wiki

For general questions use our Pecona-discussions group, and for development question Percona-dev group.

For support, commercial and sponsorship inquiries contact Percona