-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 10.2, 10.3, 10.4, 10.5, 10.2.35
-
Component/s: Optimizer
-
Labels:
-
Environment:Centos 7
A query with a large IN () section will be stuck in statistics and use up all RAM. Multiple such queries will crash the server regardless of memory limitations specified in my.cnf
I noticed this in 10.2.35. Downgrading to 10.2.34 fixes the problem
An example is the WordPress "select post_id,meta_value from wp_postmeta where meta_id in (1,2,3 etc ...)" query.
- is caused by
-
MDEV-23811 With large number of indexes optimizer chooses an inefficient plan
-
- Closed
-
- is duplicated by
-
MDEV-24163 Mariadb is restarting after sending this message [Warning] Aborted connection 5889 to db: 'xxxx' user: 'xxxxx' host:
-
- Closed
-
-
MDEV-24173 After minor upgrade to 10.2.35 queries with large IN clauses have performance issues
-
- Closed
-
-
MDEV-24195 Huge memory usage after upgrade
-
- Closed
-