Sergei Petrunia added a comment - 2015-12-01 13:36 See also https://mariadb.com/kb/en/mariadb/moving-from-oracle-to-mariadb/#comment_1839

Sergei Petrunia added a comment - 2018-03-07 15:50 Note that despite MDEV-9197 being fixed, this particular issue is not fixed on the current 10.3 tree. I was motivated to check again, because I got this question on the "optimizer status update and plans" session in New York. create table t20 (a int, b int, c int); insert into t20 values (1,1,1), (2,2,2), (3,3,3); An example that shows HAVING->WHERE pushdown is not happening: explain format=json select a, max(b) from t20 group by a having a<4;   EXPLAIN: { "query_block": { "select_id": 1, "having_condition": "t20.a < 4", "filesort": { "sort_key": "t20.a", "temporary_table": { "table": { "table_name": "t20", "access_type": "ALL", "rows": 6, "filtered": 100 } } } } } An example shows that if one uses derived table, pushdown will happen: explain format=json select * from (select a, max(b) from t20 group by a) TBL where TBL.a<4;   EXPLAIN: { "query_block": { "select_id": 1, "table": { "table_name": "<derived2>", "access_type": "ALL", "rows": 6, "filtered": 100, "attached_condition": "TBL.a < 4", "materialized": { "query_block": { "select_id": 2, "filesort": { "sort_key": "t20.a", "temporary_table": { "table": { "table_name": "t20", "access_type": "ALL", "rows": 6, "filtered": 100, "attached_condition": "t20.a < 4" } } } } } } } }

Igor Babaev (Inactive) added a comment - 2019-02-24 19:48 Patches for this task was pushed into 10.4