circle-info
Webinar | The Great Database Exodus: Navigating Strategic Risk in the Post-Oracle MySQL Era
Register Nowarrow-up-right
search
Download MariaDBContact Us

MariaDB 5.5.20 Changelog

The most recent release in the MariaDB 5.5 series is:MariaDB 5.5.68 Download Nowarrow-up-right

Downloadarrow-up-right |Release Notes |Changelog |[Overview of 5.5arrow-up-right

Release date: 26 Feb 2012

For the highlights of this release, see the release notes.

The revision number links will take you to the revision's page on Launchpad. On Launchpad you can view more details of the revision and view diffs of the code modified in that revision.

  • Revision #3279arrow-up-right [merge] Fri 2012-02-24 14:37:00 +0100

    • 5.3 merge

  • Revision #3278arrow-up-right Thu 2012-02-23 15:31:24 +0100

    • disable safemalloc for valgrind builds.

    • always try to use valgrind headers in debug builds.

    • define HAVE_valgrind for --with-valgrind

    • fix valgrind check in my_valgrind.h

  • Revision #3277arrow-up-right [merge] Wed 2012-02-22 12:21:54 +0400

  • Revision #3276arrow-up-right [merge] Tue 2012-02-21 20:51:56 +0100

    • 5.3 merge

    • Revision #2502.513.51arrow-up-right Mon 2012-02-20 21:30:23 +0100

      • fix for "relocation R_X86_64_PC32 against `handler_index_cond_check' can not be used when making a shared object; recompile with -fPIC"

      • don't use visibility=hidden for external functions

    • Revision #2502.513.50arrow-up-right [merge] Tue 2012-02-21 09:43:36 +0200

    • Revision #2502.513.49arrow-up-right Mon 2012-02-20 20:38:05 +0400

      • Bug #933412arrow-up-right: Server crashes in _mi_put_key_in_record on KILL QUERY with ICP, STRAIGHT_JOIN

        • In mi_rkey(), do correct handling of case where mi_yield_and_check_if_killed() detects that the thread was killed (all other similar functions in MyISAM/Aria have slightly different code and do not have this problem).

        • Also fixed assignment in DBUG_ASSERT

        • this is 2nd variant of the fix:

          • make .result file smaller

          • run KILLable statements in a separate connection, otherwise we could end up trying to KILL the final "DROP TABLE" statement

    • Revision #2502.513.48arrow-up-right [merge] Mon 2012-02-20 15:34:50 +0400

      • Merge

      • Revision #2502.526.1arrow-up-right Mon 2012-02-20 15:30:54 +0400

        • Bug #933407arrow-up-right: Valgrind warnings in mark_as_null_row with materialization+semijoin, STRAIGHT_JOIN, impossible WHERE

        • In return_zero_rows(), don't call mark_as_null_row() for semi-join materialized tables, because

          1. they may have been already freed, and

          2. there is no real need to call mark_as_null_row() for them

    • Revision #2502.513.47arrow-up-right Sat 2012-02-18 19:11:57 -0800

      • Fixed Bug #934348arrow-up-right

      • This bug is the result of an incomplete/inconsistent change introduced into 5.3 code when the cond_equal parameter were added to the function optimize_cond.

      • The change was made during a merge from 5.2 in October 2010. The bug could affect only queries with HAVING.

    • Revision #2502.513.46arrow-up-right Sat 2012-02-18 16:06:38 -0800

      • Fixed Bug #934342arrow-up-right.

      • An outer join query with a semi-join subquery could return a wrong result if the optimizer chose to materialize the subquery.

      • It happened because when substituting for the best field into a ref item used to build access keys not all COND_EQUAL objects that could be employed at substitution were checked.

      • Also refined some code in the function check_join_cache_usage to make it safer.

    • Revision #2502.513.45arrow-up-right Fri 2012-02-17 13:27:41 +0100

      • Remove engine-specific (but identical) icp callbacks. create one reusable common icp callback in the handler.cc.

      • It can also increment status counters, without making the engine dependent on the exact THD layout (that is different in embedded).

    • Revision #2502.513.44arrow-up-right Thu 2012-02-16 20:13:28 -0800

      • Fixed LP bug #928352.

      • This bug led to wrong values of the use_count fields in some SEL_ARG trees that triggered complains on the server side when executing the test case for LP bug 800184 if a debug build of the server was used.

      • This was the result of the incomplete fix for bug 800184.

      • To complete it the following corrections had to be made:

        • the copy constructor for SEL_TREE must call the new function incr_refs_all() instead of the function incr_refs(), because references to next key parts from any SEL_ARG tree belonging to the list of the first key part has to be adjusted.

        • the method and_sel_tree of the class SEL_IMERGE must use the copy constructor of the SEL_TREE class to make a copy of its second argument before it ANDs it with any SEL_TREE tree from the processed SEL_IMERGE object.

    • Revision #2502.513.43arrow-up-right Thu 2012-02-16 20:15:57 +0400

      • Backport of:

        • timestamp: Thu 2011-12-01 15:12:10 +0100

        • Fix for Bug#13430436 PERFORMANCE DEGRADATION IN SYSBENCH ON INNODB DUE TO ICP

        • When running sysbench on InnoDB there is a performance degradation due to index condition pushdown (ICP). Several of the queries in sysbench have a WHERE condition that the optimizer uses for executing these queries as range scans. The upper and lower limit of the range scan will ensure that the WHERE condition is fulfilled. Still, the WHERE condition is part of the queries' condition and if ICP is enabled the condition will be pushed down to InnoDB as an index condition.

        • Due to the range scan's upper and lower limits ensure that the WHERE condition is fulfilled, the pushed index condition will not filter out any records. As a result the use of ICP for these queries results in a performance overhead for sysbench. This overhead comes from using resources for determining the part of the condition that can be pushed down to InnoDB and overhead in InnoDB for executing the pushed index condition.

        • With the default configuration for sysbench the range scans will use the primary key. This is a clustered index in InnoDB. Using ICP on a clustered index provides the lowest performance benefit since the entire record is part of the clustered index and in InnoDB it has the highest relative overhead for executing the pushed index condition.

        • The fix for removing the overhead ICP introduces when running sysbench is to disable use of ICP when the index used by the query is a clustered index.

        • When WL#6061arrow-up-right is implemented this change should be re-evaluated.

    • Revision #2502.513.42arrow-up-right Thu 2012-02-16 18:56:10 +0400

      • Added comments

    • Revision #2502.513.41arrow-up-right Thu 2012-02-16 08:49:10 +0200

  • Revision #3275arrow-up-right Fri 2012-02-17 12:19:38 +0100

    • fix the include guards and add missing gplv2 headers

  • Revision #3274arrow-up-right Tue 2012-02-21 01:08:22 +0400

    • Bug #919878arrow-up-right: Assertion `!eliminated_tables...

      • In MySQL 5.5, print_join() was re-worked to print "FROM dual" when all tables are constant. This change didn't work together with table elimination.

  • Revision #3273arrow-up-right Mon 2012-02-20 22:25:44 +0100

    • Workaround buggy Linux dtrace - it fails on fedora if CC is set to 'ccache gcc'

  • Revision #3272arrow-up-right [merge] Wed 2012-02-15 19:11:16 +0100

  • Revision #3271arrow-up-right Wed 2012-02-15 17:09:56 +0100

    • Fix wrong type causing build failure on windows.

  • Revision #3270arrow-up-right Wed 2012-02-15 16:38:38 +0100

    • Fix wrong type causing build failure on windows.

  • Revision #3269arrow-up-right [merge] Wed 2012-02-15 15:37:38 +0100

    • Merge XtraDB from Percona-Server-5.5.20-24.1 into MariaDB 5.5.

    • Revision #0.12.52arrow-up-right Wed 2012-02-15 11:49:53 +0100

      • Updated with XtraDB from Percona Server 5.5.20-24.1

      • Files copied from Percona-Server-5.5.20-rel24.1.tar.gz source tarball.

  • Revision #3268arrow-up-right [merge] Tue 2012-02-14 16:06:41 +0100

  • Revision #3267arrow-up-right Tue 2012-02-14 13:24:03 +0100

    • Fix wrong error code in the test case.

    • The replication slave sets first error 1913 and immediately after error

  1. Thus it is possible, but unlikely, to get 1913. The original test seems to realise this, but uses an invalid error code - my guess is that this was a temporary code used in a feature tree, which was then forgotten to be fixed when merged to main. The removed "1923" is something committed by mistake during tests.

circle-info

Be notified of new MariaDB Server releases automatically by subscribingarrow-up-right to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

This page is licensed: CC BY-SA / Gnu FDL

spinner
PreviousMariaDB 5.5.21 ChangelogNextChangelogs - MariaDB 5.3 Series

Last updated

Was this helpful?