mariadb

Tree: 648b957f42

Author	SHA1	Message	Date
Sergei Petrunia	7711999d8b	MDEV-406: ANALYZE $stmt: add support for BNL join buffering	11 years ago
Sergei Petrunia	c3cfb6910a	MDEV-406: ANALYZE $stmt: Scans that never executed will have r_rows=NULL	11 years ago
Sergei Petrunia	c08de06246	MDEV-406: ANALYZE $stmt: get ANALYZE work for subqueries - "ANALYZE $stmt" should discard select's output, but it should still evaluate the output columns (otherwise, subqueries in select list are not executed) - SHOW EXPLAIN's code practice of calling JOIN::save_explain_data() after JOIN::exec() is disastrous for ANALYZE, because it resets all counters after the first execution. It is stopped = "Late" test_if_skip_sort_order() calls explicitly update their part of the query plan. = Also, I had to rewrite I_S optimization to actually have optimization and execution stages.	11 years ago
Sergei Petrunia	917b22393f	MDEV-406: ANALYZE $stmt - Testcase for ANALYZE UNION - Provide r_rows for union result.	12 years ago
Sergei Petrunia	5621aa3230	MDEV-406: ANALYZE $stmt - Support tracking for UNIONs, temporary-table based ORDER BYs, and both.	12 years ago
Sergei Petrunia	eaba1ba4a5	Re-commit in git: MDEV-406: ANALYZE $stmt - Ported the old patch to new explain code - New SQL syntax (ANALYZE $stmt) - ANALYZE UPDATE/DELETE is now supported (because EXPLAIN UPDATE/DELETE is supported) - Basic counters are calculated for basic kinds of queries (still need to see what happens with join buffer, ORDER BY...LIMIT queries, etc)	12 years ago
Alexander Barkov	3bf20bc7de	A clean-up for "MDEV-3798: [SHOW] EXPLAIN UPDATE/DELETE". Local variable table_name_buffer went out of scope while its content was still being used by a String instance. Moved the variable to the function scope.	12 years ago
Sergey Petrunya	4bed7aa858	MDEV-3798: [SHOW] EXPLAIN UPDATE/DELETE, Memory leak in binlog.binlog_base64_flag: - It turns out, there are statements that will call lex_start(thd->lex) after parsing has been finished. lex_start() will set lex->explain=NULL, which will lose the pointer to already allocated Explain_plan object. - To get rid of this, switch to lazy creation of lex->explain. Now, it is created only when we get a part ot query plan.	12 years ago
Sergey Petrunya	207f008220	Fix valgrind failure caused by calling c_ptr() of an empty StringBuffer<N>.	12 years ago
Sergey Petrunya	105e3ae6c9	MDEV-3798: EXPLAIN UPDATE/DELETE Update the SHOW EXPLAIN code to work with the new architecture (part#1): Before, SHOW EXPLAIN operated on real query plan structures, which meant it had to check when SELECTs are created/deleted. SELECTs would call apc_target->enable() when they got a query plan and disable() when their query plan was deleted. Now, Explain data structure becomes available at once (and we call apc_target->enable()) and then it stays until it is deleted (when that happens, we call apc_target->disable()).	12 years ago
Sergey Petrunya	094f70fd19	MDEV-5106: Server crashes in Explain_union::print_explain on ER_TOO_BIG_SELECT - Don't save UNION's EXPLAIN data if optimization failed with an error. We could end up saving incomplete plan, which will cause a crash when we attempt to print it.	12 years ago
Sergey Petrunya	161d687594	MDEV-3798: EXPLAIN UPDATE/DELETE - Generate correct contents of `Extra` column for UPDATEs/DELETEs that use quick selects - UPDATEs with used_key_is_modified=true will show "Using buffer"	12 years ago
Sergey Petrunya	fda46df620	MDEV-3798: EXPLAIN UPDATE/DELETE - if EXPLAIN DELETE prints "Deleting all rows", it should show the expected number of rows in the rows column.	12 years ago
Sergey Petrunya	98a8642fe8	MDEV-3798: EXPLAIN UPDATE/DELETE - Add support for EXPLAIN INSERT.	12 years ago
Sergey Petrunya	abcf14e595	MDEV-3798: EXPLAIN UPDATE/DELETE - Handle the case when EXPLAIN UPDATE/DELETE has pruned away all partitions.	12 years ago
Sergey Petrunya	72bc6d7364	MDEV-3798: EXPLAIN UPDATE/DELETE - Address review feedback: more renames	12 years ago
Sergey Petrunya	6a7f8af3f9	MDEV-3798: EXPLAIN UPDATE/DELETE - Address review feedback: rename files	12 years ago
Sergey Petrunya	fedf769f0b	MDEV-3798: EXPLAIN UPDATE/DELETE - Address review feedback: rename nearly any name used by the new EXPLAIN code.	12 years ago
Sergey Petrunya	5e4044e92c	MDEV-5093, MDEV-5094: - Make EXPLAIN {PARTITIONS,EXTENDED} {UPDATE,DELETE} work.	12 years ago
Sergey Petrunya	0b69c44e94	MDEV-5067: Valgrind warnings (Invalid read) in QPF_table_access::print_explain - Query plan footprint (in new terms, "EXPLAIN structure") should always keep a copy of key_name. This is because the table might be a temporary table which may be already freed by the time we use query plan footprint.	12 years ago
Sergey Petrunya	7d60030c02	MDEV-5060 Server crashes on EXPLAIN EXTENDED or EXPLAIN PARTITIONS with explain in slow_log - If we're running explain with flags, use the same set of flags to make EXPLAIN columns and contents.	12 years ago
Sergey Petrunya	d998a1635f	MDEV-5045: Server crashes in QPF_query::print_explain with log_slow_verbosity='explain' - Don't print a plan when the statement didn't produce it - Also, add first testcase. We can't check the EXPLAIN from the slow log itself, though.	12 years ago
Sergey Petrunya	2add402891	MDEV-407: Print EXPLAIN [ANALYZE] in the slow query log - Initial implementation.	12 years ago
Sergey Petrunya	ae6e95c498	Code cleanup.	12 years ago
Sergey Petrunya	abf4a910f2	[SHOW] EXPLAIN UPDATE/DELETE - Make QPF structures store data members, not strings. This is not fully possible, because table names (and hence key names, etc) can be deleted, and we have to store strings.	12 years ago
Sergey Petrunya	69c386d9a6	Code cleanup	12 years ago
Sergey Petrunya	befacafd73	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Let Query Plan Footprint store join buffer type in binary form, not string. - Same for LooseScan type.	12 years ago
Sergey Petrunya	c0f7efb1ae	Code cleanup	12 years ago
Sergey Petrunya	8b7bbcf4dc	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Make query plan be re-saved after the first join execution (saving it after JOIN::cleanup is too late because EXPLAIN output is currently produced before that) - Handle QPF allocation/deallocation for edge cases, like unsuccessful BINLOG command. - Work around the problem with UNION's direct subselects not being visible. - Update test results ("Using temporary; Using filesort" are now always printed last in the Extra column) - This cset gets rid of memory leaks/crashes. Some result mismatches still remain.	12 years ago
Sergey Petrunya	79392b9383	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Support "using index for group-by (scanning) " queries	12 years ago
Sergey Petrunya	cebdf3de2e	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Handle another specific case where there the JOIN never had a query plan, but had multiple join->cleanup(full=true) calls - The idea that there can only be MAX_TABLES subuqeries/unions was wrong. Switch QPF_query to using a Dynamic_array. = make Dynamic_array template support size growth. its underlying DYNAMIC_ARRAY supports it. (this part will need more polishing)	12 years ago
Sergey Petrunya	af5e128e50	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Handle statements inside SPs: = regular statements = SET command, which does not have its own statement. - Handle execution of subquery from range optimizer: allocate subquery QPFs on the same MEM_ROOT as the whole query plan was allocated.	12 years ago
Sergey Petrunya	52cfa54c1d	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring Single table UPDATE/DELETE - Correctly print type=SIMPLE vs type=PRIMARY - Handle UPDATE/DELETE of mergeable VIEWs: we get the VIEW's select as the first subquery. (MySQL 5.6 doesn't print it because it finds that the subquery is not attached to any select)	12 years ago
Sergey Petrunya	0a560289aa	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Introduce back QueryPlan/QueryPlanFootprint separation for single-table UPDATEs/DELETEs - Create an empty QueryPlanFootprint for all kinds of queries	12 years ago
Sergey Petrunya	1951d40a88	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring - Make EXPLAIN UPDATE/DELETE use "Query Plan Footprints", too.	12 years ago
Sergey Petrunya	1c6fc3f6b9	[SHOW] EXPLAIN UPDATE/DELETE, code re-structuring Part 2 of: - Pass more tests - select with subselects is now shown with type=PRIMARY where it used to be (incorrectly) 'SIMPLE'	12 years ago
Sergey Petrunya	d2ea53aaed	[SHOW] EXPLAIN UPDATE/DELETE, code re-architecting - Pass more tests - select with subselects is now shown with type=PRIMARY where it used to be (incorrectly) 'SIMPLE'	12 years ago
Sergey Petrunya	d97ca5f56c	[SHOW] EXPLAIN UPDATE/DELETE, code reordering - Add further details, the goal is to pass the testsuite - SJM-nests are not printed correctly yet.	12 years ago
Sergey Petrunya	03691a7771	SHOW EXPLAIN UPDATE/DELETE - Introduce "Query Plan Footprints" (abbrev. QPFs) QPF is a part of query plan that is 1. sufficient to produce EXPLAIN output, 2. can be used to produce EXPLAIN output even after its subquery/union was executed and deleted 3. is cheap to save so that we can always save query plans - This patch doesn't fully address #2, we make/save strings for a number of EXPLAIN's columns. This will be fixed.	12 years ago

19 Commits (648b957f42e0b6600da5456407a563b1218c000b)