Showing 1-30 of 73 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
82736 | 2016-08-26 3:01 | 2019-04-08 14:00 | MySQL Server: InnoDB storage engine | Can't repeat (1839 days) | S2 | 5.7.11 | Any | Any | Undo log corruption when using generated columns |
18300 | 2006-03-17 10:45 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Can't repeat (5374 days) | S1 | 5.0.19, 4.1.18 | Any | Any | Memory leak of st_lex (and maybe sp_pcontext?) structures? |
1232 | 2003-09-09 3:35 | 2003-12-13 13:51 | MySQL Server | Can't repeat (7434 days) | S3 | 4.1.1 (20030830) | Any | Optimizer chooses wrong plan on simple join | |
422 | 2003-05-13 4:47 | 2003-07-01 2:46 | MySQL Server: Command-line Clients | Can't repeat (7599 days) | S2 | 4.1.x | Any (All) | Any | 4.1 libedit strange behaviour with åäö |
538 | 2003-05-29 13:38 | 2003-06-02 10:21 | MySQL Server | Can't repeat (7628 days) | S2 | 4.1.0 | Linux (Linux) | Any | mysqld.sym.gz not included with 4.1 |
111112 | 2023-05-22 19:56 | 2023-05-24 15:34 | MySQL Server | Closed (332 days) | S3 | 8.0 | Any | Any | JSON SDI default_value in columns object includes trailing zero bytes |
81814 | 2016-06-11 16:25 | 2022-04-06 20:59 | MySQL Server: InnoDB storage engine | Closed (745 days) | S3 | 5.7.11 | Any | Any | InnoDB adaptive hash index uses a bad partitioning algorithm for the real world |
97001 | 2019-09-25 0:35 | 2022-01-25 16:57 | MySQL Server: Optimizer | Closed (1478 days) | S2 | 5.7, 5.7.27 | Any | Any | Dangerous optimization reconsidering_access_paths_for_index_ordering |
96537 | 2019-08-14 17:14 | 2019-10-22 22:11 | MySQL Server: Optimizer | Closed (1642 days) | S3 | 5.7, 5.7.27, 8.0.17 | Any | Any | Differing error for MAX_EXECUTION_TIME depending on query stage at termination |
82234 | 2016-07-14 21:15 | 2017-11-07 15:15 | MySQL Server: Documentation | Closed (2356 days) | S2 | All | Any | Any | The MEMORY Storage Engine page claims Replication support: Yes |
67963 | 2012-12-22 6:51 | 2015-11-02 12:52 | MySQL Server: InnoDB storage engine | Closed (3092 days) | S3 | All | Any | Any | InnoDB wastes almost one extent out of every innodb_page_size pages |
67433 | 2012-10-31 5:49 | 2016-05-05 15:57 | MySQL Server: Replication | Closed (3481 days) | S2 | 5.5 (All) | Any | Any | Using SET GLOBAL SQL_LOG_BIN should not be allowed |
73689 | 2014-08-22 15:31 | 2015-05-15 18:45 | MySQL Server: InnoDB storage engine | Closed (3482 days) | S2 | 5.6 | Any | Any | Zero can be a valid InnoDB checksum, but validation will fail later |
67718 | 2012-11-27 0:54 | 2014-09-24 17:15 | MySQL Server: InnoDB storage engine | Closed (3568 days) | S3 | All | Any | Any | InnoDB drastically under-fills pages in certain conditions |
72594 | 2014-05-09 16:59 | 2014-09-25 12:11 | MySQL Server: InnoDB storage engine | Closed (3596 days) | S3 | 5.6.17 | Any | Any | InnoDB in-place ALTER failures block future ALTERs |
72604 | 2014-05-10 0:16 | 2014-06-10 19:59 | MySQL Server: Documentation | Closed (3602 days) | S3 | Any | Any | Use of mysql_init is not thread safe, but not documented as such | |
72015 | 2014-03-12 0:26 | 2014-06-06 8:47 | MySQL Server: InnoDB storage engine | Closed (3606 days) | S3 | 5.6.16, 5.6.18, 5.7.5 | Any | Any | InnoDB calculates estimated row count wildly incorrectly with BLOBs |
72636 | 2014-05-13 19:24 | 2014-05-27 19:22 | MySQL Server: Documentation | Closed (3616 days) | S3 | 5.6 | Any | Any | Implications of innodb_page_size on compression are undocumented |
69477 | 2013-06-14 19:06 | 2014-09-19 17:06 | MySQL Server: InnoDB storage engine | Closed (3617 days) | S2 | All | Any | Any | InnoDB: Use of large externally-stored fields makes crash recovery lose data |
68908 | 2013-04-09 23:07 | 2014-03-11 20:52 | MySQL Server: Locking | Closed (3693 days) | S3 | 5.5.29,5.5.x, 5.1.x | Any | Any | Stray MYF(0) in mysys/thr_alarm.c on line 263 |
71661 | 2014-02-11 1:07 | 2014-02-18 17:08 | MySQL Server: Documentation | Closed (3714 days) | S3 | Any | Any | Manual describes InnoDB log limits incorrectly | |
70516 | 2013-10-03 22:28 | 2013-10-04 13:58 | MySQL Server: Compiling | Closed (3851 days) | S3 | 5.0,5.1,5.5,5.6,5.7 | Any | Any | Conditional include of sys/resource.h uses incorrect guard define |
68868 | 2013-04-04 21:08 | 2017-07-01 19:00 | MySQL Server: Documentation | Closed (3974 days) | S3 | 5.5, 5.6 | Any | Any | Documentation for InnoDB tablespace flags for file format incorrect |
68909 | 2013-04-09 23:11 | 2013-04-20 16:40 | MySQL Server: Data Types | Closed (4021 days) | S3 | 5.5.29 | Any | Any | In my_MD5Final in mysys/md5.c, ctx is not properly zeroed as intended |
67024 | 2012-09-30 16:22 | 2012-10-08 14:08 | MySQL Server: Compiling | Closed (4212 days) | S3 | mysql-5.6.7-rc-osx10.7-x86_64 | MacOS | Any | Builds on Mac OS X have incorrect version_compile_machine |
64035 | 2012-01-15 6:07 | 2012-01-19 11:31 | MySQL Server: Replication | Closed (4475 days) | S1 | 5.5.18+ | Any | Any | Several errors in COM_BINLOG_DUMP/mysql_binlog_send crash the server in 5.5.18+ |
37885 | 2008-07-04 17:00 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5053 days) | S3 | 5.0/5.1 | Any | Any | row_search_for_mysql may gap lock unnecessarily with SQL comments in query |
20129 | 2006-05-29 18:54 | 2011-02-16 23:43 | MySQL Server: Partitions | Closed (5053 days) | S2 | 5.1.19 | Any | Any | ALTER TABLE ... REPAIR PARTITION ... complains that partition is corrupt |
38883 | 2008-08-19 7:38 | 2019-06-12 8:53 | MySQL Server | Closed (5056 days) | S1 | 5.1.25, 5.1.28, 5.1.30,5.4.3 | Any | Any | thd_security_context is not thread safe, crashes? |
18874 | 2006-04-07 3:28 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5328 days) | S2 | 5.0,21-BK, 5.0.19,5.1.37,5.1.38 | Any (n/a) | Any | Setting myisam_repair_threads > 1, index cardinality always 1 |
Showing 1-30 of 73 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |