mariadb

Tree: ec505e9570

Author	SHA1	Message	Date
Dmitry Lenev	ec505e9570	Fix for bug #57422 "rpl_row_sp003 sporadically fails under heavy load". rpl_row_sp003.test has sporadically failed when run on machine under heavy load or on slow hardware. This patch fixes races in the test which were causing these failures and also removes unnecessary 100 second wait from it.	15 years ago
Konstantin Osipov	eb882fe41b	Fix Bug#56443 remove last 'mysqld_show_column_type' remains sql/sql_show.h: Remove an unused declaration.	15 years ago
Jon Olav Hauglid	231347c435	Merge from mysql-5.5-bugteam to mysql-5.5-runtime No conflicts	15 years ago
Dmitry Shulga	cd81c833a8	A follow up for the patch for Bug#45445, increase stack size to fix an sp-error.test failure on Sun Sparc system.	15 years ago
Alexander Nozdrin	0e1dd99c71	Remove NDB test suites from default-test-suites in MTR.	15 years ago
Alexander Nozdrin	de3d279372	Fix compilation warnings.	15 years ago
Vladislav Vaintroub	10bc97de5c	Do not accept invalid INSTALL_LAYOUT parameter	15 years ago
Vasil Dimov	9f157e6ed0	Merge mysql-5.5-innodb -> mysql-5.5-bugteam	15 years ago
Luis Soares	03d36a1eff	Automerged bzr bundle.	15 years ago
Luis Soares	86de24edee	Fix for crash in mysqld --verbose --help while initializing option for --init-rpl-role. Problem: There are two variables involved in this issue, rpl_status and rpl_role_type. The former is an array containing the description of the possible values for the latter. rpl_status is declared as an enumeration and is stored in a 4 bytes integer. On the other hand, my_getopt, reads enum values into a ulong: (ulong)value= arg; This is overwriting the memory used for rpl_role_type, corrupting the first entry in the array. Fix: We fix this by re-declaring rpl_status as a ulong, so that it has space to accommodate the value "parsed" in my_getopt .	15 years ago
Jimmy Yang	5c15a5a103	Merge from mysql-5.1-innodb to mysql-5.5-innodb	15 years ago
Jimmy Yang	820e1bc6f4	A more complete fix for bug #57345 btr_pcur_store_position abort for load with concurrent lock/unlock tables Approved by Marko	15 years ago
Vasil Dimov	2c986cf2ab	Merge mysql-5.5-innodb -> mysql-5.5-bugteam	15 years ago
unknown	d659cc54f9	Null merge The bug happened only on 5.1	15 years ago
unknown	42f8d2f249	Bug#56226 Table map set to 0 after altering MyISAM table After ALTER TABLE which changed only table's metadata, row-based binlog sometimes got corrupted since the tablemap was unexpectedly set to 0 for subsequent updates to the same table. ALTER TABLE which changed only table's metadata always reset table_map_id for the table share to 0. Despite the fact that 0 is a valid value for table_map_id, this step caused problems as it could have created situation in which we had more than one table share with table_map_id equal 0. If more than one table with table_map_id are 0 were updated in the same statement, updates to these different tables were written into the same rows event. This caused slave server to crash. This bug happens only on 5.1. It doesn't affect 5.5+. This patch solves this problem by ensuring that ALTER TABLE statements which change metadata only never reset table_map_id to 0. To do this it changes reopen_table() to correctly use refreshed table_map_id value instead of using the old one/ resetting it. mysql-test/suite/rpl/r/rpl_alter.result: Add test for BUG#56226 mysql-test/suite/rpl/t/rpl_alter.test: Add test for BUG#56226	15 years ago
unknown	f40acd9a0e	Postfix for BUG#55375 Removed option file and changed result file.	15 years ago
Sunny Bains	7ee98d4fea	Bug# 56982 Assertion Failure from ha_innobase::innobase_peek_autoinc() when auto_inc > 0 Print an error message to stderr an get rid of the assertion. Approved by: Jimmy Yang (over IM)	15 years ago
Alfranio Correia	989b057a6c	null-merge mysql-5.1-bugteam --> mysql-5.5-bugteam	15 years ago
Alfranio Correia	eec585f143	merge mysql-5.1-bugteam (local) --> mysql-5.1-bugteam	15 years ago
unknown	56edc1df7c	Manual merge	15 years ago
unknown	10812c0782	Bug#55375 Transaction bigger than max_binlog_cache_size crashes slave When slave executes a transaction bigger than slave's max_binlog_cache_size, slave will crash. It is caused by the assert that server should only roll back the statement but not the whole transaction if the error ER_TRANS_CACHE_FULL happens. But slave sql thread always rollbacks the whole transaction when an error happens. Ather this patch, we always clear any error set in sql thread(it is different from the error in 'SHOW SLAVE STATUS') and it is cleared before rolling back the transaction. mysql-test/suite/rpl/r/rpl_binlog_max_cache_size.result: SET binlog_cache_size and max_binlog_cache_size for all test cases. Add test case for bug#55375. mysql-test/suite/rpl/t/rpl_binlog_max_cache_size-master.opt: binlog_cache_size and max_binlog_cache_size can be set in the client connection. so remove this option file. mysql-test/suite/rpl/t/rpl_binlog_max_cache_size.test: SET binlog_cache_size and max_binlog_cache_size for all test cases. Add test case for bug#55375. sql/log_event.cc: Some functions don't return the error code, so it is a wrong error code. The error should always be set into thd->main_da. So we use slave_rows_error_report to report the right error. sql/slave.cc: exec_relay_log_event() need call cleanup_context() to clear context. clearup_context() will call end_trans(). Clear thd's error before cleanup_context. It avoid to trigger the assert which cause this bug.	15 years ago
Dmitry Lenev	1af8cfa094	Merged recent changes from mysql-5.5-bugteam into mysql-5.5-runtime tree.	15 years ago
Davi Arnaut	f60106f82d	Bug#45288: pb2 returns a lot of compilation warnings on linux Fix assorted compiler warnings. sql/mysqld.cc: Do not declare max_page_size twice. If large pages support is enabled, the code expects the size in max_desired_page_size. storage/innobase/include/ibuf0ibuf.h: Remove trailing comma. Only present in C99. Approved by: Vasil (via IRC) storage/innobase/include/row0row.h: Remove trailing comma. Only present in C99. Approved by: Vasil (via IRC) strings/my_vsnprintf.c: No need to assert the obvious.	15 years ago
Alexander Barkov	3fdcf2060d	The fix for Bug#55744 GROUP_CONCAT + CASE + ucs return garbage revealed problems in how character set aggregation code works with prepared statements. This patch fixes (hopefully) the problems.	15 years ago
Davi Arnaut	c192be206a	Bug#42733: Type-punning warnings when compiling MySQL -- strict aliasing violations. Due to the extent of aliasing violations in the MySQL source code, at this time it is safer to disable strict aliasing related optimizations in release builds. As of this patch, only GCC enables strict aliasing by default. Hence, use the -fno-strict-aliasing option to disable the aliasing rules. cmake/build_configurations/mysql_release.cmake: Add -fno-strict-aliasing to release builds.	15 years ago
Mats Kindahl	d40abf9130	Merging with mysql-5.5-bugteam.	15 years ago
Mats Kindahl	0a9c39684e	WL#5363: Thread Pool Service Interface Adding a comment to scheduler_types on the default values used.	15 years ago
Mats Kindahl	96daec35d1	Bug #57338 : Extreneous server variable thread_pool_size The server contained code for the server variable and option thread_pool_size, but this server variable where not used anywhere. The variable is probably remains from backporting too much from 6.0 (specifically, the thread pool implementation was not backported from 6.0, which this variable is associated with). This patch eliminates the variable from the server.	15 years ago
Davi Arnaut	15ccca1d55	Bug#56822: Add a thread state for sessions waiting on the query cache lock Only wait for a single debug signal at a time as the signal state is global. Also, do not activate the query cache debug sync points if the thread has no associated THD session. mysql-test/t/query_cache_debug.test: Only wait for a single debug signal at a time as the signal state is global. sql/sql_cache.cc: Do not execute the debug sync point if the thread has no associated THD session. This scenario happens for federated threads.	15 years ago
Tor Didriksen	c8d7a31f35	Bug#57209 valgrind + Assertion failed: dst > buf Buffer overrun when trying to format DBL_MAX mysql-test/r/func_math.result: Add test case for Bug#57209 mysql-test/t/func_math.test: Add test case for Bug#57209 sql/item_strfunc.cc: Allocate a larger buffer for the result.	15 years ago
Vasil Dimov	f9e19fe487	Adjust results files after innodb_file_per_table became 0. In calvin.sun@oracle.com-20101005183830-p81bemgffq8l2en9 the default value of innodb_file_per_table was changed from 1 to 0.	15 years ago
Sergey Vojtovich	8284a3786d	Fixed plugin_load_option failure, when example storage engine is not available. We need to add loose prefix to example load option.	15 years ago
Alexey Botchkov	5f318d4ad9	Bug#30025 Mysqld prints out warnings/errors being run with --no-defaults --help now do no initializations for the --help. Do it for --verbose --help though. per-file comments: sql/mysqld.cc Bug#30025 Mysqld prints out warnings/errors being run with --no-defaults --help quit with the help message at once as --help was given	15 years ago
Alexey Botchkov	42dc7264c0	Bug#35269 mysqlcheck behaves different depending on order of parameters Issue an error if user specifies multiple commands to run. Also there was an unnoticed bug that DO_CHECK was actually 0 which lead to wrong actions in some cases. The mysqlcheck.test contained commands with the suspicious meaning for the above reason. Extra commands removed from there. per-file commands: client/mysqlcheck.c Bug#35269 mysqlcheck behaves different depending on order of parameters Drop with an error if multiple commands. mysql-test/r/mysqlcheck.result Bug#35269 mysqlcheck behaves different depending on order of parameters result completed. mysql-test/t/mysqlcheck.test Bug#35269 mysqlcheck behaves different depending on order of parameters testcase added. not-working commands removed from some mysqlcheck calls.	15 years ago
Davi Arnaut	754471060b	Bug#45288: pb2 returns a lot of compilation warnings on linux Fix warnings related to the use of the deprecated gets() function and passing NULL to non-pointer argument of the sys_var constructor. plugin/auth/dialog.c: Do not use the deprecated gets() function. sql/sys_vars.h: Do not pass NULL to a non-pointer argument of the sys_var constructor.	15 years ago
Davi Arnaut	28be8f919f	Bug#56822: Add a thread state for sessions waiting on the query cache lock Move Query_cache_wait_state declaration out of a debug block.	15 years ago
Luis Soares	fcc741f33f	BUG#54144: manual merged bzr bundle from bug report.	15 years ago
Davi Arnaut	36051b0106	Bug#56822: Add a thread state for sessions waiting on the query cache lock The problem was that threads waiting on the query cache lock are not easily seen due to the lack of a state indicating that the thread is waiting on the said lock. This made it difficult for users to quickly spot (for example, via SHOW PROCESSLIST) a query cache contention problem. The solution is to update the thread state when the query cache lock needs to be acquired. Whenever the lock is to be acquired, the thread state is updated to "Waiting for query cache lock" and is reset once the lock is granted or the wait is interrupted. The intention is to make query cache related hangs more evident. To further investigate query cache related locking problems, one may use PERFORMANCE_SCHEMA to track the overhead associated with the locking bits and determine which particular lock is being a contention point. sql/sql_cache.cc: Set and reset the thread state whenever a attempt to lock the query cache is made. Use DEBUG_SYNC instead of the now unnecessary wait_for_kill hack.	15 years ago
Evgeny Potemkin	7365a389a3	Auto-merged.	15 years ago
Evgeny Potemkin	731dcfc7ff	Bug#57095: Wrongly chosen expression cache type led to a wrong result. The coalesce function returned DATETIME type due to a DATETIME argument, but since it's not a date/time function it can't return correct int value for it. Nevertheless Item_datetime_cache was chosen to cache coalesce's result and that led to a wrong result. Now Item_datetime_cache is used only for those function that could return correct int representation of DATETIME values. mysql-test/r/type_datetime.result: Added a test case for the bug#57095. mysql-test/t/type_datetime.test: Added a test case for the bug#57095. sql/item.cc: Bug#57095: Wrongly chosen expression cache type led to a wrong result. Now Item_datetime_cache is used only for those function that could return correct int representation of DATETIME values.	15 years ago
Dmitry Lenev	eaae675279	Fix for bug#57061 "User without privilege on routine can discover its existence". The problem was that user without any privileges on routine was able to find out whether it existed or not. DROP FUNCTION and DROP PROCEDURE statements were checking if routine being dropped existed and reported ER_SP_DOES_NOT_EXIST error/warning before checking if user had enough privileges to drop it. This patch solves this problem by changing code not to check if routine exists before checking if user has enough privileges to drop it. Moreover we no longer perform this check using a separate call instead we rely on sp_drop_routine() returning SP_KEY_NOT_FOUND if routine doesn't exist. This change also simplifies one of upcoming patches refactoring global read lock implementation. mysql-test/r/grant.result: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Removed DROP PROCEDURE/FUNCTION statements which have started to fail after this fix (correctly). There is no need in dropping routines in freshly created database anyway. mysql-test/r/sp-security.result: Added new test case for bug#57061 "User without privilege on routine can discover its existence". Updated existing tests according to new behaviour. mysql-test/suite/funcs_1/r/innodb_storedproc_06.result: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Now we drop routines under user which has enough privileges to do so. mysql-test/suite/funcs_1/r/memory_storedproc_06.result: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Now we drop routines under user which has enough privileges to do so. mysql-test/suite/funcs_1/r/myisam_storedproc_06.result: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Now we drop routines under user which has enough privileges to do so. mysql-test/suite/funcs_1/storedproc/storedproc_06.inc: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Now we drop routines under user which has enough privileges to do so. mysql-test/t/grant.test: Updated test case after fixing bug#57061 "User without privilege on routine can discover its existence". Removed DROP PROCEDURE/FUNCTION statements which have started to fail after this fix (correctly). There is no need in dropping routines in freshly created database anyway. mysql-test/t/sp-security.test: Added new test case for bug#57061 "User without privilege on routine can discover its existence". Updated existing tests according to new behaviour. sql/sp.cc: Removed sp_routine_exists_in_table() which is no longer used. sql/sp.h: Removed sp_routine_exists_in_table() which is no longer used. sql/sql_parse.cc: When dropping routine we no longer check if routine exists before checking if user has enough privileges to do so. Moreover we no longer perform this check using a separate call instead we rely on sp_drop_routine() returning SP_KEY_NOT_FOUND if routine doesn't exist.	15 years ago
Sergey Vojtovich	85d023eb38	Merge WL#5496 and WL#5341 to 5.5-bugteam.	15 years ago
Luis Soares	06e921818a	BUG#54144: ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE is hard coded The error message for ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE was hard coded. Additionally, the same error was used in three separate error symptoms: 1. when heartbeat period exceeds the value of slave_net_timeout, 2. when it is smaller than 1 milisecond and 3. when it was not in range, ie, either negative or greater than the maximum allowed. We fix this by splitting into three distinct errors and by removing the message from the source code and moving it to the errmsg-utf8.txt file.	15 years ago
Georgi Kodinov	f6e649cfbb	null-merge to 5.5-bugteam	15 years ago
Georgi Kodinov	f0f01d54dd	merge	15 years ago
Georgi Kodinov	ec830356d7	bumped the version to 5.1.53	15 years ago
Jon Olav Hauglid	4bc7ff6993	Merge from mysql-5.5-bugteam to mysql-5.5-runtime No conflicts	15 years ago
Jon Olav Hauglid	e486d21dfc	Merge from mysql-5.5-runtime to mysql-5.5-bugteam No conflicts	15 years ago
Dmitry Shulga	60d558d89d	Fixed bug#45445 - cannot execute procedures with thread_stack set to 128k. mysql-test/collections/default.experimental: Re-enabled test rpl.rpl_row_sp011. sql/sp_head.cc: sp_head::execute() modified: pass constant value 2 STACK_MIN_SIZE instead of 8 * STACK_MIN_SIZE as a second argument value in call to check_stack_overrun.	15 years ago
Vasil Dimov	d4b2f93aac	Merge mysql-5.5-innodb -> mysql-5.5-bugteam	15 years ago

1 2 3 4 5 ...

67224 Commits (ec505e95708ab1bacd0c6afa8e83e411dbe4b0f7) All Branches Search

67224 Commits (ec505e95708ab1bacd0c6afa8e83e411dbe4b0f7)

All Branches