5.0.77 / 5.0.82 -build16 Percona binaries

PREVIOUS POST
NEXT POST

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

PREVIOUS POST
NEXT POST

Comments

  1. Mark says

    Thanks for sticking with the 5.0 release of MySQL! I’m working on switching to 5.1, but it takes time to test and validate everything.

  2. Pawel says

    5.0.82 debian server packages are broken, they do not contain /usr/share/mysql directory structure.
    Please change maintainer field, as this package is maintained by percona.
    What happened with highperf packages?

    Anyway, good work!

  3. says

    Building MySQL-percona-b16-5.0.82-0.rhel5.src.rpm fails because userstatv2.patch can’t be applied cleanly:

    patching file sql/mysqld.cc
    Hunk #10 FAILED at 5081.
    Hunk #11 succeeded at 6537 (offset -12 lines).
    1 out of 11 hunks FAILED — saving rejects to file sql/mysqld.c

    Here’s hunk #10:
    @@ -5056,6 +5081,7 @@
    OPT_PROFILING_USE_GETRUSAGE,
    OPT_SLOW_LOG,
    OPT_SLOW_QUERY_LOG_FILE,
    + OPT_USERSTAT_RUNNING,
    OPT_USE_GLOBAL_LONG_QUERY_TIME,
    OPT_INNODB_ROLLBACK_ON_TIMEOUT,
    OPT_SECURE_FILE_PRIV,

    And there is no OPT_PROFILING_USE_GETRUSAGE in mysqld.cc, just OPT_PROFILING.

    Next patch which fails is:

    Patch #12 (innodb_io_pattern.patch):
    + /bin/cat /home/foo/rpmbuild/SOURCES/innodb_io_pattern.patch
    + /usr/bin/patch -s -p1 –fuzz=0
    1 out of 1 hunk FAILED — saving rejects to file innobase/include/srv0srv.h.rej

    srv0srv.h.rej:
    ***************
    *** 145,150 ****
    extern ulint srv_flush_neighbor_pages;
    extern uint srv_read_ahead;
    extern ulint srv_adaptive_checkpoint;
    /*——————————————-*/

    extern ulint srv_n_rows_inserted;
    — 145,155 —-
    extern ulint srv_flush_neighbor_pages;
    extern uint srv_read_ahead;
    extern ulint srv_adaptive_checkpoint;
    +
    + extern volatile ibool srv_io_pattern;
    + extern ulong srv_io_pattern_trace;
    + extern ulong srv_io_pattern_trace_running;
    + extern ulong srv_io_pattern_size_limit;
    /*——————————————-*/

    extern ulint srv_n_rows_inserted;

    And at that point I gave up.

Leave a Reply

Your email address will not be published. Required fields are marked *