The Ultimate Guide to High Availability with MariaDB

MariaDB 5.1.66 Changelog

You are viewing an old version of this article. View the current version here.

Download | Release Notes | Changelog Release date: 26 Nov 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 #3145 [merge] Thu 2012-04-05 10:49:38 +0200
    • mysql-5.1.62 merge
    • Revision #2502.1178.22 [merge] Fri 2012-03-02 13:18:12 +0100
      • Upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.0 to 5.1.
      • Revision #1810.4000.36 Fri 2012-03-02 13:12:07 +0100
        • Further upgrade the yaSSL library to version 2.2.0 to pick up some new security fixes that are in it.
        • Patch provided by Georgi Kodinov.
    • Revision #2502.1178.21 Tue 2012-02-28 17:20:30 +0100
      • AIX builds fail for comments using
    • Revision #2502.1178.20 [merge] Tue 2012-02-28 12:44:21 +0100
      • Upmerge the copyright year change, from 5.0 to 5.1.
      • Revision #1810.4000.35 Tue 2012-02-28 12:42:02 +0100
        • The current year is 2012, and nobody noticed ... Update the year in the copyright notice, file "README".
    • Revision #2502.1178.19 [merge] Sat 2012-02-18 10:58:19 +0200
      • merge mysql-5.1->mysql-5.1-security
      • Revision #2502.1137.140 Fri 2012-02-17 11:42:04 +0200
        • Bug#13721257 RACE CONDITION IN UPDATES OR INSERTS OF WIDE RECORDS
    • Revision #2502.1178.18 [merge] Fri 2012-02-17 11:55:06 +0200
      • merge mysql-5.0-security->mysql-5.1-security
      • Revision #1810.4000.34 [merge] Fri 2012-02-17 11:51:14 +0200
        • merged mysql-5.0->mysql-5.0-security
    • Revision #2502.1178.17 [merge] Fri 2012-02-17 11:52:41 +0200
      • merge mysql-5.1->mysql-5.1-security
      • Revision #2502.1137.139 Thu 2012-02-16 15:54:16 +0200
        • Fix link error on Windows. error LNK2001: unresolved external symbol _debug_sync_C_callback_ptr
      • Revision #2502.1137.138 [merge] Thu 2012-02-16 12:02:53 +0100
        • Merge
        • Revision #2502.1183.4 Thu 2012-02-16 12:24:11 +0200
          • Add instrumentation for Bug#13721257 RACE CONDITION IN UPDATES OR INSERTS OF WIDE RECORDS
          • row_ins_index_entry_low(), row_upd_clust_rec(): Make a redo log checkpoint if a DEBUG flag is set. Add DEBUG_SYNC around btr_store_big_rec_extern_fields().
          • rb:946 approved by Jimmy Yang
        • Revision #2502.1183.3 Thu 2012-02-16 12:20:41 +0200
          • Correct a few copyright messages.
      • Revision #2502.1137.137 Thu 2012-02-16 11:35:30 +0100
        • Updated/added copyright headers
      • Revision #2502.1137.136 [merge] Thu 2012-02-16 11:17:04 +0100
        • Merge
        • Revision #2502.1183.2 Wed 2012-02-15 16:28:00 +0200
          • Remove a race condition in innodb_bug53756.test. Before killing the server, tell mysql-test-run that it is to be expected.
          • Discussed with Bjorn Munch on IM.
        • Revision #2502.1183.1 Wed 2012-02-15 15:53:29 +0200
          • store_create_info(): Fix a compiler warning about unused variable.
      • Revision #2502.1137.135 [merge] Wed 2012-02-15 17:21:38 +0100
        • Updated/added copyright headers
        • Revision #1810.3997.19 Wed 2012-02-15 17:13:47 +0100
          • Updated/added copyright headers
      • Revision #2502.1137.134 Fri 2012-02-10 14:09:12 +1100
        • BUG#12739098 - 62401: ASSERTION TRX->ERROR_STATE == DB_SUCCESS, QUE0QUE.C LINE 1264 ON TRUNCATE
        • During FIC error handling the trx->error_state was not being set to DB_SUCCESS after failure, before attempting the next DDL SQL operation. This reset to DB_SUCCESS is somewhat of a requirement though not explicitly stated anywhere. The fix is to reset it to DB_SUCCESS in row0merge.cc if row_merge_rename_indexes or row_merge_drop_index functions fail, also reset to DB_SUCCESS at trx commit.
        • rb:935 Approved by Jimmy Yang.
    • Revision #2502.1178.16 [merge] Thu 2012-02-16 15:55:53 +0100
      • Merge compile fix for AIX into delivery tree.
      • Revision #2502.1182.1 Thu 2012-01-19 17:05:47 +0100
        • Compile fix needed for AIX, to work around the lack of a bzero() prototype.
    • Revision #2502.1178.15 [merge] Mon 2012-02-13 13:40:12 +0200
      • merge from 5.0-security
      • Revision #1810.4000.33 Fri 2012-02-10 16:33:27 +0200
        • Bug #13706828: UPGRADE YASSL FROM 1.7.2 TO 2.1.4
        • $SUBJ$ 1. Took a diff between the previous base version and the mysql sources. 2. Added the new 2.1.4 base version. 3. Reviewed and re-applied the diff from step #1.
    • Revision #2502.1178.14 [merge] Fri 2012-02-10 11:49:48 +0200
      • merge
      • Revision #2502.1181.1 Tue 2012-02-07 14:16:09 +0100
        • Bug #11765810 58813: SERVER THREAD HANGS WHEN JOIN + WHERE + GROUP BY IS EXECUTED TWICE FROM P
        • This bug is a duplicate of bug 12567331, which was pushed to the optimizer backporting tree on 2011-06-11. This is just a back-port of the fix. Both test cases are included as they differ somewhat.
    • Revision #2502.1178.13 [merge] Fri 2012-02-10 11:39:51 +0200
      • empty merge of mysql-5.0-security->mysql-5.1-security
      • Revision #1810.4000.32 Fri 2012-02-10 11:10:07 +0200
        • Bug#13706621 : UNIFY THE YASSL VERSIONS THAT WE USE BY BACKPORTING 5.1 AND 5.5 YASSL FIXES.
        • Took the 5.5 yassl code and applied it to the 5.0 codebase, keeping the compilation files.
    • Revision #2502.1178.12 Fri 2012-02-10 11:35:36 +0200
      • Bug#13706621 : UNIFY THE YASSL VERSIONS THAT WE USE BY BACKPORTING 5.1 AND 5.5 YASSL FIXES.
      • Took the 5.5 yassl directory and moved it to the 5.1 tree, while preserving the makefiles.
    • Revision #2502.1178.11 [merge] Mon 2012-02-06 18:26:48 +0200
      • empty weave merge mysql-5.0-security->mysql-5.1-security
      • Revision #1810.4000.31 [merge] Mon 2012-02-06 18:23:41 +0200
        • merged mysql-5.0->mysql-5.0-security
    • Revision #2502.1178.10 [merge] Mon 2012-02-06 18:24:51 +0200
      • merged mysql-5.1->mysql-5.1-security
      • Revision #2502.1137.133 Mon 2012-02-06 12:44:59 +0200
        • Fix Bug#11754376 45976: INNODB LOST FILES FOR TEMPORARY TABLES ON GRACEFUL SHUTDOWN
        • During startup mysql picks up .frm files from the tmpdir directory and tries to drop those tables in the storage engine.
        • Reviewed by: Marko (http://bur03.no.oracle.com/rb/r/929/)
      • Revision #2502.1137.132 Fri 2012-02-03 19:37:00 +0530
        • BUG#11748748 - 37280: CHECK AND REPAIR TABLE REPORT TABLE CORRUPTED WHEN RUN CONCURRENTLY WITH
        • ISSUE: Table corruption due to concurrent queries. Different threads running check, repair query along with insert. Locks not properly acquired in repair query. Rows are inserted inbetween repair query.
        • SOLUTION: Mutex lock is acquired before the repair call. Concurrent queries wont effect the call to repair.
      • Revision #2502.1137.131 Thu 2012-02-02 16:22:13 +0400
        • Postfix for Bug#11752408. Recording correct test results.
        • modified: mysql-test/suite/engines/funcs/r/db_alter_collate_ascii.result mysql-test/suite/engines/funcs/r/db_alter_collate_utf8.result
      • Revision #2502.1137.130 Thu 2012-02-02 13:38:32 +0200
        • Bug#13654923 BOGUS DEBUG ASSERTION IN INDEX CREATION FOR ZERO-LENGTH RECORD
        • row_merge_buf_write(): Relax the bogus assertion.
      • Revision #2502.1137.129 Thu 2012-02-02 12:07:06 +0200
        • Suppress messages about long semaphore waits in innodb_bug34300.test.
      • Revision #2502.1137.128 [merge] Thu 2012-02-02 14:19:38 +0530
        • BUG#11756869 - 48848: MYISAMCHK DOING SORT RECOVER IN CERTAIN CASES RESETS DATA POINTER TO SMAL
        • ISSUE: Myisamchk doing sort recover on a table reduces data_file_length. Maximum size of data file decreases, lesser number of rows are stored.
        • SOLUTION: Size of data_file_length is fixed to the original length.
        • Revision #2502.1180.1 Wed 2012-02-01 11:19:53 +0530
          • BUG#11756869 - 48848: MYISAMCHK DOING SORT RECOVER IN CERTAIN CASES RESETS DATA POINTER TO SMAL
          • ISSUE: Myisamchk doing sort recover on a table reduces data_file_length. Maximum size of data file decreases, lesser number of rows are stored.
          • SOLUTION: Size of data_file_length is fixed to the original length.
      • Revision #2502.1137.127 Tue 2012-01-31 09:31:31 -0500
        • Bug#13636122 THE ORIGINAL TABLE MISSING WHILE EXECUTE THE DDL 'ALTER TABLE ADD COLUMN
        • rb:914 approved by: Marko Makela
        • Poll in fil_rename_tablespace() after setting ::stop_ios flag can result in a hang because the other thread actually dispatching the IO won't wake IO helper threads or flush the tablespace before starting wait in fil_mutex_enter_and_prepare_for_io().
      • Revision #2502.1137.126 Tue 2012-01-31 17:39:40 +0530
      • Revision #2502.1137.125 Tue 2012-01-31 17:09:32 +0530
        • Bug #64127: MTR --warnings option misses some of InnoDB errors and warnings
      • Revision #2502.1137.124 [merge] Tue 2012-01-31 10:57:12 +0400
        • Null-merge from mysql-5.0.
        • Revision #1810.3997.18 Mon 2012-01-30 22:52:33 +0400
          • Fix for BUG#13596377: MYSQL CRASHES ON STARTUP ON FREEBSD IN PB2
          • Fix for #36428/#38364 backported into 5.0.
      • Revision #2502.1137.123 Thu 2012-01-26 10:25:23 +0100
        • Fixes for: BUG#13519696 - 62940: SELECT RESULTS VARY WITH VERSION AND WITH/WITHOUT INDEX RANGE SCAN BUG#13453382 - REGRESSION SINCE 5.1.39, RANGE OPTIMIZER WRONG RESULTS WITH DECIMAL CONVERSION BUG#13463488 - 63437: CHAR & BETWEEN WITH INDEX RETURNS WRONG RESULT AFTER MYSQL 5.1. Those are all cases where the range optimizer got it wrong with > and >=.
      • Revision #2502.1137.122 Wed 2012-01-25 10:15:27 +0200
        • btr_cur_search_to_nth_level(): Add a debug assertion and some Valgrind instrumentation.
      • Revision #2502.1137.121 [merge] Tue 2012-01-24 16:02:12 +0400
        • Merging from mysql-5.1
        • Revision #2502.1179.1 Mon 2012-01-23 13:07:10 +0400
          • Bug#11752408 - 43593: DUMP/BACKUP/RESTORE/UPGRADE TOOLS FAILS BECAUSE OF UTF8_GENERAL_CI
          • Introducing new collations: utf8_general_mysql500_ci and ucs2_general_mysql500_ci, to reproduce behaviour of utf8_general_ci and ucs2_general_ci from mysql-5.1.23 (and earlier).
          • The collations are added to simplify upgrade from mysql-5.1.23 and earlier.
          • Note: The patch does not make new server start over old data automatically. Some manual upgrade procedures are assumed.
          • Paul: please get in touch with me to discuss upgrade procedures when documenting this bug.
          • modified: include/m_ctype.h mysql-test/r/ctype_utf8.result mysql-test/t/ctype_utf8.test mysys/charset-def.c strings/ctype-ucs2.c strings/ctype-utf8.c
      • Revision #2502.1137.120 Tue 2012-01-24 13:00:13 +0400
        • BUG#13458237 - INCONSISTENT HANDLING OF INVALIDE DATES WITH ZERO DAY. SIMILAR TO '2009-10-00' - Reverting the patch for Bug # 12584302 The patch will be reverted in 5.1 and 5.5. The patch will not be reverted in 5.6, the change will be properly documented in 5.6. - Backporting DBUG_ASSERT not to crash on '0000-01-00' (already fixed in mysql-trunk (5.6))
      • Revision #2502.1137.119 Tue 2012-01-17 09:10:58 +0530
        • Bug #11760384 52792: MYSQLDUMP IN XML MODE DOES NOT DUMP ROUTINES
        • Minor post-fix to avoid build failure when built with Werror.
      • Revision #2502.1137.118 Mon 2012-01-16 14:22:03 +0200
        • Bug#13496818 ASSERTION: REC_PAGE_NO > 4 IN IBUF CONTRACTION Relax a bogus debug assertion. Approved by Jimmy Yang on IM.
      • Revision #2502.1137.117 Mon 2012-01-16 09:17:40 +0000
        • BUG#11893288 60542: RPL.RPL_EXTRA_COL_MASTER_* DOESN'T TEST WHAT WAS INTENDED
        • Test extra/rpl_tests/rpl_extra_col_master.test (used by rpl_extra_col_master_*) ends with the active connection pointing to the slave. Thus, the two last tests never succeed in changing the binlog format of the master away from 'row'. With correct active connection (master) tests fail for binlog 'statement' and 'mixed' formats.
        • Tests rpl_extra_col_master_* only run when binary log format is row. Statement and mix replication do not make sense in this tests since it will try to execute statements on columns that do not exist. This fix is basically a backport from mysql-5.5, see changes done as part of BUG 39934.
      • Revision #2502.1137.116 Mon 2012-01-16 09:55:12 +0200
        • buf_page_get_known_nowait(): Relax a bogus debug assertion. When mode==BUF_KEEP_OLD, buffered inserts are being merged to the page. It is possible that a read request for a page was pending while the page was freed in DROP INDEX or DROP TABLE. In these cases, it is OK (although useless) to merge the buffered changes to the freed page.
      • Revision #2502.1137.115 Mon 2012-01-16 09:58:31 +0530
        • Bug #11765438 58406: ISSUES WITH COPYING PARTITIONED INNODB TABLES FROM LINUX TO WINDOWS
        • This problem was already fixed in mysql-trunk as part of bug #11755924. I am backporting the fix to mysql-5.1.
    • Revision #2502.1178.9 Mon 2012-01-30 11:57:33 +0530
      • Bug#13105873 :Valgrind Warning: CRASH IN FOREIGN KEY HANDLING ON SUBSEQUENT CREATE TABLE IF NOT EXISTS
    • Revision #2502.1178.8 Fri 2012-01-27 11:13:13 +0100
      • Bug#13580775 ASSERTION FAILED: RECORD_LENGTH == M_RECORD_LENGTH Bug#13011410 CRASH IN FILESORT CODE WITH GROUP BY/ROLLUP
      • The assert in 13580775 is visible in 5.6 only, but shows that all versions are vulnerable. 13011410 crashes in all versions.
      • filesort tries to re-use the sort buffer between invocations in order to save malloc/free overhead. The fix for Bug 11748783 - 37359: FILESORT CAN BE MORE EFFICIENT. added an assert that buffer properties (num_records, record_length) are consistent between invocations. Indeed, they are not necessarily consistent.
      • Fix: re-allocate the sort buffer if properties change.
    • Revision #2502.1178.7 [merge] Thu 2012-01-12 16:43:41 +0200
      • empty weave merge mysql-5.0-security->mysql-5.1-security
      • Revision #1810.4000.30 [merge] Thu 2012-01-12 16:39:44 +0200
        • empty weave merge from mysql-5.0
    • Revision #2502.1178.6 [merge] Thu 2012-01-12 16:42:23 +0200
      • weave merge mysql-5.1->mysql-5.1-security
      • Revision #2502.1137.114 [merge] Thu 2012-01-12 14:57:14 +0200
        • empty weave merge
        • Revision #1810.3997.17 [merge] Wed 2012-01-11 10:10:34 +0100
          • Merge from mysql-5.0.95-release
      • Revision #2502.1137.113 [merge] Wed 2012-01-11 18:51:42 +0100
        • Merge from mysql-5.1.61-release
      • Revision #2502.1137.112 Tue 2012-01-10 13:33:45 +0530
        • BUG#11760384 - 52792: mysqldump in XML mode does not dump routines.
        • mysqldump in xml mode did not dump routines, events or triggers.
        • This patch fixes this issue by fixing the if conditions that disallowed the dump of above mentioned objects in xml mode, and added the required code to enable dump in xml format.
      • Revision #2502.1137.111 Tue 2012-01-10 14:18:58 +0900
        • Bug#12400341 INNODB CAN LEAVE ORPHAN IBD FILES AROUND
        • If we meet DB_TOO_MANY_CONCURRENT_TRXS during the execution tab_create_graph from row_create_table_for_mysql(), .ibd file for the table should be created already but was not deleted for the error handling.
        • rb:875 approved by Jimmy Yang
      • Revision #2502.1137.110 Fri 2012-01-06 16:28:24 +0530
        • Bug#12872803 - 62154: FEDERATED.FEDERATED_SERVER TEST FAILS WITH RUN --REPEAT=2 Fixed it to work with "--repeat" option.
      • Revision #2502.1137.109 Fri 2012-01-06 15:46:03 +0530
        • Bug#12872804 - 62155: BINLOG.BINLOG_STM_UNSAFE_WARNING FAILS WHEN RUN WITH --REPEAT=2 Fixed the testcase using timestamp logic while doing grep from the error file.
      • Revision #2502.1137.108 Mon 2012-01-02 06:25:48 +0000
        • BUG#11755281/47032: ERROR 2006 / ERROR 2013 INSTEAD OF PROPER ERROR MESSAGE
        • If init_command was incorrect, we couldn't let users execute queries, but we couldn't report the issue to the client either as it does not expect error messages before even sending a command. Thus, we simply disconnected them without throwing a clear error.
        • We now go through the proper sequence once (without executing any user statements) so we can report back what the problem is. Only then do we disconnect the user.
        • As always, root remains unaffected by this as init_command is (still) not executed for them.
      • Revision #2502.1137.107 Wed 2011-12-28 12:19:30 +0200
        • Bug#13418934 REMOVE HAVE_PURIFY DEPENDENCES FROM INNODB
        • InnoDB: Remove HAVE_purify, UNIV_INIT_MEM_TO_ZERO, UNIV_SET_MEM_TO_ZERO.
        • The compile-time setting HAVE_purify can mask potential bugs. It is being set in PB2 Valgrind runs. We should simply get rid of it, and replace it with UNIV_MEM_INVALID() to declare uninitialized memory as such in Valgrind-instrumented binaries.
        • rb:813 approved by Jimmy Yang
      • Revision #2502.1137.106 Fri 2011-12-23 18:52:44 +0400
        • Fix for bug#11758931 - 51196: SLAVE SQL: GOT AN ERROR WRITING COMMUNICATION PACKETS, ERROR_CODE: 1160
        • Addendum: for some queries table->in_use might be NULL - check it.
      • Revision #2502.1137.105 Fri 2011-12-23 17:22:48 +0400
        • Fix for bug#11758931 - 51196: SLAVE SQL: GOT AN ERROR WRITING COMMUNICATION PACKETS, ERROR_CODE: 1160
        • If idle FEDERATED table is evicted from the table cache when a connection to remote server is lost, query that initiated eviction may fail. If this query is executed by slave SQL thread it may fail as well.
        • An error of close was stored in diagnostics area, which was later attributed to the statement that caused eviction.
        • With this patch FEDERATED clears an error of close.
      • Revision #2502.1137.104 Wed 2011-12-21 21:36:52 -0500
        • Add ChangeLog message.
      • Revision #2502.1137.103 Wed 2011-12-21 21:33:13 -0500
        • Bug#11866367 FPE WHEN SETTING INNODB_SPIN_WAIT_DELAY
        • rb:865 approved by: Jimmy
        • Integer overflow causes division by zero.
    • Revision #2502.1178.5 Mon 2012-01-09 11:28:02 +0100
      • Backport from mysql-trunk of:
        • revno: 3258
        • committer: Jon Olav Hauglid <jon.hauglid@oracle.com>
        • branch nick: mysql-trunk-bug12663165
        • timestamp: Thu 2011-07-14 10:05:12 +0200
        • message: Bug#12663165 SP DEAD CODE REMOVAL DOESN'T UNDERSTAND CONTINUE HANDLERS
      • When stored routines are loaded, a simple optimizer tries to locate and remove dead code. The problem was that this dead code removal did not work correctly with CONTINUE handlers.
      • If a statement triggers a CONTINUE handler, the following statement will be executed after the handler statement has completed. This means that the following statement is not dead code even if the previous statement unconditionally alters control flow. This fact was lost on the dead code removal routine, which ended up with removing instructions that could have been executed. This could then lead to assertions, crashes and generally bad behavior when the stored routine was executed.
      • This patch fixes the problem by marking as live code all stored routine instructions that are in the same scope as a CONTINUE handler.
      • Test case added to sp.test.
    • Revision #2502.1178.4 Thu 2011-12-22 12:55:44 +0200
      • Fix Bug#13510739 63775: SERVER CRASH ON HANDLER READ NEXT AFTER DELETE RECORD.
      • CREATE TABLE bug13510739 (c INTEGER NOT NULL, PRIMARY KEY ©) ENGINE=INNODB; INSERT INTO bug13510739 VALUES (1), (2), (3), (4); DELETE FROM bug13510739 WHERE c=2; HANDLER bug13510739 OPEN; HANDLER bug13510739 READ `primary` = (2); HANDLER bug13510739 READ `primary` NEXT; <-- crash
      • Approved by: Marko (http://bur03.no.oracle.com/rb/r/863/)
    • Revision #2502.1178.3 [merge] Fri 2011-12-16 12:54:28 +0100
      • Empty merge (alignment of version number changesets).
      • Revision #1810.4000.29 [merge] Fri 2011-12-16 12:51:47 +0100
        • Empty merge of identical version number changes.
      • Revision #1810.4000.28 Fri 2011-12-16 12:22:47 +0100
        • Raise version number after cloning 5.0.95
    • Revision #2502.1178.2 [merge] Fri 2011-12-16 12:50:07 +0100
    • Revision #2502.1178.1 Fri 2011-12-16 12:24:05 +0100
      • Raise version number after cloning 5.1.61

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.