Showing 1-10 of 486 (Edit, Save, CSV, Feed) Show Next 10 Entries »
ID# Date Updated Type Status Sev Version OS CPU Summary
385502008-08-04
21:47
2018-09-09
20:45
MySQL Server: OptimizerVerified
(5665 days)
S55.0.60, 5.1AnyAnymultiple optimizer bugs for queries with references from preceding table
884182017-11-09
9:12
2017-11-09
10:19
MySQL Server: InnoDB storage engineVerified
(2354 days)
S35.7, 5.7.20AnyAny IMPORT TABLESPACE fails without cfg file if table indexes are modified
361402008-04-16
14:00
2022-12-04
20:45
MySQL Server: ParserVerified
(5847 days)
S35.0.60 and upAnyAnyInconsistent synonymy of USING and TYPE for index creation
1026862021-02-22
12:50
2021-02-24
16:01
MySQL Server: OptimizerVerified
(1151 days)
S58.0AnyAnyThe query plan changed cause query too long
86622005-02-21
21:31
2018-09-09
20:45
MySQL Server: OptimizerVerified
(5255 days)
S56.0.14, 5.1.12-BK, 4.1.10AnyAnyoptimizer, query takes 3 to 10 times as long when using index
803902016-02-16
10:14
2022-10-04
15:10
MySQL Server: OptimizerVerified
(2986 days)
S55.6.30AnyAnyClustered primary key included in index merge may cause higher execution times
1052892021-10-21
14:54
2021-10-25
12:20
MySQL Server: OptimizerVerified
(911 days)
S35.7AnyAnyOptimizer choose index scan but not index range for query with range condition
1129112023-11-01
8:21
2023-11-01
8:56
MySQL Server: OptimizerVerified
(171 days)
S28.1.0, 8.0.35AnyAnyInconsistent results when using PRIMARY and DUPSWEEDOUT
1060032021-12-29
20:06
2022-11-29
7:53
MySQL Server: OptimizerVerified
(842 days)
S38.0.27/5.7AnyAnyMySQL does not use indexes correctly for backwards ORDER BY conditions
969582019-09-20
21:42
2019-09-22
14:28
MySQL Server: OptimizerVerified
(1672 days)
S38.0AnyAnyMySQL optimizer wrongly chooses to use a bigger and inefficient index for query
  Showing 1-10 of 486 (Edit, Save, CSV, Feed) Show Next 10 Entries »