mariadb

Tree: b4781e3072

Author	SHA1	Message	Date
John H. Embretsen	b4781e3072	Fix (preliminary?) for Bug#41502 - MTR v2 should not load plugins during server bootstrap. Adding --loose-skip-falcon option to the mysqld options provided by MTR (v2) during mysqld bootstrap in order to avoid plugin (in this case Falcon) initialization of static variables etc. Options --loose-skip-innodb and --loose-skip-ndbcluster were already included. This will fix Bug#41014 (falcon_bug_39708 fails in pushbuild in 6.0-rpl: "succeeded - should have failed") in the case of MTR v2 (which currently is available in -rpl branches only). MTR v1 (e.g. in main 6.0 branch) does not have this problem. It would be more ideal to remove the --loose-skip-* options and provide a single option disabling all plugin initialization instead, or have bootstrap do this by default. Server modifications are (most likely) needed to be able to do that.	17 years ago
Alfranio Correia	1fe215a7e5	auto merge	17 years ago
Alfranio Correia	3175a06a13	merge 5.1 --> 5.1-rpl	17 years ago
Andrei Elkin	047eced39f	merge 5.1-rpl repository -> 5.1-rpl local	17 years ago
Andrei Elkin	cf99c5ba7c	Bug #40129 no-threads fails on pushbuild in 6.0-rpl, ps_stm_threadpool The test reacted on the way how mtr orders arguments for the server that are gathered from different source. It appeared that the opt-file options were parsed before those that supplied to mtr via its command line. In effect, the opt-file preferences got overriden by the command line and some tests, like no-threads, were caught by surprise: a test expects an option value that had been "hardcoded" into its opt-file but gets another one. This server options ordering problem exists on in the new rpl trees mtr. In option of the author of this patch, the opt-file shall be considered as having the highest preference weight. The opt-file is merely a part of the header of a test, namely a part that can not be technically deployed along the test file. It's unnatural for the test writer to provide both the opt file value and a guard that guarantees the value will be set on in the run time. It's logical to provide either one: the option and its value or the guard. Fixed with relocating parse of the opt file to be the last among sources of the sever's options. A side effect: fixing a small problem of resetting the suite options at time the opt file starts parsing. A side effect: main.log_bin_trust_function_creators_func is disabled to be re-enabled with the fixes for bug#41003 will be merged from the main trees.	17 years ago
Serge Kozlov	de7be3a4ed	Bug#41186: Possible reason of bug is waiting any sql error on slave instead exact number of error. The patch does following: 1) Add new parameter $slave_sql_errno for wait_for_slave_sql_error.inc 2) Add waiting error 1062 (Duplicate PK) for slave SQL thread in test case.	17 years ago
Serge Kozlov	e67ab663f0	Bug#41108: It is a testcase timeout bug so the patch fixes test code in places where timeout can happen: 1. Added waiting start/stop slave to make sure that slave works properly. 2. Added cleanup for slave. 3. Updated related result files.	17 years ago
Serge Kozlov	e5a14618cd	Bug#40142: possible reason of timeout is stopped slave threads before sync_with_master command. The patch add waiting of proper state of slave before sync with master.	17 years ago
Magnus Svensson	7434596b84	Bug#40636 falcon_bug_28095 test fails with "Server failed to restart"	17 years ago
Georgi Kodinov	30d8a8f950	merged 5.0-main -> 5.1-main	17 years ago
Magnus Svensson	2790aceb35	Merge	17 years ago
Magnus Svensson	89f28a77c4	Bug#41061 analyze-warnings times out sporadically in pushbuild	17 years ago
Georgi Kodinov	cb7b5524f9	Disable wait_timeout_func and report bug #41255 .	17 years ago
Vladislav Vaintroub	4dfbf2ec93	Bug#38522: 5 seconds delay when closing application using embedded server The problem here is that embedded server starts handle_thread manager thread on mysql_library_init() does not stop it on mysql_library_end(). At shutdown, my_thread_global_end() waits for thread count to become 0, but since we did not stop the thread it will give up after 5 seconds. Solution is to move shutdown for handle_manager thread from kill_server() (mysqld specific) to clean_up() that is used by both embedded and mysqld. This patch also contains some refactorings - to avoid duplicate code, start_handle_manager() and stop_handle_manager() functions are introduced. Unused variables are eliminated. handle_manager does not rely on global variable abort_loop anymore to stop (abort_loop is not set for embedded). Note: Specifically on Windows and when using DBUG version of libmysqld, the complete solution requires removing obsolete code my_thread_init() from my_thread_var(). This has a side effect that a DBUG statement after my_thread_end() can cause thread counter to be incremented, and embedded will hang for some seconds. Or worse, my_thread_init() will crash if critical sections have been deleted by the global cleanup routine that runs in a different thread. This patch also fixes and revert prior changes for Bug#38293 "Libmysqld crash in mysql_library_init if language file missing". Root cause of the crash observed in Bug#38293 was bug in my_thread_init() described above	17 years ago
Bjorn Munch	97b0eb92e4	Bug #40924 please print timestamp when mtr fails Added text "Test ended at <time>" after failure reports	17 years ago
timothy.smith@sun.com	6a65d019d4	Raise version number after cloning 5.0.74	17 years ago
Sven Sandberg	ee6c9dda9f	BUG#41018: innodb_max_dirty_pages_pct_func fails sporadically: error 28 from storage engine BUG#39382: innodb_max_dirty_pages_pct_func failed with timeout on pushbuild Disabled innodb_max_dirty_pages_pct_func. Please re-enable if the test gets fixed.	17 years ago
Georgi Kodinov	e37c9e7fc9	moved the version to 5.0-main	17 years ago
Georgi Kodinov	9e91c8d6c2	Fixed a bad merge (5.0->5.1) of the fix for bug 37339. There was a missing initialization.	17 years ago
Georgi Kodinov	51938fa015	Addendum to the fix for bug #39178 : Server crash in YaSSL with non-RSA-requesting client if server uses RSA key matchSuite() may not find a match. It will return error in this case. Added a error checking code that will prevent using uninitialized memory in the code based on the assumption that matchSuite() has found a match.	17 years ago
Georgi Kodinov	6969832813	merged addendum to bug 39920 to 5.1-bugteam	17 years ago
Georgi Kodinov	f0c49a6a7d	addendum to the fix for bug #39920 : post-merge test suite fixes	17 years ago
Georgi Kodinov	8f8183eee3	merged bug 39920 and 5.1-main to 5.1-bugteam	17 years ago
Georgi Kodinov	25e641673c	merged 5.1-main -> 5.1-bugteam	17 years ago
Georgi Kodinov	f2a317b663	merged 5.0-main into 5.0-bugteam	17 years ago
Georgi Kodinov	d21c85037f	merged bug 39920 to 5.0-bugteam	17 years ago
Georgi Kodinov	8f36a23c00	Bug #39920 : MySQL cannot deal with Leap Second expression in string literal. Updated MySQL time handling code to react correctly on UTC leap second additions. MySQL functions that return the OS current time, like e.g. CURDATE(), NOW() etc will return :59:59 instead of :59:60 or 59:61. As a result the reader will receive :59:59 for 2 or 3 consecutive seconds during the leap second. This fix will not affect the values returned by UNIX_TIMESTAMP() for leap seconds. But note that when converting the value returned by UNIX_TIMESTAMP() to broken down time the correction of leap seconds will still be applied. Note that this fix will make a difference only if the OS is specially configured to return leap seconds from the OS time calls or when using a MySQL time zone defintion that has leap seconds. Even after this change date/time literals (or other broken down time representations) with leap seconds (ending on :59:60 or 59:61) will still be considered illegal and discarded by the server with an error or a warning depending on the sql mode. Added a test case to demonstrate the effect of the fix.	17 years ago
Georgi Kodinov	1ca8861771	merge of the addenum for bug 37339 to 5.1-bugteam	17 years ago
Georgi Kodinov	be5e6ee031	Addendum to bug #37339 : make the test case portable to windows by using and taking out a full path.	17 years ago
Gleb Shchepa	81cf1a8205	null-merge 5.0-bugteam --> 5.1-bugteam (bug 33461)	17 years ago
Gleb Shchepa	a3cb8c68c3	After-push commit for bug #33461 to make valgrind happy: TABLE_LIST doesn't free Strings in its string lists (TABLE_LIST::use_index and TABLE_liST::ignore_index), so calling c_ptr_safe() on that Strings leads to memleaks. OTOH "safe" c_ptr_safe() is not necessary there and we can replace it with c_ptr().	17 years ago
Ingo Struewing	b2563ca8ff	auto-merge	17 years ago
Matthias Leich	33f51cb67d	Null merge, everything is already in place	17 years ago
Matthias Leich	b9f919e143	Merge of last pushes into GCA tree, no conflicts Diff to actual 5.0-bugteam is revno: 2725 only	17 years ago
Gleb Shchepa	44beb2475d	manual merge 5.0-bugteam --> 5.1-bugteam (bug 33461)	17 years ago
Gleb Shchepa	c762d934cc	Bug #40745 : Error during WHERE clause calculation in UPDATE leads to an assertion failure Any run-time error in stored function (like recursive function call or update of table that is already updating by statement which invoked this stored function etc.) that was used in some expression of the single-table UPDATE statement caused an assertion failure. Multiple-table UPDATE (as well as INSERT and both single- and multiple-table DELETE) are not affected.	17 years ago
Gleb Shchepa	228c913ee5	Bug #33461 : SELECT ... FROM <view> USE INDEX (...) throws an error Even after the fix for bug 28701 visible behaviors of SELECT FROM a view and SELECT FROM a regular table are little bit different: 1. "SELECT FROM regular table USE/FORCE/IGNORE(non existent index)" fails with a "ERROR 1176 (HY000): Key '...' doesn't exist in table '...'" 2. "SELECT FROM view USING/FORCE/IGNORE(any index)" fails with a "ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW". OTOH "SHOW INDEX FROM view" always returns empty result set, so from the point of same behaviour view we trying to use/ignore non existent index. To harmonize the behaviour of USE/FORCE/IGNORE(index) clauses in SELECT from a view and from a regular table the "ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW" message has been replaced with the "ERROR 1176 (HY000): Key '...' doesn't exist in table '...'" message like for tables and non existent keys.	17 years ago
Georgi Kodinov	8479932c42	merged bug 37339 to 5.1-bugteam	17 years ago
Georgi Kodinov	ccc3404f1b	merged bug 37339 to 5.0-bugteam	17 years ago
Georgi Kodinov	0708ad5f98	Bug #37339 : SHOW VARIABLES not working properly with multi-byte datadir The SHOW VARIABLES LIKE .../SELECT @@/SELECT ... FROM INFORMATION_SCHEMA.VARIABLES were assuming that all the system variables are in system charset (UTF-8). However the variables that are settable through command line will have a different character set (character_set_filesystem). Fixed the server to remember the correct character set of basedir, datadir, tmpdir, ssl, plugin_dir, slave_load_tmpdir, innodb variables; init_connect and init_slave variables and use it when processing data.	17 years ago
Ingo Struewing	6baa973d63	merge	17 years ago
Sergey Glukhov	3059c95c65	automerge	17 years ago
Sergey Glukhov	68066aa5a1	error code is changed to satisfy Win NT	17 years ago
Ingo Struewing	57b8f758f0	merge	17 years ago
Sergey Glukhov	a0ddfab9ff	5.0-bugteam->5.1-bugteam merge	17 years ago
Sergey Glukhov	17cd69ccf4	pushbuild failure fixes	17 years ago
He Zhenxing	8c54f0e685	Auto merge	17 years ago
Ingo Struewing	1d69696658	merge	17 years ago
Ingo Struewing	5323968d8f		17 years ago
Tatiana A. Nurnberg	669a8e82a6	auto-merge	17 years ago

1 2 3 4 5 ...

55759 Commits (b4781e30725b1b469267abf001c838f0863d0436) All Branches Search

55759 Commits (b4781e30725b1b469267abf001c838f0863d0436)

All Branches