[MCOL-3334] parameter optimizer_switch can not be changed Created: 2019-05-28 Updated: 2021-01-11 Resolved: 2021-01-11 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | 1.1.6, 1.1.7, 1.2.3 |
| Fix Version/s: | 5.4.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Maroš Lipták | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | optimizer | ||
| Environment: |
CentOS Linux, Debian Linux, Docker |
||
| Description |
|
Parameter optimizer_switch can not be changed and it is not possible to enable/disable specific optimizations of query optimizer. It is also not possible to enable these optimizations as session variable. Testcase: I tried to configure optimizer_switch parameter also in my.cnf, but this modification was not reflected and all optimizations are always disabled: This bug is affecting me because I need to run some queries on InnoDB tables in MariaDB ColumnStore server. Without query optimizations I always have very silly query plan and complex queries with subselects do not use most of database indexes. When I executed the same query on standard MariaDB with query optimizations enabled in parameter optimizer_switch, all my queries were fast and indexes were used. My test query took 18 minutes on standard MariaDB and 50 hours on MariaDB ColumnStore on the same dataset. This behavior affects only MariaDB ColumnStore. Standard MariaDB without ColumnStore is not affected and optimizer_switch works according to documentation. |
| Comments |
| Comment by Maroš Lipták [ 2019-05-29 ] |
|
It seems that parameter infinidb_vtable_mode = 0 resolves the problem described in this issue. Anyway, I expected at least a warning from database when I executed |
| Comment by Roman [ 2021-01-11 ] |
|
This is a known issue for versions that uses a forked MDB server. Both 10.5 and 10.4 doesn't have this limitation. |