Export - CSV (All fields)
Export - CSV (Current fields)
MDEV-36381
Comment "Procedure of keys generation ..." is in the wrong place
Explain output for SHOW EXPLAIN in the slow log looks useless
Histogram code lacks coverage for non-latin characters
Json_writer produces extra members in output
Incorrect query result caused by WHERE optimization
Wrong query rows of Function PERIOD_ADD
Wrong query result of Function TIMESTAMPADD
Wrong query result of SUBDATE Function
Using FirstMatch() in SEMI JOIN maybe a better choice
Performance Bug: q1 UNION q2 LIMIT 0 executes fully despite empty result
Performance Bug: q1 EXCEPT q2 LIMIT 0 executes fully despite empty result
LIMIT 0 query in the left branch of an EXCEPT operation should perform no action
JOIN ON FALSE query in the left branch of an EXCEPT operation should perform no action
impossible HAVING query in the left branch of an EXCEPT operation should perform no action
impossible WHERE query in the left branch of an EXCEPT operation should perform no action
impossible HAVING query when INTERSECTed with another query should perform no action
MariaDB Fails to Handle EXCEPT Operation Involving Empty Table
MariaDB Fails to Handle INTERSECT Operation Involving Empty Table
Performance Bug When Creating an Empty Table Using q EXCEPT q
Constant subqueries marked as unmergeableMDEV-34013
Ignoring items instead of removing them.
DISTINCT removal in aggregate func do not affect grouping strategy
MDEV-35432
my_snprintf fixes for 11.2+
Add optimizer trace to main/order_by_innodb.test to diagnose debian build issue
analyze table persistent for column (list) inconsistency
Make optimizer handle LCASE(varchar_col)=...
Query Optimization for Counting Foreign Key Records Not Found in Parent Key even after adding indexes
Query that runs for 2ms was not terminated when using MAX_EXECUTION_TIME(1)
Wrong result upon forcing fulltext index on InnoDB table
The opposite HAVING clause intersects and is always an empty set.
The opposite WHERE clause intersects and is always an empty set.
EXCEPT with identical left/right queries isn't eliminated
A query triggers a logic bug and a performance bug
JSON histograms become invalid with a specific (corrupt) value in table
Wrong result: HAVING evaluates NULL = NULL as true, SELECT from view returns extra rows
ANALYZE TABLE in processlist with State NULL
No meaningful error message upon failing ANALYZE .. PERSISTENT with some engines
Histograms are not calculated for geometry columns
Remove unneded code in join_read_always_key()
Time reported as spent in optimizer exceeds total query timeMDEV-28724
innodb_stats_persistent_sample_pages accepting percentage value
Potential performance issue
Left join condition not fully considered, causing warnings during function evaluation on unrelated rows
Precreate static Item_bool() to simplify code
optimize table : Unknown column
Assertion `using_unique_constra int || group_buff <= param->group_buff + param->group_length' failed in create_tmp_table
Wrong result upon JOIN with constant CSV table
Inconsistent name resolution with subquery in HAVING clause
Debug server is extremely slow upon ANALYZE FORMAT=JSON with long literals
join_cache.test shows plans that meaninglessly use rowid filtering