Showing 1–30 of 59
ID# Date Updated Type Status Sev Version OS CPU Summary
191952006-04-19
12:09		2018-09-09
20:45		MySQL Server: OptimizerVerified
(6247 days)		S35.0.27-BK, 5.0.21-BK, 5.0.19Linux (Linux)AnyOptimizer does not use proper index for join
255712007-01-12
7:27		2013-03-03
20:45		MySQL Server: Federated storage engineVerifiedS35.0.34-BK, 5.0.27Linux (Linux)AnyEXPLAIN returns incorrect estimation of rows for federated table
255722007-01-12
10:04		2013-03-03
20:45		MySQL Server: Federated storage engineVerifiedS25.0.34-BK, 5.0.27Linux (Linux)AnySHOW INDEX does not report cardinality (always NULL) for FEDERATED table
284042007-05-13
18:33		2018-11-11
14:44		MySQL Server: OptimizerVerified
(2913 days)		S24.0.31, 4.1.25, 4.1.26, 5.0.42-BK, 5.0.46, 5.1.33LinuxAnyOptimizer does not consider index that can be used for ORDER BY
285542007-05-21
9:32		2018-09-09
20:45		MySQL Server: OptimizerVerified
(6373 days)		S34.1.22, 5.0.42-BKAnyAnyOptimizer wrongly prefers index for (col = value) over (PK <= value)
591872010-12-27
15:31		2018-09-09
20:45		MySQL Server: OptimizerVerified
(5789 days)		S25.1.55, 5.6.2-m5AnyAnyWrong result with NULL NOT IN subquery
615512011-06-17
12:26		2011-06-18
8:34		MySQL Server: OptimizerVerified
(5617 days)		S35.1.56AnyAnyLoose index scan is not used for select COUNT(distinct a)
640362012-01-15
15:51		2012-01-15
19:07		MySQL Server: OptimizerVerified
(5405 days)		S3AnyAnyUse non-materializing loose-scan-merge for certain subqueries in FROM with LIMIT
701642013-08-27
13:57		2013-08-28
11:19		MySQL Server: InnoDB storage engineVerified
(4814 days)		S35.1, 5.5, 5.6AnyAnyMisleading comment for the recv_parse_or_apply_log_rec_body() function
705552013-10-08
17:29		2013-10-09
8:03		MySQL Server: OptimizerVerified
(4772 days)		S35.6.14AnyAnyEXPLAIN for INSERT ... SELECT waits for table lock
706292013-10-16
8:27		2017-05-14
20:45		MySQL Server: InnoDB storage engineVerified
(4721 days)		S25.6.14AnyAnyInnoDB updated rec_per_key[] statis not published to the optimizer enough often
706302013-10-16
8:46		2013-10-17
23:04		MySQL Server: InnoDB storage engineVerified
(4764 days)		S35.6.14AnyAnyWhy one can access persistent statistics data while they are changing?
706842013-10-22
8:13		2013-10-22
11:35		MySQL Server: OptimizerVerified
(4759 days)		S35.5.33, 5.6.14AnyAnyHAVING referring to subquery results in WARNING 1292
710912013-12-05
12:52		2013-12-06
11:15		MySQL Server: CSVVerified
(4714 days)		S35.5.33, any, 5.6.15, 5.5.35AnyAnyCSV engine does not properly process "", in quotes
711402013-12-13
9:16		2015-07-31
8:59		MySQL Server: OptimizerVerified
(4112 days)		S25.1, 5.5, 5.6.15, 5.7.7AnyAnyOptimizer does NOT use range checks in typical self-join for InnoDB tables
711462013-12-14
11:34		2021-08-08
20:45		MySQL Server: DocumentationVerified
(4704 days)		S3anyAnyAnyManual does not explain when REPAIR or OPTIMIZE TABLE uses repair by sorting
711892013-12-20
14:56		2021-08-08
20:45		MySQL Server: DocumentationVerified
(4700 days)		S35.5, anyAnyAnyManual does not provide enough details on how loose index scan really works
711912013-12-20
15:30		2013-12-20
20:20		MySQL Server: OptimizerVerified
(4700 days)		S35.5.33AnyAnyLoose index scan is used even though full table scan/tight index scan is faster
711992013-12-21
18:16		2014-01-28
17:45		MySQL Server: OptimizerVerified
(4697 days)		S35.6.14, 5.6.15, 5.5.35AnyAnyOptimizer's estimated number of rows is 2 times wrong for (loose?) index scans
712042013-12-22
15:42		2014-01-06
13:43		MySQL Server: Performance SchemaVerified
(4696 days)		S35.6.14, 5.6.16AnyAnyTiming for stages in P_S is different from what SHOW PROFILE reports
712322013-12-26
11:34		2014-07-04
9:51		MySQL Server: InnoDB storage engineVerified
(4504 days)		S35.6.15AnyAnyWrong behaviour for auto_increment unsigned bigint column approaching max value
712792014-01-02
17:29		2014-01-08
9:33		MySQL Server: Security: PrivilegesVerified
(4687 days)		S35.6AnyAnyMisleading error message for ANALYZE against PERFORMANCE_SCHEMA tables
712802014-01-02
18:21		2014-01-03
8:37		MySQL Server: Information schemaVerified
(4686 days)		S35.6.14, 5.6.15, 5.6.16AnyAnyMisleading error message for ANALYZE against INFORMATION_SCHEMA tables
712932014-01-04
18:35		2021-08-08
20:45		MySQL Server: Performance SchemaVerified
(4683 days)		S35.6AnyAnyManual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values
712942014-01-04
19:24		2014-01-24
16:26		MySQL Server: GeneralVerified
(4683 days)		S35.6AnyAnyManual page for P_S.FILE_INSTANCES table does not explain '~' in FILE_NAME
713122014-01-07
13:21		2014-01-08
12:27		MySQL Server: Information schemaVerified
(4681 days)		S35.6.15AnyAnyWeird warning for MERGE table while accessing I_S.REFERENTIAL_CONSTRAINTS
713552014-01-12
17:22		2014-01-13
5:06		MySQL Server: Information schemaVerified
(4676 days)		S35.6AnyAnyStrange data type is used for name-related columns in some I_S.INNODB_* tables
714772014-01-25
12:10		2014-01-27
15:11		MySQL Server: OptionsVerified
(4662 days)		S35.6.15AnyAnytransaction_allow_batching is available in non-Cluster MySQL Server 5.6
714792014-01-25
15:32		2014-01-30
14:23		MySQL Server: OptionsVerified
(4662 days)		S35.6Windows (Win64)Anysort_buffer_size is limited to 4GB-1 on 64-bit Windows
715132014-01-29
16:08		2014-01-30
6:16		MySQL Server: ErrorsVerified
(4659 days)		S35.6.15, 5.5.35AnyAnymysqld --help --verbose doesn't produce error for wrong innodb_flush_method
Showing 1–30 of 59

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.236 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.