Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.16, 10.3.15, 10.4.5
-
Linux x64
Description
I found MariaDB behaviour changing according to the number of JOINs in a query.
In this particular application, when the number of JOINs goes from 30 to 31 the execution plan changes, causing potential problems to the execution time and resources management.
The tests were made with few records and with millions of records: apparently this behaviour doesn't depend on the number of records, but when they are millions, the chosen plan considerably slows down execution using gigabytes of temporary files and can crash entire system.
I couldn't find any configuration parameters that drive this behaviour, I don't know if it can be changed
Attachments
Issue Links
- relates to
-
MDEV-11050 Reuse temporary tables created for materialized CTE tables
- Stalled