------------------------------------------------------------
revno: 4024 tags: clone-5.1.71-build 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: 4023 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: 4022 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: 4021 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: 4020 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: 4019 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: 4018 [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: 4002.1.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 |