Showing 1-10 of 683 (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
(6482 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
(3171 days)
S35.7, 5.7.20AnyAny IMPORT TABLESPACE fails without cfg file if table indexes are modified
1209012026-07-13
8:53
2026-07-14
13:12
MySQL Server: OptimizerVerified
(2 days)
S38.4.9, 8.4.10AnyAnySELECT ... LOCK IN SHARE MODE returns different row sets depending on index choice under RC/RU
361402008-04-16
14:00
2022-12-04
20:45
MySQL Server: ParserVerified
(6664 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
(1968 days)
S58.0AnyAnyThe query plan changed cause query too long
1163352024-10-10
16:53
2025-09-10
1:54
MySQL Server: OptimizerVerified
(643 days)
S58.0.39AnyAnyMulti-valued index isn't used with some range scans on composite indexes
86622005-02-21
21:31
2018-09-09
20:45
MySQL Server: OptimizerVerified
(6072 days)
S56.0.14, 5.1.12-BK, 4.1.10AnyAnyoptimizer, query takes 3 to 10 times as long when using index
1204412026-05-11
11:29
2026-06-09
20:48
MySQL Server: InnoDB storage engineDocumenting
(38 days)
S2trunk 8.0.24 8.4.9 AnyAnyInnoDB btr_create() can hold page latches for a long time because buf_stat_per_index->inc() may synchronously run ut_loc
803902016-02-16
10:14
2022-10-04
15:10
MySQL Server: OptimizerVerified
(3803 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
(1728 days)
S35.7AnyAnyOptimizer choose index scan but not index range for query with range condition
  Showing 1-10 of 683 (Edit, Save, CSV, Feed) Show Next 10 Entries »