14-day MaxScale Trial: Explore the latest version of our advanced database proxy!
Start Trial
Download MariaDBContact Us

MariaDB 5.5.27 Changelog

The most recent release in the MariaDB 5.5 series is:MariaDB 5.5.68 Download Now

Download |Release Notes |Changelog |[Overview of 5.5

Release date: 07 Sep 2012

For the highlights of this release, see therelease 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 #3527 Thu 2012-09-06 10:08:09 +0200

    • MDEV-510 assert triggered by ./mtr --ps-protocol rpl_mdev382

    • The DELETE for emplicitly emptied MEMORY tables should be written directly to binlog.

  • Revision #3526 [merge] Thu 2012-09-06 00:14:33 +0300

    • merge 5.3->5.5

    • Revision #2502.567.18 Wed 2012-09-05 23:23:58 +0300

      • MDEV-486 Bug #1010116 fix.

      • Link view/derived table fields to a real table to check turning the table record to null row.

      • Item_direct_view_ref wrapper now checks if table is turned to null row.

    • Revision #2502.567.17 Fri 2012-08-31 19:50:45 +0500

      • Bug #1043845 st_distance() results are incorrect depending on variable order.

      • Autointersections of an object were treated as nodes, so the wrong result.

      • per-file comments:

        • mysql-test/r/gis.result

          • Bug #1043845 st_distance() results are incorrect depending on variable order.

          • test result updated.

        • mysql-test/t/gis.test

          • Bug #1043845 st_distance() results are incorrect depending on variable order.

          • test case added.

        • sql/item.cc

          • small fix to make compilers happy.

        • sql/item_geofunc.cc

          • Bug #1043845 st_distance() results are incorrect depending on variable order.

          • Skip intersection points when calculate distance.

  • Revision #3525 Wed 2012-09-05 13:15:05 +0200

    • sys_vars.expensive_subquery_limit_basic

  • Revision #3524 [merge] Wed 2012-09-05 13:14:37 +0200

    • XtraDB from Percona-Server-5.5.27-rel28.1

    • Revision #0.12.55 Wed 2012-09-05 10:44:23 +0200

      • Percona-Server-5.5.27-rel28.1

  • Revision #3523 Tue 2012-09-04 19:11:06 +0200

    • MDEV-481 Assertion `pins->pin[i] == 0' failed in _lf_pinbox_put_pins on concurrent OPTIMIZE TABLE and DML with Aria tables

    • A bug in the lock-free hash implementation!

    • when lsearch() has not found the key, the caller needs to unpin all the three pins, because lsearch() was using all the three.

  • Revision #3522 Tue 2012-09-04 12:12:28 +0200

    1. fix an old typo. A purgatory must be cleaned on every LF_PURGATORY_SIZE freeing, not every time.

    2. Increase purgatory size.

  • Revision #3521 Sun 2012-09-02 19:09:17 +0200

    • don't run mdev375.test for embedded server

  • Revision #3520 Sat 2012-09-01 00:23:30 +0200

    • remove the forgotten commented out piece of the old merge

  • Revision #3519 Fri 2012-08-31 16:48:02 +0200

    • fix the test to work with --lower-case-table-names=1

  • Revision #3518 [merge] Fri 2012-08-31 14:15:52 +0200

    • 5.3 merge

    • Revision #2502.567.16 Fri 2012-08-31 12:01:52 +0200

      • compilation warning

    • Revision #2502.567.15 Thu 2012-08-30 10:53:49 +0200

      • MDEV-381: fdatasync() does not correctly flush growing binlog file.

      • When we append data to the binlog file, we use fdatasync() to ensure the data gets to disk so that crash recovery can work.

      • Unfortunately there seems to be a bug in ext3/ext4 on linux, so that fdatasync() does not correctly sync all data when the size of a file is increased. This causes crash recovery to not work correctly (it loses transactions from the binlog).

      • As a work-around, use fsync() for the binlog, not fdatasync(). Since we are increasing the file size, (correct) fdatasync() will most likely not be faster than fsync() on any file system, and fsync() does work correctly on ext3/ext4. This avoids the need to try to detect if we are running on buggy ext3/ext4.

    • Revision #2502.567.14 Thu 2012-08-30 09:05:27 +0200

      • MDEV-437 Microseconds: In time functions precision is calculated modulo 256

      • store the precision in uint, not uint8

    • Revision #2502.567.13 Wed 2012-08-29 18:36:57 +0200

      • MDEV-438 Microseconds: Precision is ignored in CURRENT_TIMESTAMP(N) when it is given as a default column value

      • The syntax for specifying precision in the DEFAULT clause is unintentional and unsupported.

      • Don't allow it anymore.

    • Revision #2502.567.12 Wed 2012-08-29 17:55:59 +0200

      • MDEV-454 Addition of a time interval reduces the resulting value

        1. Field_newdate::get_date should refuse to return a date with zeros when TIME_NO_ZERO_IN_DATE is set, not when TIME_FUZZY_DATE is unset

        2. Item_func_to_days and Item_date_add_interval can only work with valid dates, no zeros allowed.

    • Revision #2502.567.11 Wed 2012-08-29 10:59:51 +0200

      • MDEV-456 An out-of-range datetime value (with a 5-digit year) can be created and cause troubles

      • fix Item_func_add_time::get_date() to generate valid dates.

      • Move the validity check inside get_date_from_daynr() instead of relying on callers

      • (5 that had it, and 2 that did not, but should've)

    • Revision #2502.567.10 Wed 2012-08-29 11:35:42 +0300

    • Revision #2502.567.9 Tue 2012-08-28 13:51:01 +0400

      • Fix bugs in BatchedKeyAccess that show up when working with a storage engine in HA_MRR_NO_ASSOCIATION mode.

      • (there is no testcase because we don't ship any such engines currently)

  • Revision #3517 Fri 2012-08-31 13:03:41 +0200

    • MDEV-414 Depending on indexes or execution plans, a warning on incorrect or out of range values in WHERE condition is sometimes produced and sometimes not

    • use the same method that disables warnings in all relevant places, remove redundant function

  • Revision #3516 Thu 2012-08-30 11:47:01 +0200

    • MDEV-395 PR_SET_DUMPABLE set in unreachable code

  • Revision #3515 Wed 2012-08-29 15:19:17 +0200

    • MDEV-448 Memory loss warnings in mysqldump when more than one schema is dumped

  • Revision #3514 Tue 2012-08-28 19:39:49 +0300

    • Split ER_NO_SUCH_TABLE into ER_NO_SUCH_TABLE and ER_NO_SUCH_TABLE_IN_ENGINE to be able to distingus if a .frm file is missing or if the table is missing in the engine.

  • Revision #3513 Tue 2012-08-28 16:03:22 +0400

    • Update test results (checked)

  • Revision #3512 Tue 2012-08-28 15:40:38 +0400

    • MDEV-405: Server crashes in test_if_skip_sort_order on EXPLAIN with GROUP BY and HAVING in EXISTS subquery

    • Testcase

  • Revision #3511 [merge] Tue 2012-08-28 15:20:37 +0400

    • Merge

    • Revision #3501.1.1 Tue 2012-08-28 15:15:05 +0400

      • MDEV-430: Server crashes in select_describe on EXPLAIN with materialization+semijoin, etc

      • Don't do early cleanup of uncorrelated subqueries if we're running an EXPLAIN.

  • Revision #3510 Tue 2012-08-28 15:07:50 +0500

    • MDEV-471 update help tables.

      • the fill_help_table-5.5.sql file was copied into mariadb.

      • per-file comments:

        • scripts/fill_help_tables.sql

  • Revision #3509 [merge] Mon 2012-08-27 18:13:17 +0200

    • 5.3 merge

    • Revision #2502.567.8 Fri 2012-08-24 23:43:18 +0200

      • MDEV-336 oqgraph 5.5 crashes in buildbot

      • force -fno-strict-aliasing for oqgraph

    • Revision #2502.567.7 Sat 2012-08-25 09:15:57 +0300

      • fix for MDEV-367

      • The problem was that was_null and null_value variables was reset in each reexecution of IN subquery, but engine rerun only for non-constant subqueries.

      • Fixed checking constant in Item_equal sort.

      • Fix constant reporting in Item_subselect.

    • Revision #2502.567.6 [merge] Fri 2012-08-24 19:13:34 +0200

    • Revision #2502.567.5 [merge] Fri 2012-08-24 15:39:34 +0200

    • Revision #2502.567.4 [merge] Fri 2012-08-24 14:26:23 +0200

      • Merge into latest 5.3

    • Revision #2502.567.3 Thu 2012-08-23 13:52:36 +0200

      • remove mysql-5.1 assert that is already absent in mysql-5.5

    • Revision #2502.567.2 Wed 2012-08-22 18:40:27 +0200

      • MDEV-472 mysql-test-run --valgrind main.ps_2myisam gives warning about not initialized memory

      • Item::get_date() should return 1 unless the value is a valid date.

    • Revision #2502.567.1 [merge] Wed 2012-08-22 16:45:25 +0200

      • 5.2 merge.

      • two tests still fail:

        • main.innodb_icp and main.range_vs_index_merge_innodb

        • call records_in_range() with both range ends being open (which triggers an assert)

      • Revision #2502.566.1 [merge] Wed 2012-08-22 16:13:54 +0200

        • 5.1 merge

        • increase xtradb verson from 13.0 to 13.01

        • Revision #2502.565.2 Wed 2012-08-22 16:10:31 +0200

          • merge with XtraDB as of Percona-Server-5.1.63-rel13.4

        • Revision #2502.565.1 [merge] Wed 2012-08-22 11:40:39 +0200

          • merge with MySQL 5.1.65

  • Revision #3508 [merge] Fri 2012-08-24 15:29:01 +0200

  • Revision #3507 [merge] Fri 2012-08-24 13:57:39 +0200

    • Merge from 5.3

    • Revision #2502.561.18 [merge] Fri 2012-08-24 13:51:16 +0200

      • Merge from 5.2

      • Revision #2502.562.10 Thu 2012-06-21 18:47:13 +0300

        • Fix for Bug #1001505 and Bug #1001510

        • We set correct cmp_context during preparation to avoid changing it later by Item_field::equal_fields_propagator. (see mysql bugs #57135 #57692 during merging)

    • Revision #2502.561.17 Tue 2012-08-21 22:24:34 +0400

      • Better comments

    • Revision #2502.561.16 Tue 2012-08-14 14:25:56 -0700

      • Corrected the pactch for MDEV-449 to fix valgrind failures.

    • Revision #2502.561.15 Mon 2012-08-13 21:13:14 -0700

      • Fixed bug MDEV-449.

      • The bug could caused a crash when the server executed a query with ORDER by and sort_buffer_size was set to a small enough number.

      • It happened because the small sort buffer did not allow to allocate all merge buffers in it.

      • Made sure that the allocated sort buffer would be big enough to contain all possible merge buffers.

  • Revision #3506 Thu 2012-08-23 15:36:38 +0200

    • MDEV-439 cmake -DWITHOUT_SERVER does not work

    • fix mysys/waiting_threads.c to compile w/o performance schema include clients. scripts and manpages in -DWITHOUT_SERVER

  • Revision #3505 Thu 2012-08-23 15:32:03 +0200

    • MDEV-469 Debian/Ubuntu build dependencies for source package mariadb-5.5 does not includes "cmake"

    • only add cmake as a build dependency for distributions, where cmake is recent enough

  • Revision #3504 Thu 2012-08-23 15:30:43 +0200

    • remove duplicate code from the factorial dbug example

  • Revision #3503 Wed 2012-08-22 23:33:45 +0200

    • MDEV-469 Debian/Ubuntu build dependencies for source package mariadb-5.5 does not includes "cmake"

  • Revision #3502 Wed 2012-08-22 18:03:31 +0300

    • More DBUG_ENTER, to make it easier to find out where free_root(thd->mem_root) is called

  • Revision #3501 [merge] Wed 2012-08-22 09:56:20 +0200

    • merge XtraDB 1.1.8-27.0 from Percona-Server-5.5.25a-rel27.1

    • Revision #0.12.54 Wed 2012-08-22 08:42:24 +0200

      • XtraDB 1.1.8-27.0 from Percona-Server-5.5.25a-rel27.1

  • Revision #3500 Tue 2012-08-21 15:24:43 +0300

    • Fix bug MDEV-447: Wrong output from the EXPLAIN command of the test case for Bug #714999

    • The fix backports from MWL#182: Explain running statements the logic that saves the original JOIN_TAB array of a query plan after optimization. This array is later used during EXPLAIN to iterate over the original JOIN plan nodes in the cases when this plan could be changed by early subquery execution during the optimization phase of the outer query.

  • Revision #3499 Tue 2012-08-21 08:46:32 +0300

    • Fix for Bug #1039277 "Crash in sql_cache.cc".

    • The crash happend when combining query cache, prepared statements and using a read only cursor.

  • Revision #3498 Mon 2012-08-20 22:54:15 +0300

    • Ensure we don't assert with debug binaries if SHOW INNODB STATUS returns with an error.

  • Revision #3497 Fri 2012-08-17 14:35:28 +0200

    • Fix incorrect regexp in warning suppression pattern

  • Revision #3496 Fri 2012-08-17 10:01:19 +0300

    • Fixed compiler warnings

    • Fixed error in test that caused following tests to fail

  • Revision #3495 Wed 2012-08-15 14:37:55 +0300

    • Fixed MDEV-366: Assertion `share->reopen == 1' failed in maria_extra on DROP TABLE which is locked twice

  • Revision #3494 Wed 2012-08-15 13:33:37 +0300

    • Fixed MDEV-365 "Got assertion when doing alter table on a partition"

  • Revision #3493 [merge] Wed 2012-08-15 12:07:21 +0300

  • Revision #3492 Tue 2012-08-14 12:40:40 +0200

    • MDEV-450: Deadlock between starting a slave and reading system variables

    • Starting the SQL thread might deadlock with reading the values of the replication filtering options.

    • The deadlock is due to a lock order violation when the variables are read or set. For example, reading replicate_ignore_table first acquires LOCK_global_system_variables in sys_var::value_ptr and later acquires LOCK_active_mi in Sys_var_rpl_filter::global_value_ptr. This violates the order established when starting a SQL thread, where LOCK_active_mi is acquired before start_slave, and ends up creating a thread (handle_slave_sql) that allocates a THD handle whose constructor acquires LOCK_global_system_variables in THD::init.

    • The solution is to unlock LOCK_global_system_variables before the replication filtering options are set or read. This way the lock order is preserved and the data being read/set is still protected given that it acquires LOCK_active_mi.

  • Revision #3491 Mon 2012-08-13 11:14:43 +0200

    • MDEV-364 Server crashes in add_identifier on concurrent ALTER TABLE and SHOW ENGINE INNODB STATUS

    • fix add_identifier() to distinguish between temporary tables (#sql- prefix) and temporary partitions (#TMP

suffix).

  • change add_identifier() to use the same name variant constants as sql_partition.cc does.

  • Revision #3490 Mon 2012-08-13 09:21:47 +0200

    • MDEV-286 mytop is not installed in 5.5

    • include mytop in bintars, rpms, and debs.

    • install mysqlbug.1 too.

  • Revision #3489 Sat 2012-08-11 10:31:10 +0200

    • MDEV-336 oqgraph 5.5 crashes in buildbot

    • compile oqgraph with -fno-strict-aliasing

  • Revision #3488 Fri 2012-08-10 13:48:31 +0200

    • compiler warnings

  • Revision #3487 Thu 2012-08-09 18:25:47 +0200

    • fix val_str_ascii to return a string in the ascii-compatible charset.

    • two items didn't do that properly, one was exploitable, the other was not, but fixed anyway.

  • Revision #3486 [merge] Thu 2012-08-09 17:22:00 +0200

    • merge with MySQL 5.5.27

    • manually checked every change, reverted incorrect or stupid changes.

    • Revision #3077.149.180 Wed 2012-08-08 12:32:34 +0200

      • undo the fix for MySQL Bug#12998841

  • Revision #3485 Wed 2012-08-08 12:08:54 +0200

    • MDEV-392 MTR: skip-combinations option is declared in help, but is ignored

    • remove unused mtr option

  • Revision #3484 Mon 2012-08-06 16:33:11 +0300

    • Fixed compiler warnings

  • Revision #3483 Wed 2012-08-01 19:57:36 +0200

    • MDEV-399 Combinations defined in the base suite cannot be skipped by overlay

    • When appliying parent combinations to the overlay, filter them through the %skip_combinations using the overlayed filename

  • Revision #3482 Thu 2012-08-02 23:17:27 +0200

    • fix oqgraph on MSVC

  • Revision #3481 Thu 2012-08-02 04:48:33 +0400

    • MDEV-369: Mismatches in MySQL engines test suite

    • Post-merge fixes for mismatches that only affect 5.5 (but not 5.3)

  • Revision #3480 [merge] Thu 2012-08-02 04:22:43 +0400

    • Merge 5.3->5.5

    • Revision #2502.561.14 [merge] Thu 2012-08-02 00:58:13 +0400

      • MDEV-369 (Mismatches in MySQL engines test suite)

      • Following reasons caused mismatches:

        • different handling of invalid values;

        • different CAST results with fractional seconds;

        • microseconds support in MariaDB;

        • different algorithm of comparing temporal values;

        • differences in error and warning texts and codes;

        • different approach to truncating datetime values to time;

        • additional collations;

        • different record order for queries without ORDER BY;

        • MySQL Bug #66034.

      • More details in MDEV-369 comments.

      • Revision #2502.564.2 Mon 2012-07-30 04:16:49 +0400

        • MDEV-369 (Mismatches in MySQL engines test suite)

      • Revision #2502.564.1 Thu 2012-07-26 23:31:08 +0400

  • Revision #3479 Tue 2012-07-31 22:39:33 +0200

    • MDEV-336 oqgraph 5.5 crashes in buildbot

    • make CMakeLists.txt to detect if the installed boost can be compiled with the installed compile and specified set of compiler options.

    • Background: even sufficiently new Boost cannot be compiled with the sufficiently old gcc in the presence of -fno-rtti

  • Revision #3478 Tue 2012-07-31 19:29:07 +0200

    • MDEV-419 ensure that all HAVE_XXX constants can be set by cmake

    • add missing checks to configure.cmake

    • remove dead code and unused HAVE_xxx constants from the sources

  • Revision #3477 Tue 2012-07-31 18:32:46 +0200

    • MDEV-375 Server crashes in THD::print_aborted_warning with log_warnings > 3

    • Don't use ER(xxx) in THD::close_connection(), when current_thd is already reset to NULL.

    • Prefer ER_THD() or ER_DEFAULT() instead.

  • Revision #3476 Tue 2012-07-31 16:21:53 +0500

    • MDEV-340 Save replication comments for DROP TABLE.

    • mysql_rm_table_no_locks() function was modified.

    • When we construct log record for the DROP TABLE, now we look if there's a comment before the first table name and add it to the record if so.

    • per-file comments:

      • sql/sql_table.cc

        • MDEV-340 Save replication comments for DROP TABLE.

          • comment_length() function implemented to find comments in the query,

          • call it in mysql_rm_table_no_locks() and use the result to form log record.

      • mysql-test/suite/binlog/r/binlog_drop_if_exists.result

        • MDEV-340 Save replication comments for DROP TABLE.

          • test result updated.

      • mysql-test/suite/binlog/t/binlog_drop_if_exists.test

        • MDEV-340 Save replication comments for DROP TABLE.

          • test case added.

  • Revision #3475 Tue 2012-07-31 11:31:26 +0200

    • MDEV-418 Feedback plugin statisics problem

    • Add the check for sys/utsname.h to configure.cmake

  • Revision #3474 Mon 2012-07-30 20:13:23 +0200

    • MDEV-417 - fix typo that prevented use of atomic instructions on Windows

    • use correct macro for Microsoft compiler. It is _MSC_VER , not _MSV_VER

  • Revision #3473 Wed 2012-07-25 20:41:48 +0400

    • MDEV-410: EXPLAIN shows type=range, while SHOW EXPLAIN and userstat show full table scan is used

    • Make Item_subselect::fix_fields() ignore UNCACHEABLE_EXPLAIN flag when deciding whether the subquery item should be marked as constant.

  • Revision #3472 Tue 2012-07-24 17:50:06 +0300

    • Awoiding registering partiton engine underlying tables whan it has no sens.

  • Revision #3471 Mon 2012-07-23 23:54:57 +0200

    • MDEV-409 : /etc/my.cnf config file overwritten during RPM installation

    • Fix : use attribute %config(noreplace) for /etc/my.cnf , instead of (automatically generated) %config

  • Revision #3470 [merge] Thu 2012-07-19 13:24:24 +0200

  • Revision #3469 [merge] Wed 2012-07-18 22:40:15 +0400

    • Merge 5.3->5.5

    • Revision #2502.561.13 Wed 2012-07-18 15:03:05 +0400

      • MDEV-398: Sergv related to spacial queries

      • index_merge/intersection is unable to work on GIS indexes, because:

        1. index scans have no Rowid-Ordered-Retrieval property

        2. When one does an index-only read over a GIS index, they do not get the index tuple, because index only contains bounding box of the geometry. This is why key_copy() call crashed.

      • This patch fixes #1, which makes the problem go away. Theoretically, it would be nice to check #2, too, but SE API semantics is not sufficiently precise to do it.

  • Revision #3468 [merge] Wed 2012-07-18 22:36:20 +0400

    • Merge Bug #1007622 from 5.3 to 5.5

    • Revision #2502.561.12 Tue 2012-06-26 21:43:34 +0300

      • Fix for Bug #1007622

      • TABLE_LIST::check_single_table made aware about fact that now if table attached to a merged view it can be (unopened) temporary table (in 5.2 it was always leaf table or non (in case of several tables)).

  • Revision #3467 Mon 2012-07-16 10:48:03 +0300

    • fix to satisfy compiler.

  • Revision #3466 Fri 2012-07-13 22:17:32 +0300

    • fixed MySQL Bug #53775:

    • Now partition engine adds underlying tables to the QC and ask underlying tables engine permittion to cache the query and return result of the query.

    • Incorrect QC cleanup in case of table registration failure fixe.

    • Unified interface for myisammrg & partitioned engnes for QC.

  • Revision #3465 Thu 2012-07-12 15:32:35 +0200

    • MDEV-393. Remove --loose-pbxt=OFF/loose-skip-pbxt from bootstrapper calls to avoid "unknown parameter" warning

  • Revision #3464 Wed 2012-07-11 16:19:05 +0200

    • Bug #1023404 problems with savepoints and tokudb with 5.5

    • fix incorrect merge

  • Revision #3463 Tue 2012-07-10 09:02:12 +0300

    • Fixed MDEV-385: mysqltest running with continue-on-error crashes on a non-SQL command producing an error

  • Revision #3462 [merge] Thu 2012-07-05 14:39:01 +0400

    • Merge fix for MDEV-376

    • Revision #3457.1.1 Wed 2012-07-04 14:34:45 +0400

      • MDEV-376: Wrong result (missing rows) with index_merge+index_merge_intersection, join

      • Let QUICK_RANGE_SELECT::init_ror_merged_scan() call quick->reset() only after we've set the column read bitmaps.

  • Revision #3461 Thu 2012-07-05 09:29:34 +0200

    • The variable "table_cache" is deprecated, use the new name "table_open_cache" instead.

    • Thanks to Ivoz for pointing this out.

  • Revision #3460 Wed 2012-06-27 17:13:12 +0300

    • Don't abort InnoDB/XtraDB if one can't allocate resources for AIO

    • Better error messages

    • This fixes that one again can run the test systems with many threads without having to increase fs.aio-max-nr.

  • Revision #3459 Mon 2012-06-25 18:17:24 +0200

    • fix compile error, when building with oqgraph

  • Revision #3458 [merge] Sun 2012-06-24 09:10:11 -0700

    • Merge 5.3->5.5.

    • Revision #2502.561.11 [merge] Sat 2012-06-23 15:00:05 -0700

      • Merge 5.2->5.3

      • Revision #2502.562.9 Sat 2012-06-23 12:19:07 -0700

        • Fixed bug MDEV-360.

        • The bug was the result of the incomplete fix for bug lp bug 1008293.

      • Revision #2502.562.8 Mon 2012-06-18 22:32:17 -0700

        • Fixed bug MDEV-354.

        • Virtual columns of ENUM and SET data types were not supported properly in the original patch that introduced virtual columns into MariaDB 5.2.

        • The problem was that for any virtual column the patch used the interval_id field of the definition of the column in the frm file as a reference to the virtual column expression.

        • The fix stores the optional interval_id of the virtual column in the extended header of the virtual column expression.

    • Revision #2502.561.10 Fri 2012-06-22 14:14:22 +0400

      • Added comment about QUICK_RANGE_SELECT::free_cond being unused.

    • Revision #2502.561.9 Thu 2012-06-21 14:33:36 +0400

      • Update test results (checked)

    • Revision #2502.561.8 Wed 2012-06-20 22:30:24 +0400

      • Update test results.

  • Revision #3457 Sat 2012-06-23 20:12:54 +0400

    • Add back testcase for Bug #817966 (was lost in the merge)

  • Revision #3456 Fri 2012-06-22 10:42:55 +0200

    • MDEV-342: fix two race conditions in the test case that could occasionally cause spurious failures.

Be notified of new MariaDB Server releases automatically by subscribing 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

PreviousMariaDB 5.5.25 ChangelogNextMariaDB 5.5.28 Changelog

Last updated

Was this helpful?