| Showing 1-30 of 73 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 67718 | 2012-11-27 0:54 | 2014-09-24 17:15 | MySQL Server: InnoDB storage engine | Closed (3571 days) | S3 | All | Any | Any | InnoDB drastically under-fills pages in certain conditions |
| 18300 | 2006-03-17 10:45 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Can't repeat (5377 days) | S1 | 5.0.19, 4.1.18 | Any | Any | Memory leak of st_lex (and maybe sp_pcontext?) structures? |
| 110383 | 2023-03-15 21:04 | 2023-06-08 12:30 | MySQL Server: Data Dictionary | Verified (404 days) | S3 | 8.0.32 | Any | Any | After ALTER, TABLESPACE is incorrectly explicit with innodb_file_per_table=0 |
| 26123 | 2007-02-06 19:26 | 2007-05-17 8:28 | MySQL Server: Replication | Duplicate (6186 days) | S2 | 5.0 | Linux (Linux) | Any | Relay logs occasionally get corrupted |
| 27655 | 2007-04-04 18:09 | 2007-04-13 8:31 | Connector / J | Closed (6220 days) | S3 | 5.0.5 | Any | Any | Excessive SHOW VARIABLES LIKE 'tx_isolation' |
| 98496 | 2020-02-05 20:21 | 2023-09-11 7:38 | MySQL Server: JSON | Duplicate (225 days) | S3 | 5.7, 8.0 | Any | Any | JSON columns allow empty string, allowing invalid JSON in binlog row images |
| 97001 | 2019-09-25 0:35 | 2022-01-25 16:57 | MySQL Server: Optimizer | Closed (1481 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 (1645 days) | S3 | 5.7, 5.7.27, 8.0.17 | Any | Any | Differing error for MAX_EXECUTION_TIME depending on query stage at termination |
| 82736 | 2016-08-26 3:01 | 2019-04-08 14:00 | MySQL Server: InnoDB storage engine | Can't repeat (1842 days) | S2 | 5.7.11 | Any | Any | Undo log corruption when using generated columns |
| 42276 | 2009-01-22 19:22 | 2012-05-18 20:19 | MySQL Server: C API (client library) | Verified (5283 days) | S3 | 5.0.75, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | mysql_stmt_bind_result should be not assert with bad MYSQL_BIND |
| 64035 | 2012-01-15 6:07 | 2012-01-19 11:31 | MySQL Server: Replication | Closed (4478 days) | S1 | 5.5.18+ | Any | Any | Several errors in COM_BINLOG_DUMP/mysql_binlog_send crash the server in 5.5.18+ |
| 67024 | 2012-09-30 16:22 | 2012-10-08 14:08 | MySQL Server: Compiling | Closed (4215 days) | S3 | mysql-5.6.7-rc-osx10.7-x86_64 | MacOS | Any | Builds on Mac OS X have incorrect version_compile_machine |
| 67433 | 2012-10-31 5:49 | 2016-05-05 15:57 | MySQL Server: Replication | Closed (3484 days) | S2 | 5.5 (All) | Any | Any | Using SET GLOBAL SQL_LOG_BIN should not be allowed |
| 109401 | 2022-12-16 2:01 | 2023-07-07 12:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (494 days) | S3 | 8.0.31, 5.7.40, 8.0.33 | Any | Any | Rows_query_log_event truncates query due to treating query as C string |
| 82234 | 2016-07-14 21:15 | 2017-11-07 15:15 | MySQL Server: Documentation | Closed (2359 days) | S2 | All | Any | Any | The MEMORY Storage Engine page claims Replication support: Yes |
| 68023 | 2013-01-03 19:42 | 2015-06-03 10:58 | MySQL Server: InnoDB storage engine | Verified (4109 days) | S3 | All | Any | Any | InnoDB reserves an excessive amount of disk space for write operations |
| 68868 | 2013-04-04 21:08 | 2017-07-01 19:00 | MySQL Server: Documentation | Closed (3977 days) | S3 | 5.5, 5.6 | Any | Any | Documentation for InnoDB tablespace flags for file format incorrect |
| 68908 | 2013-04-09 23:07 | 2014-03-11 20:52 | MySQL Server: Locking | Closed (3696 days) | S3 | 5.5.29,5.5.x, 5.1.x | Any | Any | Stray MYF(0) in mysys/thr_alarm.c on line 263 |
| 68909 | 2013-04-09 23:11 | 2013-04-20 16:40 | MySQL Server: Data Types | Closed (4024 days) | S3 | 5.5.29 | Any | Any | In my_MD5Final in mysys/md5.c, ctx is not properly zeroed as intended |
| 69477 | 2013-06-14 19:06 | 2014-09-19 17:06 | MySQL Server: InnoDB storage engine | Closed (3620 days) | S2 | All | Any | Any | InnoDB: Use of large externally-stored fields makes crash recovery lose data |
| 70516 | 2013-10-03 22:28 | 2013-10-04 13:58 | MySQL Server: Compiling | Closed (3854 days) | S3 | 5.0,5.1,5.5,5.6,5.7 | Any | Any | Conditional include of sys/resource.h uses incorrect guard define |
| 81814 | 2016-06-11 16:25 | 2022-04-06 20:59 | MySQL Server: InnoDB storage engine | Closed (748 days) | S3 | 5.7.11 | Any | Any | InnoDB adaptive hash index uses a bad partitioning algorithm for the real world |
| 72015 | 2014-03-12 0:26 | 2014-06-06 8:47 | MySQL Server: InnoDB storage engine | Closed (3609 days) | S3 | 5.6.16, 5.6.18, 5.7.5 | Any | Any | InnoDB calculates estimated row count wildly incorrectly with BLOBs |
| 72594 | 2014-05-09 16:59 | 2014-09-25 12:11 | MySQL Server: InnoDB storage engine | Closed (3599 days) | S3 | 5.6.17 | Any | Any | InnoDB in-place ALTER failures block future ALTERs |
| 79080 | 2015-11-02 20:17 | 2019-07-09 17:37 | MySQL Server: Security: Encryption | Won't fix (1750 days) | S3 | 5.6 | Any | Any | YaSSL does not handle SSL/TLS alerts, resulting in "unknown error number" |
| 73689 | 2014-08-22 15:31 | 2015-05-15 18:45 | MySQL Server: InnoDB storage engine | Closed (3485 days) | S2 | 5.6 | Any | Any | Zero can be a valid InnoDB checksum, but validation will fail later |
| 111112 | 2023-05-22 19:56 | 2023-05-24 15:34 | MySQL Server | Closed (335 days) | S3 | 8.0 | Any | Any | JSON SDI default_value in columns object includes trailing zero bytes |
| 111865 | 2023-07-24 18:39 | 2024-04-23 10:01 | MySQL Server: Documentation | Not a Bug | S3 | 8.0 | Any | Any | Maximum file size limit may reduce 64 TiB InnoDB limit substantially |
| 544 | 2003-05-30 0:25 | 2019-05-14 14:27 | MySQL Server | Not a Bug (7634 days) | S2 | 4.1.0 | Any (All) | Any | LIMIT not accepted with multi-table DELETE |
| 1087 | 2003-08-18 17:54 | 2003-08-19 12:36 | MySQL Server | Closed (7553 days) | S1 | 4.0 | Any (All) | Any | Crash in in_longlong::set() |
| Showing 1-30 of 73 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
