Bug #79450 | Range optimizer utilizes too much memory with many OR conditions | ||
---|---|---|---|
Submitted: | 30 Nov 2015 6:19 | Modified: | 15 Feb 2016 14:34 |
Reporter: | Chaithra Gopala Reddy | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.7.10 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[30 Nov 2015 6:19]
Chaithra Gopala Reddy
[15 Feb 2016 14:34]
Paul DuBois
Noted in 5.7.12, 5.8.0 changelogs. For queries ith many OR conditions, the optimizer now is more memory-efficient and less likely to exceed the memory limit imposed by the range_optimizer_max_mem_size system variable. Consequently, the default value for that variable has been reduced from 1536000 to 8388608.
[15 Feb 2016 17:24]
Paul DuBois
Correction: Default value has been raised, not reduced.