|
------------------------------------------------------------
revno: 4412 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5.33-release timestamp: Mon 2013-07-15 13:41:27 +0200 message: Removed random passwords feature for Bugfix#17160741 (not applicable for 5.5.X) ------------------------------------------------------------ revno: 4411 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5.33-release timestamp: Wed 2013-07-10 19:14:41 +0200 message: Updated spec file for Bug#17080138 ------------------------------------------------------------ revno: 4410 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5.33-release timestamp: Tue 2013-07-09 20:35:26 +0200 message: Removed directory /usr/share/mysql/solaris/postinstall-solaris to resolve build error ------------------------------------------------------------ revno: 4409 tags: clone-5.5.33-build committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.5 timestamp: Fri 2013-07-05 14:30:15 +0530 message: Bug#17033706 SINCE 5.5.32 & 5.6.12, INNODB CANT START WITH OWN MULTI-FILE TABLESPACE ANALYSIS -------- When a tablespace has multiple data files, InnoDB fails to open the tablespace. This is because for each ibd file, the first page is checked.But the first page of all ibd file need not be the first page of the tablespace. Only the first page of the tablespace contains the tablespace header. When we check the first page of an ibd file that is not the first page of the tablespace, then the "tablespace flags" is not really available.This was wrongly used to check if a page is corrupt or not. FIX --- Use the tablespace flags only if the page number is 0 in a tablespace. [Approved by Inaam rb#2836 ] ------------------------------------------------------------ revno: 4408 committer: Venkata Sidagam <venkata.sidagam@oracle.com> branch nick: 5.5 timestamp: Thu 2013-07-04 16:59:09 +0530 message: Bug #16567381 DATETIME FIELD COMPARISONS DO NOT WORK PROPERLY WITH UTF8_UNICODE_CI COLLATION Problem Description: When comparing datetime values with strings, the utf8_unicode_ci collation prevents correct comparisons. Consider the below set of queries, it is not showing any results on a table which has tuples that satisfies the query. But for collation utf8_general_ci it shows one tuple. set names utf8 collate utf8_unicode_ci;; select * from lang where dt='1979-12-09'; Analysis: The comparison function is not chosen in case of collation utf8_unicode_ci. In agg_item_set_converter() because the collation state is having "MY_CS_NONASCII" for collation type "utf8_unicode_ci". The conversion of the collation is happening for the date field. And because of that it is unable to pickup proper compare function(i.e CMP_DATE_WITH_STR). Actually the bug is accidentally introduced by the WL#3759 in 5.5. And in 5.6 it is been fixed by the WL#3664. Fix: I have backported the changes from the file strings/ctype-uca.c which are related to "utf8" introduced by the WL#3664. This change helps in choosing the correct comparison function for all the collations of utf8 charset. ------------------------------------------------------------ revno: 4407 [merge] committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5-merge timestamp: Mon 2013-07-01 15:38:16 +0200 message: merge 5.1 => 5.5 ------------------------------------------------------------ revno: 2661.844.48 committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.1 timestamp: Mon 2013-07-01 15:30:55 +0200 message: Bug#58165: "my_empty_string" gets modified and causes LOAD DATA to fail and Cleanup test case (left outfile in data dir) ------------------------------------------------------------ revno: 4406 committer: Annamalai Gurusami <annamalai.gurusami@oracle.com> branch nick: mysql-5.5 timestamp: Mon 2013-07-01 16:53:30 +0530 message: I have added --innodb_file_per_table=1 InnoDB config option to run i_innodb.innodb_bug16417635 test case. ------------------------------------------------------------ revno: 4405 [merge] committer: Georgi Kodinov <georgi.kodinov@oracle.com> branch nick: B16996656-5.5 timestamp: Fri 2013-06-28 17:13:44 +0300 message: merge back to the 5.5 tree and fix indentation ------------------------------------------------------------ revno: 4400.1.1 committer: Georgi Kodinov <georgi.kodinov@oracle.com> branch nick: B16996656-5.5 timestamp: Wed 2013-06-26 12:19:02 +0300 message: Bug #16996656: UNIQUE OPTION PREFIXES NOT DEPRECATED IN 5.5+ Backported the deprecation warnings from WL#6978 to 5.5 ------------------------------------------------------------ revno: 4404 committer: Mattias Jonsson <mattias.jonsson@oracle.com> branch nick: topush-5.5 timestamp: Fri 2013-06-28 13:18:16 +0200 message: Bug#16589511: MYSQL_UPGRADE FAILS TO WRITE OUT ENTIRE ALTER TABLE ... ALGORITHM= ... STATEMENT The problem was an intermediate buffer of smaller size, which truncated the alter statement. Solved by providing the size of the buffer to be allocated through the function call, instead of using an one-size-fits-all stack buffer inside the function. ------------------------------------------------------------ revno: 4403 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5 timestamp: Thu 2013-06-27 10:08:30 +0200 message: Updated copyright year in the spec file ------------------------------------------------------------ revno: 4402 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5 timestamp: Thu 2013-06-27 09:18:48 +0200 message: - Spec file cleanup for 5.5.33 release to resolve rpm dependencies bugs Bug16785036 - RPM REQUIRES: MISSING PACKAGES ON RHEL 6 (AND PROBABLY 5) Bug 16878042 - CANNOT KEEP SEVERAL MAJOR VERSIONS OF MYSQL IN THE SAME YUM REPOSITORY ------------------------------------------------------------ revno: 4401 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2013-06-26 11:43:44 +0200 message: Cleaned up spec file for 5.5.33 release ------------------------------------------------------------ revno: 4400 committer: Annamalai Gurusami <annamalai.gurusami@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2013-06-26 10:02:42 +0530 message: Bug #16994338 PARSING TAP OUTPUT OF UNIT TEST EXPLAIN_FILENAME-T FAILS Problem: The problem is that explain_filename-t is not printing a test plan as required by the TAP protocol. The test invokes plan(NO_PLAN) but does not invoke exit_status() at the end, where the plan would be printed. Solution: Invoke exit_status() at the end. ------------------------------------------------------------ revno: 4399 committer: bin.x.su@oracle.com branch nick: mysql-5.5-bug16876388 timestamp: Tue 2013-06-25 09:42:54 +0800 message: Bug 16876388 - PLEASE BACKPORT BUG#16208542 TO 5.5 Straight forward backport. Approved by Jimmy, rb#2656 ------------------------------------------------------------ revno: 4398 committer: Vasil Dimov <vasil.dimov@oracle.com> branch nick: mysql-5.5 timestamp: Mon 2013-06-24 13:56:11 +0300 message: Fix nondeterminism in innodb_bug16417635.test ------------------------------------------------------------ revno: 4397 committer: Sujatha Sivakumar <sujatha.sivakumar@oracle.com> branch nick: Bug16753869_mysql-5.5 timestamp: Mon 2013-06-24 11:11:55 +0530 message: Bug#16753869:INCORRECT TRUNCATION OF LONG SET EXPRESSION IN LOAD DATA CAN CAUSE SQL INJECTION Problem: ======= A long SET expression in LOAD DATA is incorrectly truncated when written to the binary log. Analysis: ======== LOAD DATA statements are reconstructed once again before they are written to the binary log. When SET clauses are specified as part of LOAD DATA statement, these SET clause user command strings need to be stored as it is inorder to reconstruct the original user command. At present these strings are stored as part of SET clause item tree's top most Item node's name itself which is incorrect. As an Item::name can be of MAX_ALIAS_NAME (256) size. Hence the name will get truncated to "255". Because of this the rewritten LOAD DATA statement will be terminated incorrectly. When this statment is read back by the mysqlbinlog tool it reads a starting single quote and continuos to read till it finds an ending quote. Hence any statement written post ending quote will be considered as a new statement. Fix: === As name field has length restriction the string value should not be stored in Item::name. A new String list is maintained to store the SET expression values and this list is read during reconstrution. ------------------------------------------------------------ revno: 4396 committer: Prabeen Pradhan <prabeen.pradhan@oracle.com> branch nick: mysql-5.5 timestamp: Mon 2013-06-24 10:42:40 +0530 message: Bug#169900529 :Move nist suite to internal ------------------------------------------------------------ revno: 4395 committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5 timestamp: Fri 2013-06-21 14:18:01 +0200 message: Bug#16945503 ADDRESSSANITIZER BUG IN SYS_VARS Sys_var_keycache inherits from some variant of Sys_var_integer Instances of Sys_var_keycache are initialized using the KEYCACHE_VAR macro, which takes an offset within st_key_cache. However, the Sys_var_integer CTOR treats the offset as if it was within global_system_variables (hidden within some layers of macros and fuction pointers) The result is that we write arbitrary data to arbitrary locations in memory. This all happens during static initialization of global objects, i.e. before we have even entered the main() function. Bug#12325449 TYPO IN CMAKE/DTRACE.CMAKE Fix typo in dtrace.cmake ------------------------------------------------------------ revno: 4394 [merge] committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2013-06-19 14:55:46 +0530 message: Bug#11829813 UNUSED MUTEX COMMIT_THREADS_M [Merge from 5.1] ------------------------------------------------------------ revno: 2661.844.47 committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.1 timestamp: Wed 2013-06-19 14:43:15 +0530 message: Bug#11829813 UNUSED MUTEX COMMIT_THREADS_M Analysis -------- The pthread_mutex commit_threads_m was initiliazed but never used. Fix --- Removing the commit_threads_m mutex from the code base. [ Approved by Marko rb#2475] ------------------------------------------------------------ revno: 4393 committer: Vasil Dimov <vasil.dimov@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2013-06-18 17:12:28 +0300 message: Fix Bug#16907783 5.5 STILL CRASHES IN DICT_UPDATE_STATISTICS WITH CONCURRENT DDL AND I_S QUERIES Skip partially created indexes (ones whose name starts with TEMP_INDEX_PREFIX) from stats gathering. Because InnoDB reports HA_INPLACE_ADD_INDEX_NO_WRITE to MySQL, the latter allows parallel execution of ha_innobase::add_index() and ha_innobase::info(). Reviewed by: Inaam (rb:2613) ------------------------------------------------------------ revno: 4392 [merge] committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2013-06-18 15:49:13 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD TO INCONSISTENCY [ Disabling the test for valgrind ] ------------------------------------------------------------ revno: 2661.844.46 committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.1 timestamp: Tue 2013-06-18 15:48:00 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD TO INCONSISTENCY [ Disabling the test for valgrind ] ------------------------------------------------------------ revno: 4391 committer: Thayumanavar <thayumanavar.x.sachithanantha@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2013-06-18 10:20:30 +0530 message: BUG#14081240 - THREAD POOL BASED CONNECTIONS CAUSE ABORTED_CLIENTS TO BE INCREMENTED. PROBLEM AND FIX: The global status indicate Aborted_clients increment when thread pool connections are gracefully terminated. The thd killed flag is set for all connection cleanup. The fix is not to set thd killed in tp_full_cleanup so that Aborted_clients doesn't increment for normal client disconnects. ------------------------------------------------------------ revno: 4390 committer: bin.x.su@oracle.com branch nick: mysql-5.5 timestamp: Mon 2013-06-17 10:49:53 +0800 message: Fix for test case failure in weekly-trunk regression Not to assume the pages, whose page type is INDEX, with NULL index_name and table_name won't exist during the test Approved by Jimmy in mail ------------------------------------------------------------ revno: 4389 committer: kevin.lewis@oracle.com branch nick: mysql-5.5 timestamp: Fri 2013-06-14 13:33:37 -0500 message: Bug#16914007-INNODB: CHECK TABLE SHOULD MARK AN INDEX AS CORRUPTED IF IT HAS A WRONG COUNT If CHECK TABLE finds that a secondary index contains the wrong number of entries, it used to report an error but not mark the index as corrupt. The error means that the index should be rebuilt, which can be done with ALTER TABLE DROP INDEX and ALTER TABLE ADD INDEX. But just in case the DBA does not pay any attention to the output of CHECK TABLE, the secondary index should be marked as corrupted so that it is not used again. Approved by Inaam in RB:2607 ------------------------------------------------------------ revno: 4388 committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5 timestamp: Fri 2013-06-14 16:38:27 +0200 message: Bug#14834378 ADDRESSSANITIZER BUG IN FILENAME_TO_TABLENAME Backport to 5.5 ------------------------------------------------------------ revno: 4387 committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5 timestamp: Fri 2013-06-14 10:52:23 +0200 message: Bug#16729109: FIX COMPILATION WARNINGS WITH GCC 4.8 Backport to 5.5 (external Bug#69407 Build warnings with mysql) ------------------------------------------------------------ revno: 4386 [merge] committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.5 timestamp: Fri 2013-06-14 16:55:37 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD [ Disabling the test for embedded server ] ------------------------------------------------------------ revno: 2661.844.45 committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.1 timestamp: Fri 2013-06-14 16:44:49 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD [ Disabling the test for embedded server ] ------------------------------------------------------------ revno: 4385 [merge] committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.5 timestamp: Fri 2013-06-14 11:28:29 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD TO INCONSISTENCY [Merge from 5.1] ------------------------------------------------------------ revno: 2661.844.44 committer: Aditya A <aditya.a@oracle.com> branch nick: mysql-5.1 timestamp: Fri 2013-06-14 11:22:05 +0530 message: Bug#13548704 ALGORITHM USED FOR DROPPING PARTITIONED TABLE CAN LEAD TO INCONSISTENCY PROBLEM -------- When we drop a partitoned table , we first gather the information about partitions in the table from the table_name.par file and store it in an internal data structure.Then we delete this file and the data in the table. If the server crashes after deleting the file,then after recovering we cannot access the table .Even we cannot drop the table ,because drop algorithm requires par file to read the partition information. FIX --- 1. We move the part of deleting par file after deleting all the table data from the storage egine. 2. During drop operation if we detect that the par file is missing then we delete the .frm file,since there is no way of recovering without par file. [Approved by Mattias rb#2576 ] ------------------------------------------------------------ revno: 4384 committer: Annamalai Gurusami <annamalai.gurusami@oracle.com> branch nick: mysql-5.5 timestamp: Thu 2013-06-13 11:14:13 +0530 message: Bug #16417635 INNODB FAILS TO MERGE UNDER-FILLED PAGES DEPENDING ON DELETION ORDER Problem: When a InnoDB index page is under-filled, we will merge it with either the left sibling node or the right sibling node. But this checking is incorrect. When the left sibling node is available, even if merging is not possible with left sibling node, we do not check for the possibility of merging with the right sibling node. Solution: If left sibling node is available, and merging with left sibling node is not possible, then check if merge with right sibling node is possible. rb#2506 approved by jimmy & ima. ------------------------------------------------------------ revno: 4383 committer: Sivert Sorumgard <sivert.sorumgaard@oracle.com> branch nick: 5.5-14227431 timestamp: Wed 2013-06-12 09:35:33 +0200 message: Bug #14227431: CHARACTER SET MISMATCH WHEN ALTERING FOREIGN KEYS CAN LEAD TO MISSING TABLES Overview -------- If the FOREIGN_KEY_CHECKS system variable is set to 0, it is possible to break a foreign key constraint by changing the type or character set of the foreign key column, or by dropping the foreign key index (without carrying out corresponding changes on another table in the relationship). If we subsequently set FOREIGN_KEY_CHECKS to 1 and execute ALTER TABLE involving the COPY algorithm on such a table, the following happens: 1) If ALTER TABLE does not contain a RENAME clause, the attempt to install the new version of the table instead of the old one will fail due to the fact that the inconsistency will be detected. An attempt to revert the partially executed alter table operation by restoring the old table definition will fail as well due to FOREIGN_KEY_CHECKS == 1. As a result, the table being altered will be lost. 2) If ALTER TABLE contains the RENAME clause, the inconsistency will not be detected (most probably due to other bugs). But if an attempt to install the new version of the table fails (for example, due to a failure when updating triggers associated with the table), reverting the partially executed alter table by restoring the old table definition will fail too. So the table being altered might be lost as well. Suggested fix ------------- The suggested fix is to temporarily unset the option bit representing FOREIGN_KEY_CHECKS when the old table definition is restored while reverting the partially executed operation. ------------------------------------------------------------ revno: 4382 committer: Saikumar V <saikumar.v@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2013-06-12 12:00:44 +0530 message: Adding rqg grammars to internal folder ------------------------------------------------------------ revno: 4381 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.5 timestamp: Mon 2013-06-10 22:29:41 +0200 message: Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS ------------------------------------------------------------ revno: 4380 [merge] committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2013-06-11 01:20:25 +0530 message: Upmerging the changes from 5.1 for the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS ------------------------------------------------------------ revno: 2661.844.43 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1 timestamp: Tue 2013-06-11 01:13:07 +0530 message: Bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS ------------------------------------------------------------ revno: 4379 committer: Olav Sandstaa <olav.sandstaa@oracle.com> branch nick: 5.5-fix timestamp: Fri 2013-06-07 21:34:34 +0200 message: Bug #16917425 -DBUILD_CONFIG=MYSQL_RELEASE -DWITH_DEBUG=ON FAILS 4 AND SKIPS 27 MTR TESTS Revert fix since it caused mtr tests to not run in pushbuild. ------------------------------------------------------------ revno: 4378 committer: sayantan dutta <sayantan.dutta@oracle.com> branch nick: mysql-5.5 timestamp: Fri 2013-06-07 19:29:56 +0530 message: Bug #16917425 -DBUILD_CONFIG=MYSQL_RELEASE -DWITH_DEBUG=ON FAILS 4 AND SKIPS 27 MTR TESTS ------------------------------------------------------------ revno: 4377 [merge] committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.5 timestamp: Thu 2013-06-06 15:47:55 +0200 message: Null merging the changes of 5.1 branch ------------------------------------------------------------ revno: 2661.844.42 [merge] author: murthy.narkedimilli@oracle.com committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1 timestamp: Tue 2013-06-04 18:17:58 +0200 message: Merge from mysql-5.1.70-release ------------------------------------------------------------ revno: 2661.848.5 tags: mysql-5.1.70 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1.70-release timestamp: Mon 2013-05-13 15:26:11 +0200 message: Merging the changes for Build failure issues from mysql-5.1 ------------------------------------------------------------ revno: 2661.848.4 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1.70-release timestamp: Mon 2013-05-13 15:22:49 +0200 message: Merging the changes for build failures in windows. ------------------------------------------------------------ revno: 2661.848.3 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1.70-release timestamp: Fri 2013-05-10 15:27:03 +0200 message: Merging the changes which fixes the build issue for Windows Builds. Description: Fixing a build issue. The function innobase_convert_to_system_charset() is included only in the builtin InnoDB, and it is missed in InnoDB plugin. Adding this function in InnoDB plugin as well. ------------------------------------------------------------ revno: 2661.848.2 committer: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com> branch nick: mysql-5.1.70-release timestamp: Tue 2013-05-07 09:14:51 +0200 message: Updated spec file to ignore upgrade error message ------------------------------------------------------------ revno: 2661.848.1 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.1.70-release timestamp: Tue 2013-05-07 08:10:09 +0200 message: Merging the changes from 5.1 branch to release branch. Includes bug fixes for: Bug #16722314 FOREIGN KEY ID MODIFIED DURING EXPORT Bug #16754901 PARS_INFO_FREE NOT CALLED IN DICT_CREATE_ADD_FOREIGN_TO_DICTIONARY ------------------------------------------------------------ revno: 4376 [merge] author: ramesh.maddali@oracle.com committer: Build Team <bteam@helheim> branch nick: mysql-5.5 timestamp: Wed 2013-06-05 14:17:01 +0200 message: Merge from mysql-5.5.32-release ------------------------------------------------------------ revno: 4334.1.11 tags: mysql-5.5.32 committer: Murthy Narkedimilli <murthy.narkedimilli@oracle.com> branch nick: mysql-5.5.32-release timestamp: Thu 2013-05-16 17:33:32 +0200 message: Fix for BUG# 16812255: Removing the --random-password option which is supported only for MYSQL server versions 5.6 and above. |