- 13 Jan, 2012 3 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
Sergei Golubchik authored
when looking for tables to delete from
-
- 12 Jan, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 11 Jan, 2012 1 commit
-
-
unknown authored
-
- 10 Jan, 2012 2 commits
-
-
unknown authored
Fix for LP BUG#908269 Wrong result with subquery in select list, EXISTS, constant MyISAM/Aria table. Problem: When building the condition for JOIN::outer_ref_cond the optimizer forgot to take into account that this condition could depend on constant tables as well.
-
Sergey Petrunya authored
-
- 09 Jan, 2012 1 commit
-
-
Michael Widenius authored
mysql-test/r/information_schema_all_engines.result: Update result mysql-test/t/information_schema_all_engines.test: Added --sorted-results as tables in information_schema are not sorted.
-
- 08 Jan, 2012 2 commits
-
-
Vladislav Vaintroub authored
Split IO threads into ones that handle only read completion and ones that handle only write completion, as it was originally done, but got lost with "completion port" patch. The reason we need to have dedicated read and dedicated write threads is that read completion routine can block waiting for write io to complete, and in rare cases where all io threads are handling async reads, it can deadlock.
-
Sergey Petrunya authored
- Create/use do_copy_nullable_row_to_notnull() function for ref access, which is used when copying from not-NULL field in table that can be NULL-complemented to not-NULL field.
-
- 07 Jan, 2012 1 commit
-
-
Sergei Golubchik authored
geometry fields are blobs too.
-
- 06 Jan, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 05 Jan, 2012 2 commits
-
-
Sergei Golubchik authored
-
Sergei Golubchik authored
-
- 06 Jan, 2012 1 commit
-
-
Vladislav Vaintroub authored
- ensure that mtr supressions table is flushed before doing controlled crash and restart - use DBUG_SUICIDE() rather than abort() in partition tests - avoids a crash message/warning - disable perfschema all_instances test on Windows- there are legitimate reasons for output to be different on Unix (some different threads, some different locks), the differences are expected to grow in the future, e.g with threadpool.
-
- 04 Jan, 2012 1 commit
-
-
Sergei Golubchik authored
-
- 03 Jan, 2012 1 commit
-
-
Igor Babaev authored
The patch for bug 685411 erroneously removed a call of engine->set_thd() from Item_subselect::fix_fields().
-
- 02 Jan, 2012 4 commits
-
-
Vladislav Vaintroub authored
-
Sergey Petrunya authored
-
Sergey Petrunya authored
-
Sergey Petrunya authored
-
- 30 Dec, 2011 5 commits
-
-
Sergey Petrunya authored
-
unknown authored
-
Sergey Petrunya authored
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
Note: to build with -fno-rtti as we currently build the server, boost version 1.45 or later is required. (without -fno-rtti, 1.40 is enough)
-
- 29 Dec, 2011 1 commit
-
-
Sergey Petrunya authored
from a heap temptable, which uses pointers to records (that is, byte* pointers) as rowids. This meant that for rows with the same sort key value, the order was determined by memory layout.
-
- 28 Dec, 2011 3 commits
-
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
Fix oqgraph build . Plugin does not need rtti, and does not load if rtti compile settings are different from server's
-
Sergey Petrunya authored
-
- 27 Dec, 2011 6 commits
-
-
Sergey Petrunya authored
-
Vladislav Vaintroub authored
-
Michael Widenius authored
-
Michael Widenius authored
Fixed memory leak printing when doing 'mysqld --version', 'mysqld --debug --help' and 'mysqld --debug --help --verbose' mysys/my_init.c: Moved checking if we should call DBUG_END() before my_thread_end() as otherwise we will not free DBUG variables and files. mysys/thr_lock.c: Fixed compiler warning sql/mysqld.cc: Fixed memory leaks when using mysqld --help and mysqld --version Added --debug as an option that works for all builds. For non debug builds we now get a warning. strings/dtoa.c: Fixed valgrind warning (c could contain data outside of the given string)
-
Vladislav Vaintroub authored
Patch by elenst
-
Vladislav Vaintroub authored
Contributed by Maarten Vanraes (AL13N) Fix things so that chains of certificates work in the server and client certificate files. This only really works for OpenSSL-based builds, as yassl is unable to read multiple certificates from a file. The patch below to yassl/src/ssl.cpp doesn't fix that, but just arranges that the viosslfactories.c patch won't have any ill effects in a yassl build.
-
- 26 Dec, 2011 3 commits
-
-
Vladislav Vaintroub authored
-
Vladislav Vaintroub authored
it is a static library that links with shared libraries, so strictly speaking it should have -fPIC or equivalent flags. Also, it must always build as static no matter whether BUILD_SHARED_LIBS is set.
-
Igor Babaev authored
-
- 24 Dec, 2011 1 commit
-
-
Igor Babaev authored
fixed several defects in the greedy optimization: 1) The greedy optimizer calculated the 'compare-cost' (CPU-cost) for iterating over the partial plan result at each level in the query plan as 'record_count / (double) TIME_FOR_COMPARE' This cost was only used locally for 'best' calculation at each level, and *not* accumulated into the total cost for the query plan. This fix added the 'CPU-cost' of processing 'current_record_count' records at each level to 'current_read_time' *before* it is used as 'accumulated cost' argument to recursive best_extension_by_limited_search() calls. This ensured that the cost of a huge join-fanout early in the QEP was correctly reflected in the cost of the final QEP. To get identical cost for a 'best' optimized query and a straight_join with the same join order, the same change was also applied to optimize_straight_join() and get_partial_join_cost() 2) Furthermore to get equal cost for 'best' optimized query and a straight_join the new code substrcated the same '0.001' in optimize_straight_join() as it had been already done in best_extension_by_limited_search() 3) When best_extension_by_limited_search() aggregated the 'best' plan a plan was 'best' by the check : 'if ((search_depth == 1) || (current_read_time < join->best_read))' The term '(search_depth == 1' incorrectly caused a new best plan to be collected whenever the specified 'search_depth' was reached - even if this partial query plan was more expensive than what we had already found.
-