|
------------------------------------------------------------
revno: 3775 tags: clone-5.5.23-build committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5 timestamp: Thu 2012-03-29 15:07:54 +0200 message: Patch for Bug#13805127: Stored program cache produces wrong result in same THD. Background: - as described in MySQL Internals Prepared Stored (http://forge.mysql.com/wiki/MySQL_Internals_Prepared_Stored), the Optimizer sometimes does destructive changes to the parsed LEX-object (Item-tree), which makes it impossible to re-use that tree for PS/SP re-execution. - in order to be able to re-use the Item-tree, the destructive changes are remembered and rolled back after the statement execution. The problem, discovered by this bug, was that the objects representing GROUP-BY clause did not restored after query execution. So, the GROUP-BY part of the statement could not be properly re-initialized for re-execution after destructive changes. Those objects do not take part in the Item-tree, so they can not be saved using the approach for Item-tree. The fix is as follows: - introduce a new array in st_select_lex to store the original ORDER pointers, representing the GROUP-BY clause; - Initialize this array in fix_prepare_information(). - restore the list of GROUP-BY items in reinit_stmt_before_use(). ------------------------------------------------------------ revno: 3774 committer: Sunny Bains <Sunny.Bains@Oracle.Com> branch nick: 5.5 timestamp: Thu 2012-03-29 18:02:08 +1100 message: Bug #13817703 - auto_increment_offset != 1 + innodb_autoinc_lock_mode=1 => bulk inserts fail Fix the calculation of the next autoinc value when offset > 1. Some of the results have changed due to the changes in the allocation calculation. The new calculation will result in slightly bigger gaps for bulk inserts. rb://866 Approved by Jimmy Yang. Backported from mysql-trunk (5.6) ------------------------------------------------------------ revno: 3773 committer: Marc Alff <marc.alff@oracle.com> branch nick: mysql-5.5-bug13898343 timestamp: Wed 2012-03-28 17:54:30 +0200 message: Bug#13898343 THREAD LOOPS ENDLESSLY IN LF_PINBOX_PUT_PINS WHILE HOLDING LOCK_THREAD_COUNT When using the performance schema file io instrumentation in MySQL 5.5, a thread would loop forever inside lf_pinbox_put_pins, when disconnecting. It would also hold LOCK_thread_count while doing so, effectively killing the server. The root cause of the loop in lf_pinbox_put_pins() is a leak of LF_PINS, when used with the filename_hash LF_HASH table in the performance schema. This fix contains the following changes: 1) Added the missing call to lf_hash_search_unpin(), to prevent the leak. 2) In mysys/lf_alloc-pin.c, there was some extra debugging code (MY_LF_EXTRA_DEBUG) written to detect precisely this kind of issues, but it was never used. Replaced MY_LF_EXTRA_DEBUG with DBUG_OFF, so that leaks similar to this one can be always detected in regular debug builds. 3) Backported the fix for the following bug, from 5.6 to 5.5: Bug#13417446 - 63339: INCORRECT FILE PATH IN PEFORMANCE_SCHEMA ON WINDOWS ------------------------------------------------------------ revno: 3772 [merge] committer: Praveenkumar Hulakund <praveenkumar.hulakund@oracle.com> branch nick: mysql_5_5 timestamp: Wed 2012-03-28 13:35:08 +0530 message: Merge from 5.1 to 5.5 ------------------------------------------------------------ revno: 2661.799.47 committer: Praveenkumar Hulakund <praveenkumar.hulakund@oracle.com> branch nick: mysql_5_1 timestamp: Wed 2012-03-28 12:05:31 +0530 message: Bug#11763507 - 56224: FUNCTION NAME IS CASE-SENSITIVE Analysis: ------------------------------- According to the Manual (http://dev.mysql.com/doc/refman/5.1/en/identifier-case-sensitivity.html): "Column, index, stored routine, and event names are not case sensitive on any platform, nor are column aliases." In other words, 'lower_case_table_names' does not affect the behaviour of those identifiers. On the other hand, trigger names are case sensitive on some platforms, and case insensitive on others. 'lower_case_table_names' does not affect the behaviour of trigger names either. The bug was that SHOW statements did case sensitive comparison for stored procedure / stored function / event names. Fix: Modified the code so that comparison in case insensitive for routines and events for "SHOW" operation. As part of this commit, only fixing the test failures due to the actual code fix. ------------------------------------------------------------ revno: 3771 [merge] committer: Sunny Bains <Sunny.Bains@Oracle.Com> branch nick: 5.5 timestamp: Wed 2012-03-28 13:59:06 +1100 message: Merge from mysql-5.1. ------------------------------------------------------------ revno: 2661.799.46 [merge] committer: Sunny Bains <Sunny.Bains@Oracle.Com> branch nick: 5.1 timestamp: Wed 2012-03-28 13:35:44 +1100 message: Merge from mysql-5.0 ------------------------------------------------------------ revno: 1810.4004.13 committer: Sunny Bains <Sunny.Bains@Oracle.Com> branch nick: mysql-5.0 timestamp: Wed 2012-03-28 13:08:25 +1100 message: Bug# 13847885 - PURGING STALLS WHEN PURGE_SYS->N_PAGES_HANDLED OVERFLOWS Change the type of purge_sys_t::n_pages_handled and purge_sys_t::handle_limit to ulonglong from ulint. On a 32 bit system doing ~700 deletes per second the counters can overflow in ~3.5 months, if they are 32 bit. Approved by Jimmy Yang over IM. ------------------------------------------------------------ revno: 3770 [merge] committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.5-merge timestamp: Tue 2012-03-27 14:55:29 +0200 message: merge 5.1 => 5.5 ------------------------------------------------------------ revno: 2661.799.45 committer: Tor Didriksen <tor.didriksen@oracle.com> branch nick: 5.1 timestamp: Tue 2012-03-27 14:39:27 +0200 message: Backport of fix for Bug#12763207 - ASSERT IN SUBSELECT::SINGLE_VALUE_TRANSFORMER ------------------------------------------------------------ revno: 3769 [merge] committer: Praveenkumar Hulakund <praveenkumar.hulakund@oracle.com> branch nick: mysql_5_5 timestamp: Tue 2012-03-27 15:20:14 +0530 message: Merge from 5.1 to 5.5 ------------------------------------------------------------ revno: 2661.799.44 committer: Praveenkumar Hulakund <praveenkumar.hulakund@oracle.com> branch nick: mysql_5_1 timestamp: Tue 2012-03-27 12:42:11 +0530 message: Bug#11763507 - 56224: FUNCTION NAME IS CASE-SENSITIVE Analysis: ------------------------------- According to the Manual (http://dev.mysql.com/doc/refman/5.1/en/identifier-case-sensitivity.html): "Column, index, stored routine, and event names are not case sensitive on any platform, nor are column aliases." In other words, 'lower_case_table_names' does not affect the behaviour of those identifiers. On the other hand, trigger names are case sensitive on some platforms, and case insensitive on others. 'lower_case_table_names' does not affect the behaviour of trigger names either. The bug was that SHOW statements did case sensitive comparison for stored procedure / stored function / event names. Fix: Modified the code so that comparison in case insensitive for routines and events for "SHOW" operation. ------------------------------------------------------------ revno: 3768 committer: Inaam Rana <inaam.rana@oracle.com> branch nick: mysql-5.5 timestamp: Mon 2012-03-26 09:45:01 -0400 message: Bug#13704145: ELIMINATE LRU SCAN WHEN DROPPING A TABLE rb://942 approved by: Marko Makela We don't need to scan LRU for dropping AHI entries when DROPing a table. AHI entries are already removed when we free up extents for the btree. ------------------------------------------------------------ revno: 3767 committer: Bjorn Munch <bjorn.munch@oracle.com> branch nick: main-55 timestamp: Thu 2012-03-22 16:16:11 +0100 message: Merged some fixes from 7.2 release branches ------------------------------------------------------------ revno: 3766 [merge] committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2012-03-21 11:54:14 +0100 message: Upmerge of empty merge changesets from the release backmerges (5.0.96, 5.1.62). Manually resolved conflicts in ".bzr-mysql/default.conf" (tree name) and in "storage/innodb_plugin" (does not belong into 5.5). ------------------------------------------------------------ revno: 2661.799.43 [merge] committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: mysql-5.1 timestamp: Wed 2012-03-21 11:18:21 +0100 message: Upmerge an empty merge changeset (backmerge of 5.0.96 into main 5.0), solve a conflict in ".bzr-mysql/default.conf". ------------------------------------------------------------ revno: 1810.4004.12 [merge] author: karen.langford@oracle.com committer: hery.ramilison@oracle.com branch nick: mysql-5.0 timestamp: Tue 2012-03-20 17:30:49 +0100 message: Merge from mysql-5.0.96-release ------------------------------------------------------------ revno: 2661.799.42 [merge] author: karen.langford@oracle.com committer: hery.ramilison@oracle.com branch nick: mysql-5.1 timestamp: Tue 2012-03-20 17:35:41 +0100 message: Merge from mysql-5.1.62-release ------------------------------------------------------------ revno: 3765 committer: Jimmy Yang <jimmy.yang@oracle.com> branch nick: mysql-5.5 timestamp: Wed 2012-03-21 11:48:12 +0800 message: backport Bug #47707 print some progress messages during shutdown of innodb to mysql-5.5 rb://979 approved by Marko ------------------------------------------------------------ revno: 3764 committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2012-03-20 22:32:10 +0100 message: Fix tree setup: Wrong mailing list for commit mails. ------------------------------------------------------------ revno: 3763 [merge] committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: mysql-5.5 timestamp: Tue 2012-03-20 22:27:49 +0100 message: Merge the 5.5.22 release build into main 5.5, conflict in "sql/filesort.cc" solved manually. ------------------------------------------------------------ revno: 3097.15.38 [merge] tags: mysql-5.5.22 committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: clone-5.5 timestamp: Fri 2012-03-02 13:23:52 +0100 message: Further upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.1 to 5.5. Also, take a syntax fix (C++ style comment in C file) in client/mysqldump.c. ------------------------------------------------------------ revno: 2661.806.22 [merge] tags: mysql-5.1.62 committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: clone-5.1 timestamp: Fri 2012-03-02 13:18:12 +0100 message: Upmerge the yaSSL upgrade (to 2.2.0) from MySQL 5.0 to 5.1. ------------------------------------------------------------ revno: 1810.4002.45 tags: mysql-5.0.96 committer: Joerg Bruehe <joerg.bruehe@oracle.com> branch nick: clone-5.0 timestamp: Fri 2012-03-02 13:12:07 +0100 message: 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. ------------------------------------------------------------ revno: 2661.806.21 committer: Karen Langford <karen.langford@oracle.com> branch nick: mysql-5.1.62-release timestamp: Tue 2012-02-28 17:20:30 +0100 message: AIX builds fail for comments using // |