~hartmut-php/maria/bug-917662 : changes

~hartmut-php/maria/bug-917662 » Changes from revision 3383

From Revision 3383 to 3364

Rev	Summary	Authors	Tags	Date
3383	flush status output after each block (Bug #64048 / LP #91766... flush status output after each block (Bug #64048 / LP #917662) TODO: wouldn't one fflush() at the end be sufficient?	Hartmut Holzgraefe		12 years ago
3382	Added Handler_read_rnd_deleted, number of deleted rows found... Added Handler_read_rnd_deleted, number of deleted rows found with ha_read_rnd_first.	Michael Widenius		12 years ago
3381	Fix the comment. Fix the comment.	sanja at montyprogra...		12 years ago
3380	Fix for LP BUG#908269 Wrong result with subquery in select l... 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.	sanja at montyprogra...		12 years ago
3379	Merge fix for BUG#912510 Merge fix for BUG#912510	Sergey Petrunya		12 years ago
3378	Fixed that --sorted-result in mysql-test-run also works for ... Fixed that --sorted-result in mysql-test-run also works for exec	Michael Widenius		12 years ago
3377	MDEV-77 - possible deadlock in XtraDB async io subsystem on ... MDEV-77 - possible deadlock in XtraDB async io subsystem on Windows. 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.	Vladislav Vaintroub		12 years ago
3376	Fixed LP bug #910083. Fixed LP bug #910083. The patch for bug 685411 erroneously removed a call of engine->set_thd() from Item_subselect::fix_fields().	Igor Babaev		12 years ago
3375	Make test results stable. Make test results stable.	Sergey Petrunya		12 years ago
3374	Update version in configure.in (was forgotten in 5.3.3 relea... Update version in configure.in (was forgotten in 5.3.3 release).	knielsen at knielsen...		12 years ago
3373	Continuation of the efforts in previous cset. Continuation of the efforts in previous cset.	Sergey Petrunya		12 years ago
3372	Make test results stable (they weren't, because filesort() u... Make test results stable (they weren't, because filesort() used to read 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.	Sergey Petrunya		12 years ago
3371	Update test results. Update test results.	Sergey Petrunya		12 years ago
3370	Merge Merge	Sergey Petrunya		12 years ago
3369	Changed a test case from join_cache.test to make it platform Changed a test case from join_cache.test to make it platform independent.	Igor Babaev		12 years ago
3368	Back-ported the patch of the mysql-5.6 code line that Back-ported the patch of the mysql-5.6 code line that 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.	Igor Babaev		12 years ago
3367	Fix version number: it's 5.3.3 Fix version number: it's 5.3.3	Sergey Petrunya	mariadb-5.3.3-rc	12 years ago
3366	Update mysql-test/suite/pbxt/r/subselect.result for the prev... Update mysql-test/suite/pbxt/r/subselect.result for the previous push	Sergey Petrunya		12 years ago
3365	Backport of WL#5953 from MySQL 5.6 Backport of WL#5953 from MySQL 5.6 The patch differs from the original MySQL patch as follows: - All test case differences have been reviewed one by one, and care has been taken to restore the original plan so that each test case executes the code path it was designed for. - A bug was found and fixed in MariaDB 5.3 in Item_allany_subselect::cleanup(). - ORDER BY is not removed because we are unsure of all effects, and it would prevent enabling ORDER BY ... LIMIT subqueries. - ref_pointer_array.m_size is not adjusted because we don't do array bounds checking, and because it looks risky. Original comment by Jorgen Loland: ------------------------------------------------------------- WL#5953 - Optimize away useless subquery clauses For IN/ALL/ANY/SOME/EXISTS subqueries, the following clauses are meaningless: * ORDER BY (since we don't support LIMIT in these subqueries) * DISTINCT * GROUP BY if there is no HAVING clause and no aggregate functions This WL detects and optimizes away these useless parts of the query during JOIN::prepare()	timour at askmonty		12 years ago
3364	BUG#906385: EXPLAIN EXTENDED crashes in TABLE_LIST::print wi... BUG#906385: EXPLAIN EXTENDED crashes in TABLE_LIST::print with limited max_join_size - Take into account that subquery's optimization can fail because of @@max_join_size error.	Sergey Petrunya		12 years ago

Older »