circle-info
Live Webinar | From Strategy to Execution: Your Practical MySQL to MariaDB Migration Plan
Register Nowarrow-up-right
search
Download MariaDBContact Us

MariaDB 10.0.6 Changelog

The most recent release in the MariaDB 10.0 series is:MariaDB 10.0.38 Download Nowarrow-up-right

Downloadarrow-up-right |Release Notes |Changelog |Overview of 10.0

Release date: 18 Nov 2013

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 #3906arrow-up-right Thu 2013-11-14 19:56:55 +0100

    • add missing plugins to deb packages

  • Revision #3905arrow-up-right Thu 2013-11-14 14:31:30 +0400

    • MDEV-4437arrow-up-right ALTER TABLE .. ADD UNIQUE INDEX IF NOT EXISTS causes syntax error. Added the IF NOT EXISTS option to the CONSTRAINT keyword.

  • Revision #3904arrow-up-right [merge] Wed 2013-11-13 23:03:48 +0100

  • Revision #3903arrow-up-right Wed 2013-11-13 22:58:19 +0100

    • MDEV-5248arrow-up-right Serious incompatibility and data corruption of DATETIME and DATE types due to get_innobase_type_from_mysql_type refactor combined with InnoDB Online DDL

    • restore old innodb get_innobase_type_from_mysql_type() function, record all mysql_type->innodb_type mapping (as generated by mysql-5.6). add safety code to disable online alter when internal types don't match

  • Revision #3902arrow-up-right Wed 2013-11-13 22:58:10 +0100

    • MDEV-5275arrow-up-right Problems upgrading from MySQL 5.1 to MariaDB

    • correct bugs in mysql_system_tables_fix.sql. Update system_mysql_db_fix* tests

  • Revision #3901arrow-up-right Wed 2013-11-13 15:40:46 +0100

    • MDEV-5282arrow-up-right: mysql_install_db fails to create mysql.gtid_slave_pos

    • Patch by Elena.

    • Move the table creation to the end of the file, so mysql.innodb_stats_table has been created and the statement does not fail.

  • Revision #3900arrow-up-right Tue 2013-11-12 16:48:57 +0400

    • Merging xxx_unicode_520_ci and xxx_vietnamese_ci from MySQL-5.6.

  • Revision #3899arrow-up-right [merge] Mon 2013-11-11 23:40:53 +0200

  • Revision #3898arrow-up-right [merge] Mon 2013-11-11 22:46:14 +0400

    • Merge 10.0-monty -> 10.0

    • Revision #3885.2.2arrow-up-right Mon 2013-11-11 16:21:31 +0400

      • MDEV-5241arrow-up-right: Collation incompatibilities with MySQL-5.6 A clean-up: removing the code catching collation incompatibilities from handler::check_collation_compatibility(), as the collation IDs are already replaced at this point by TABLE_SHARE::init_from_binary_frm_image.

    • Revision #3885.2.1arrow-up-right Sat 2013-11-09 00:20:07 +0200

      • MDEV-5241arrow-up-right: Collation incompatibilities with MySQL-5.6 - Character set code & tests from Alexander Barkov - Integration with ALTER TABLE, REPAIR and open_table from Monty

      • The problem was that MySQL 5.6 added some croatian and vitanamese character set collations that are incompatible with MariaDB.

      • The fix is to move the MariaDB conflicting collation numbers out of the region that MySQL is likely to use. mysql_upgrade, REPAIR TABLE or ALTER TABLE will fix the collations. If one tries to access and old incompatible table, one will get the error "Table upgrade required...." After this patch, MariaDB supports all the MySQL character set collations and the old MariaDB croatian collations, which are closer to the latest standard than the MySQL versions.

      • New character sets: ucs2_croatian_mysql561_uca_ci utf8_croatian_mysql561_uca_ci utf16_croatian_mysql561_uca_ci utf32_croatian_mysql561_uca_ci utf8mb4_croatian_mysql561_uca_ci

      • Other things: - Fixed some compiler warnings - mysql_upgrade prints information about repaired tables. - Increased version number

  • Revision #3897arrow-up-right Mon 2013-11-11 19:45:55 +0400

    • MDEV-4436arrow-up-right CHANGE COLUMN IF EXISTS does not work and throws wrong warning. Use sql_field->change parameter as the name of the field.

  • Revision #3896arrow-up-right Mon 2013-11-11 18:23:53 +0400

    • MDEV-4435arrow-up-right Server crashes in my_strcasecmp_utf8 on ADD KEY IF NOT EXISTS with implicit name when the key exists. Use field name as a key name if the key name wasn't specified.

  • Revision #3895arrow-up-right Sun 2013-11-10 17:51:26 +0100

    • MDEV-201arrow-up-right - Assertion `!thd->spcont' failed in net_send_error on server shutdown

    • restore sergii@pisem.net-20120327141644-xue6r05x1giswwsm that was lost in a merge

  • Revision #3894arrow-up-right Sun 2013-11-10 17:51:20 +0100

    • MDEV-4880arrow-up-right Attempt to create a table without columns produces ER_ILLEGAL_HA instead of ER_TABLE_MUST_HAVE_COLUMNS

  • Revision #3893arrow-up-right Sun 2013-11-10 17:51:13 +0100

  • Revision #3892arrow-up-right Sun 2013-11-10 17:51:06 +0100

    • MDEV-4931arrow-up-right Can't use SHUTDOWN in stored programs

    • keywords that a statement could start from can only be in the 'keyword' list, never in the 'keyword_sp'

  • Revision #3891arrow-up-right Sun 2013-11-10 17:51:01 +0100

    • MDEV-5260arrow-up-right discovery with sql is too restrictive

    • allow ENGINE=FOOBAR in the discovering create table statement, as long as the discovering engine is FOOBAR too

  • Revision #3890arrow-up-right Sun 2013-11-10 17:50:52 +0100

  • Revision #3889arrow-up-right [merge] Sat 2013-11-09 11:05:51 +0100

    • merge with 10.0.5

  • Revision #3888arrow-up-right Sat 2013-11-09 11:04:54 +0100

    • mariadb-tokudb-engine-10.0.deb

  • Revision #3887arrow-up-right Thu 2013-11-07 14:30:21 +0100

    • misc fixes for buildbot

  • Revision #3886arrow-up-right [merge] Fri 2013-11-08 23:44:20 +0400

  • Revision #3885arrow-up-right [merge] Thu 2013-11-07 07:52:40 +0100

    • Merge 10.0-base to 10.0

    • Revision #3427.35.196arrow-up-right [merge] Thu 2013-11-07 04:31:52 +0400

    • Revision #3427.35.195arrow-up-right Wed 2013-11-06 14:51:06 +0100

      • MDEV-4506arrow-up-right: Parallel replication MDEV-5217arrow-up-right: Incorrect MyISAM event execution order causing incorrect parallel replication

      • In parallel replication, if transactions A,B group-commit together on the master, we can execute them in parallel on a replication slave. But then, if transaction C follows on the master, on the slave, we need to be sure that both A and B have completed before starting on C to be sure to avoid conflicts.

      • The necessary wait is implemented such that B waits for A to commit before it commits itself (thus preserving commit order). And C waits for B to commit before it itself can start executing. This way C does not start until both A and B have completed.

      • The wait for B's commit on A happens inside the commit processing. However, in the case of MyISAM with no binlog enabled on the slave, it appears that no commit processing takes place (since MyISAM is non-transactional), and thus the wait of B for A was not done. This allowed C to start before A, which can lead to conflicts and incorrect replication.

      • Fixed by doing an extra wait for A at the end of B before signalling C.

    • Revision #3427.35.194arrow-up-right Wed 2013-11-06 11:29:07 +0100

      • MDEV-4506arrow-up-right: Parallel replication MDEV-5217arrow-up-right: Unlock of de-allocated mutex

      • There was a race in the code for wait_for_commit::wakeup().

      • Since the waiter does a dirty read of the waiting_for_commit flag, it was possible for the waiter to complete and deallocate the wait_for_commit object while the waitee was still running inside wakeup(). This would cause the waitee to access invalid memory.

      • Fixed by putting an extra lock/unlock in the destructor for wait_for_commit, to ensure that waitee has finished with the object before it is deallocated.

    • Revision #3427.35.193arrow-up-right Wed 2013-11-06 10:18:04 +0100

      • MDEV-4506arrow-up-right: Parallel replication MDEV-5217arrow-up-right: Incorrect event pos update leading to corruption of reading of events from relay log

      • The rli->event_relay_log_pos was sometimes undated incorrectly when using parallel replication, especially around relay log rotates. This could cause the SQL thread to seek into an invalid position in the relay log, resulting in errors about invalid events or even random corruption in some cases.

    • Revision #3427.35.192arrow-up-right Tue 2013-11-05 14:49:57 +0100

      • MDEV-4506arrow-up-right: Parallel replication. MDEV-5217arrow-up-right: Last_sql_error lost in parallel replication.

      • For some reason, the query execution code in log_event.cc call rli->clear_error for each event (part of clear_all_errors()). This causes a problem in parallel replication, where the execution in one worker thread could clear the error set by another thread, causing the SQL thread to stop but leaving no error visible in SHOW SLAVE STATUS.

      • There seems to be no reason to clear the global error code in Relay_log_info for each event execution, from code review and from running the test suite. So remove this clearing of the error code to make things work also in the parallel case.

    • Revision #3427.35.191arrow-up-right Tue 2013-11-05 12:01:26 +0100

      • MDEV-4506arrow-up-right: Parallel replication MDEV-5217arrow-up-right: SQL thread hangs during stop if error occurs in the middle of an event group

      • Normally, when we stop the slave SQL thread in parallel replication, we want the worker threads to continue processing events until the end of the current event group. But if we stop due to an error that prevents further events from being queued, such as an error reading the relay log, no more events can be queued for the workers, so they have to abort even if they are in the middle of an event group. There was a bug that we would deadlock, the workers waiting for more events to be queued for the event group, the SQL thread stopped and waiting for the workers to complete their current event group before exiting.

      • Fixed by now signalling from the SQL thread to all workers when it is about to exit, and cleaning up in all workers when so signalled.

      • This patch fixes one of multiple problems reported in MDEV-5217arrow-up-right.

  • Revision #3884arrow-up-right Wed 2013-11-06 17:55:22 +0400

    • Recording correct test results: mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result

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 10.0.7 ChangelogNextMariaDB 10.0.5 Changelog

Last updated

Was this helpful?