« Show Previous 1000 Entries | Showing 2001-3000 of 5008 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
37783 | 2008-07-01 19:08 | 2008-08-01 21:49 | MySQL Workbench | No Feedback (5719 days) | S3 | 5.0.23 | Windows | Any | Importing a script created by export feature fails if datetime has default set |
22817 | 2006-09-29 9:27 | 2006-11-22 11:40 | MySQL Query Browser | No Feedback (6337 days) | S3 | 1.2.3 beta | MacOS (MAC OS X 10.4.7) | Any | Importing data doens't work correctly with accents and UTF-8 |
55369 | 2010-07-19 15:32 | 2010-08-19 23:00 | MySQL Server: Backup | No Feedback (4971 days) | S1 | 5.0.45-community-nt | Windows (Windows XP) | Any | Importing dump.xml is not working |
80079 | 2016-01-20 17:06 | 2018-07-19 19:13 | MySQL for Windows: MySQL for Excel | Closed (2520 days) | S2 | 1.3.6 | Windows (10 Pro) | Any | Improper handling of Excel date prevents exporting |
102829 | 2021-03-05 14:48 | 2021-03-09 13:33 | MySQL Server: Connection Handling | Not a Bug (1116 days) | S3 | 5.7 | Any | Any | Improperly memory allocation while field metadata sending |
105698 | 2021-11-24 12:46 | 2021-11-24 13:16 | MySQL Server: Clone Plugin | Verified (856 days) | S4 | 8.0 | Any | Any | Improve clone_valid_donor_list flexibility: add wildcard support |
83246 | 2016-10-03 13:43 | 2018-04-04 17:47 | MySQL Server: Document Store: MySQL Shell | Won't fix (2186 days) | S4 | 5.7.15-labs-gr090 | Any | Any | Improve dba.validateInstance() error output to include my.cnf format |
54294 | 2010-06-07 12:18 | 2011-02-16 23:44 | MySQL Cluster Manager: Documentation | Closed (4931 days) | S4 | 1.0.2 | Any | Any | Improve documentation of "set" of mysqld variables in MCM |
64208 | 2012-02-02 12:49 | 2014-02-11 7:15 | MySQL Workbench: Modeling | Closed (3699 days) | S4 | Any | Any | Improve error feedback when encountering errors synchronising model to db | |
46001 | 2009-07-07 11:00 | 2012-05-18 20:19 | MySQL Proxy: Core | Verified | S4 | 0.7, 0.8 | Any | Any | Improve error packet protocol code with respect to sqlstate |
103619 | 2021-05-07 7:02 | 2021-05-10 7:44 | MySQL Server: Installing | Verified (1054 days) | S4 | 8.0 | Any | Any | Improve flexibility of switching 8.0 versions |
108068 | 2022-08-04 8:49 | 2022-08-04 9:57 | MySQL Server: Document Store: MySQL Shell | Verified (603 days) | S4 | 8.0.29 | Any | Any | Improve logging of error "The recovery user name for instance ...." |
77355 | 2015-06-15 8:41 | 2015-06-15 11:56 | MySQL Server: Row Based Replication ( RBR ) | Open (3210 days) | S4 | 5.6.25 | Any | Any | Improve reporting of failure when switching binlog_format modes |
97299 | 2019-10-20 16:08 | 2020-01-17 0:35 | MySQL Server: Optimizer | Closed (1533 days) | S4 | 8.0 | Any | Any | Improve the explain informations for Hash Joins |
87678 | 2017-09-06 9:16 | 2018-02-13 8:22 | MySQL Server: Data Types | Verified (2236 days) | S4 | 5.7.18 | Any | Any | Improve the strict mode for DECIMAL |
106668 | 2022-03-08 10:05 | 2022-03-08 11:18 | MySQL Server: Performance Schema | Verified (752 days) | S4 | 5.6, 5.7, 8.0 | Any | Any | Improve the usability of query digests |
62759 | 2011-10-16 13:46 | 2016-07-14 12:53 | MySQL Server: InnoDB storage engine | Can't repeat (4481 days) | S3 | 5.0.51a | Solaris (5.10) | Any | in mysql.err log , InnoDB: Warning: purge reached the head of the history list, |
44032 | 2009-04-02 6:41 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5031 days) | S3 | 5.0.3+ | Any | Any | In ROW_FORMAT=REDUNDANT, update UTF-8 CHAR to/from NULL is not in-place |
79046 | 2015-10-31 20:43 | 2015-11-03 16:35 | MySQL Server: Documentation | Closed (3069 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Inaccurate description of --log-short-format in the manual |
68962 | 2013-04-15 12:23 | 2013-04-22 17:54 | MySQL Server: Documentation | Closed (3994 days) | S3 | Any | Any | Inaccurate description of innodb_undo_tablespaces in the manual | |
111225 | 2023-05-31 13:23 | 2023-06-06 12:35 | MySQL Server | Not a Bug (297 days) | S5 | MySQL8.0.18,MySQL8.0.28 | Linux | Any | Inaccurate execution plan generation for primary key range query |
36790 | 2008-05-18 23:26 | 2008-05-19 3:34 | MySQL Server: Stored Routines | Not a Bug (5793 days) | S2 | 5.1.24 | Windows | Any | Inappropriate 1406 error generated by stored procedure on INSERT |
48412 | 2009-10-29 16:05 | 2021-05-02 20:45 | Tests: Cluster | Verified (5264 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Incompatible option in test start triggers bug#42928 |
12275 | 2005-07-29 17:48 | 2005-07-29 18:06 | MySQL Server | Not a Bug (6818 days) | S3 | 4.1.10A | Linux (RedHat AS4 IA64) | Any | Incomplete results when performing outer join |
93783 | 2019-01-02 13:50 | 2022-06-16 12:22 | MySQL Server: Replication | Duplicate (1912 days) | S2 | 5.7.22 | Linux (debian 9) | x86 | Incomplete statement from binary log file |
47806 | 2009-10-03 14:44 | 2011-02-16 23:44 | MySQL Server: Documentation | Won't fix (5289 days) | S3 | 5.0, 5.1, 5.4 | Any | Any | Incomplete syntax for TIMESTAMP column format |
20159 | 2006-05-30 23:13 | 2006-08-03 17:46 | MySQL Server | Closed (6448 days) | S3 | 4.1 and later | Any (*) | Any | Inconsistant generation of generic error messages |
69233 | 2013-05-14 17:08 | 2014-12-10 14:19 | MySQL Server: Optimizer | Closed (3437 days) | S1 | 5.6.11 | Any | Any | inconsistant results when odbc date format is used |
31916 | 2007-10-29 14:47 | 2013-03-03 20:45 | MySQL Server: User-defined functions ( UDF ) | Verified (5996 days) | S3 | 5.1 | Any | Any | Inconsistecy between UDF_INIT and UDF_ARGS w/re/to notation of maybe_null |
31066 | 2007-09-17 19:03 | 2012-05-18 20:19 | MySQL Server: General | Duplicate (5968 days) | S3 | 4.1,5.0, 5.1 | Linux | Any | Inconsistencies setting max_binlog_cache_size to 4G |
20434 | 2006-06-13 16:41 | 2006-11-09 16:20 | MySQL Server: Replication | Not a Bug (6350 days) | S3 | Any (any) | Any | Inconsistency for max_allowed_packet | |
105125 | 2021-10-04 16:43 | 2021-10-08 15:25 | MySQL Cluster: Cluster (NDB) storage engine | Verified (904 days) | S3 | 8.0.26 | Any | Any | Inconsistency in checks of long signal to query thread |
58060 | 2010-11-08 19:06 | 2011-02-16 23:44 | MySQL Server: Information schema | Verified (4880 days) | S3 | 5.5.7-rc-debug | Any | Any | Inconsistency in row format reported through I_S |
55760 | 2010-08-05 6:24 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (4985 days) | S3 | 5.1 | Any | Any | Inconsistency of manual and behavior for binlog_direct_non_transactional_udpates |
53452 | 2010-05-05 23:40 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4957 days) | S3 | 5.6.99-m4, 5.5-m3 | Any | Any | Inconsistent behavior of binlog_direct_non_transactional_updates with temp table |
55618 | 2010-07-28 22:42 | 2011-02-16 23:44 | MySQL Cluster: Disk Data | Closed (4866 days) | S2 | mysql-5.1-telco-7.1 | Any | Any | Inconsistent conversion of col. storage format after DROP INDEX from DD tables. |
69714 | 2013-07-10 16:42 | 2016-02-25 12:24 | MySQL Server: Data Types | Closed (3655 days) | S3 | 5.6.11 | Any | Any | Inconsistent DATETIME conversions with fractional seconds |
69437 | 2013-06-10 16:30 | 2013-07-12 12:08 | MySQL Server: InnoDB storage engine | Closed (3913 days) | S4 | 5.7.2 | Windows | Any | inconsistent decimal/hex outputs of thread in innodb status |
48614 | 2009-11-07 19:43 | 2009-11-11 20:54 | MySQL Server: InnoDB Plugin storage engine | Not a Bug (5252 days) | S3 | 5.1.41 | Any | Any | inconsistent enforcement of max value for innodb_old_blocks_pct |
32133 | 2007-11-06 0:16 | 2009-05-12 12:47 | MySQL Administrator | Unsupported (5435 days) | S3 | 1.2.12 | MacOS (Darwin 8.10.3) | Any | Inconsistent graphs in MySQL Administrator |
96508 | 2019-08-12 10:51 | 2019-11-22 16:12 | MySQL Server: DDL | Closed (1681 days) | S3 | 8.0.18-git | Any | Any | Inconsistent naming of foreign keys over NDB tables |
1501 | 2003-10-08 0:23 | 2003-10-08 3:13 | MySQL Server | Closed (7478 days) | S2 | 4.1 Alpha | Windows (Windows 2003) | Any | Inconsistent page in the doublewrite buffer |
19960 | 2006-05-19 23:54 | 2006-10-06 2:51 | MySQL Server | Closed (6384 days) | S2 | 5.0.19, 5.0.20/5.0BK/5.1BK | MacOS (OSX 10.4, Linux (Debian)) | Any | Inconsistent results when joining InnoDB tables using partial UTF8 indexes |
31820 | 2007-10-24 17:19 | 2007-10-30 16:09 | MySQL Server: Data Types | Not a Bug (5995 days) | S2 | 5.0.45 | Any | Any | inconsistent String Bigint comparison |
109335 | 2022-12-12 1:17 | 2022-12-12 7:39 | MySQL Server: User-defined functions ( UDF ) | Verified (473 days) | S3 | 8.0, 8.0.31, 5.7.40 | Linux (mysql:8.0-debian) | Any | Inconsistent UDF behavior with respect to `max_length` |
9686 | 2005-04-06 16:44 | 2008-10-03 13:32 | MySQL Server: Merge storage engine | Can't repeat (5656 days) | S3 | 4.1.15-BK | Linux (Linux) | Any | inconsistent update with selfreference via merge table |
91981 | 2018-08-11 13:02 | 2023-05-10 11:56 | MySQL Server: Security: Privileges | Verified (2046 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | Inconsistent user@host definitions for definer/grantor/grantee columns |
73801 | 2014-09-04 8:30 | 2014-09-19 14:49 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3487 days) | S3 | 7.1.33 | Any | Any | Incorrect \'state\' reported as reason for ::connect_server() failure |
75542 | 2015-01-18 0:50 | 2015-03-30 15:56 | Connector / Python | Closed (3300 days) | S2 | 2.0.2 | Linux | Any | Incorrect arguments to mysqld_stmt_execute error |
89417 | 2018-01-25 15:48 | 2018-03-16 14:51 | MySQL Server: Logging | Verified (2205 days) | S3 | 5.6, 5.7 | Any | Any | Incorrect assert about the checksum length |
76016 | 2015-02-24 6:53 | 2016-02-02 19:54 | MySQL Server: Optimizer | Closed (3290 days) | S2 | 5.7.7 | Any | Any | Incorrect assumption about InnoDB record length in optimizer temporary tables |
837 | 2003-07-13 8:05 | 2008-09-27 8:11 | MySQL Server | Can't repeat (5662 days) | S2 | 4.1 | Linux (Linux) | Any | Incorrect authentication with old client and same length user/db names |
58160 | 2010-11-12 11:33 | 2011-02-16 23:44 | Tests: Replication | Closed (4855 days) | S3 | 5.6 (Erica) | Any | Any | Incorrect behaviour of rpl_change_master |
61408 | 2011-06-04 18:37 | 2011-06-05 17:06 | MySQL Server: Data Types | Not a Bug (4681 days) | S3 | 5.0.90 | Any | Any | incorrect behaviour of user-defined variables |
25562 | 2007-01-11 23:24 | 2016-02-25 12:24 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6273 days) | S3 | 5.0 -> | Linux (Linux) | Any | Incorrect calculation of part size of internal tables for TEXT columns |
47001 | 2009-08-31 5:29 | 2011-02-16 23:44 | MySQL Server: DDL | Can't repeat (5323 days) | S2 | 6.0.11-alpha | Windows | Any | Incorrect check for length of primary key |
6965 | 2004-12-02 20:58 | 2004-12-02 21:15 | MySQL Administrator | Duplicate (7057 days) | S1 | 1.0.15 | Windows (MS XP Pro) | Any | incorrect comma in backup file |
106001 | 2021-12-29 15:35 | 2022-07-28 19:23 | MySQL Server: Replication | Closed (610 days) | S3 | 8.0 | Any | Any | Incorrect computation of MAX_SIZE_LOG_EVENT_STATUS |
14139 | 2005-10-19 12:16 | 2005-11-01 19:42 | MySQL Server | Closed (6723 days) | S3 | 5.0.15-BK, 5.0.13-rc | Linux (Linux, Windows XP) | Any | Incorrect CREATE TABLE (...) SELECT ... behaviour |
15446 | 2005-12-02 20:37 | 2005-12-02 20:45 | MySQL Server | Not a Bug (6692 days) | S3 | 4.1.7 | Windows (Win XP) | Any | Incorrect Date Formatting |
45148 | 2009-05-28 1:03 | 2009-05-28 11:47 | MySQL Migration Toolkit | Duplicate (5419 days) | S3 | 1.1.12 | Windows | Any | incorrect decimal conversion from Postgres 8.1 |
74825 | 2014-11-13 2:29 | 2015-04-10 14:32 | MySQL Server: Documentation | Closed (3276 days) | S3 | 5.7, 5.6, 5.5, 5.1 | Any | Any | Incorrect description of MIXED-mode binlog_format |
29930 | 2007-07-20 12:13 | 2008-01-23 18:45 | MySQL Server: C API (client library) | Not a Bug (5910 days) | S3 | 5.0 bk, 5.1 bk | Any | Any | Incorrect docs of MYSQL_FIELD |
45832 | 2009-06-29 16:53 | 2015-08-19 13:56 | MySQL Server: Views | Closed (3145 days) | S3 | 5.1+ | Any | Any | Incorrect error message when creating unsafe view |
9057 | 2005-03-08 21:54 | 2005-04-13 2:40 | MySQL Server | Closed (6925 days) | S3 | 4.0./5.0 | Any (any) | Any | Incorrect errormsg for too-large char field in table definition |
70382 | 2013-09-20 7:18 | 2013-09-20 11:50 | MySQL Workbench | Duplicate (3843 days) | S3 | 6.0.7.11216 | MacOS (10.8.4) | Any | Incorrect extension when exporting results as Excel file |
22114 | 2006-09-08 11:45 | 2006-09-08 12:01 | MySQL Server | Duplicate (6412 days) | S2 | 5.0 | Windows (Windows) | Any | Incorrect field length from mysql_stmt_bind_result() and mysql_fetch_fields() |
95219 | 2019-05-02 8:05 | 2019-11-04 15:29 | MySQL Server: Data Types | Won't fix (1607 days) | S2 | 8.0.16 | Windows | Any | Incorrect FROM_UNIXTIME value during daylight savings adjustment hour |
21806 | 2006-08-24 8:44 | 2006-12-28 14:24 | MySQL Cluster: Replication | Closed (6301 days) | S3 | Any | Incorrect handling of cluster restart in binlog | ||
100451 | 2020-08-07 8:30 | 2020-08-12 12:09 | MySQL Workbench: Administration | Verified (1325 days) | S3 | 8.0.17 | MacOS | x86 | Incorrect layout in Workbench Error log when log_timestamps=SYSTEM |
78979 | 2015-10-27 13:19 | 2015-10-30 12:24 | MySQL Server: JSON | Closed (3073 days) | S3 | 5.7.9 | Any | Any | Incorrect length check in Field_json::store_binary() |
96433 | 2019-08-06 9:28 | 2019-08-22 12:16 | MySQL Server: Compiling | Closed (1690 days) | S3 | 5.7.27 | Any | Any | incorrect length in read_ok_ex() |
38576 | 2008-08-05 16:07 | 2008-08-05 19:20 | MySQL Server: Optimizer | Can't repeat (5715 days) | S2 | 5.1.23 | Linux (CentOS release 5 (Final)) | Any | Incorrect LIMIT behavior with ORDER BY |
54155 | 2010-06-01 17:13 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5049 days) | S2 | mysql-5.1-telco-6.2 | Any | Any | incorrect ndbrequire in DbtupTrigger.cpp |
85259 | 2017-03-02 1:21 | 2017-03-03 16:40 | MySQL Server: Documentation | Closed (2583 days) | S3 | 5.1,5.5,5.6,5.7 | Any | Any | Incorrect note about blackhole and row based replication |
42680 | 2009-02-09 4:20 | 2018-09-09 20:45 | MySQL Server: DML | Duplicate (4532 days) | S3 | 5.0.77, 5.1.30, 5.1.31, 5.0, 5.1, 6.0 bzr | Any | Any | Incorrect NULL output & max_allowed_packet warning for nested string functions |
54056 | 2010-05-28 6:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5054 days) | S3 | 5.1.47, 5.1.48, 5.6.99 | Any | Any | Incorrect number format in output from SELECT |
89650 | 2018-02-13 13:55 | 2018-02-14 6:56 | MySQL Server: Optimizer | Verified (2235 days) | S3 | 5.7, 8.0, 5.6.39, 5.7.21 | Any | Any | Incorrect ordering with memory tables and long keys |
23342 | 2006-10-16 18:19 | 2007-05-20 6:17 | Connector / NET | Closed (6158 days) | S2 | 5.0.1 | Windows (XP SP2) | Any | Incorrect parsing of Datetime object for MySQL versions below 4.1 |
39408 | 2008-09-11 19:13 | 2011-02-16 23:43 | MySQL Server: General | Closed (5379 days) | S2 | 6.0 | Any | Any | Incorrect path computation for file commands |
104756 | 2021-08-28 7:52 | 2021-10-09 7:02 | MySQL Server: Optimizer | Verified (902 days) | S3 | 5.7.35 | Any | Any | Incorrect query results after index creation |
71777 | 2014-02-20 9:39 | 2014-02-20 10:54 | MySQL Server: Optimizer | Verified (3690 days) | S2 | 5.5.35-0ubuntu0.13.10.1 | Linux (ubuntu0.13.10.1) | Any | Incorrect results are returned with NULLIF() |
47047 | 2009-09-01 15:36 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5289 days) | S2 | 5.1.37, 5.0.85 | Any | Any | incorrect return type length |
76096 | 2015-03-02 14:06 | 2018-11-08 13:58 | MySQL Server: Storage Engines | Closed (1978 days) | S3 | 5.5.14 | Any | Any | Incorrect return value from ha_innobase::max_supported_key_part_length() |
112071 | 2023-08-15 8:56 | 2023-08-16 15:14 | MySQL Server | Not a Bug (226 days) | S3 | 8.0 | Any | Any | Incorrect row size checking when writing an ondisk temptable during cursor fetch |
111007 | 2023-05-11 20:30 | 2023-05-12 13:09 | MySQL Server: Optimizer | Verified (322 days) | S3 | 8.0 | Any | Any | Incorrect rows estimate |
89413 | 2018-01-25 15:15 | 2018-02-07 15:37 | MySQL Server | Closed (2242 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Incorrect sprintf buffer size in sp_head::show_routine_code |
2320 | 2004-01-08 7:29 | 2004-01-08 10:41 | MySQL Server: Documentation | Closed (7386 days) | S3 | Any | Incorrect SQL statement in Old Client appendix | ||
28263 | 2007-05-05 21:23 | 2007-10-22 15:42 | Connector / ODBC | Not a Bug (6003 days) | S2 | 5.0-20070505 | Windows (VISTA 64) | Any | INCORRECT STING VALUE WHEN INSERTING MEMO (ERR 1366) |
36335 | 2008-04-25 8:49 | 2008-04-25 13:59 | MySQL Server: Documentation | Closed (5817 days) | S3 | 4.1+ | Any | Any | Incorrect syntax description for DECIMAL/NUMERIC column definitions |
11120 | 2005-06-06 18:59 | 2005-07-12 16:53 | MySQL Migration Toolkit | Closed (6835 days) | S2 | 1.0.7 Beta | Windows (Windows XP) | Any | Incorrect syntax for creating unique index when migrating from Oracle |
92273 | 2018-09-03 11:16 | 2018-09-17 11:31 | MySQL Server: Data Dictionary | Closed (2023 days) | S3 | Any | Any | Incorrect timezone object used to create dd timestamps for routines and views | |
69438 | 2013-06-11 6:02 | 2014-02-03 11:20 | MySQL Server: InnoDB storage engine | Closed (3761 days) | S3 | 5.6.12 | Any | Any | incorrect transaction active time for recoving transaction after crash |
36780 | 2008-05-17 21:25 | 2009-07-20 9:52 | Connector / J | Not a Bug (5366 days) | S2 | 5.1.5 | Any | Any | incorrect utf8 behavior with mysql 5.1.22 and jdbc driver 5.1.5 |
11540 | 2005-06-24 4:29 | 2005-06-24 20:00 | Connector / J | Closed (6853 days) | S3 | 3.1.8a | Windows (Windows2000 sp4) | Any | Incorrect year conversion in setDate(..) for system that use B.E. year |
67643 | 2012-11-20 1:22 | 2013-04-03 9:58 | MySQL Server: Command-line Clients | Closed (4013 days) | S4 | 5.6 | Any | Any | Increase mysqlbinlog version (3.4 or something higher than 3.3) in MySQL 5.6 |
12756 | 2005-08-23 14:26 | 2008-10-03 20:45 | MySQL Server | Duplicate (5656 days) | S4 | 5.0.7-beta | Windows (Windows 2000) | Any | Increase the maximal length of primary key |
24558 | 2006-11-23 20:35 | 2007-03-30 19:30 | MySQL Server: Data Types | Closed (6209 days) | S3 | 5.1.14-beta-debug/5.0BK | Linux (SUSE 10.0 / 64-bit) | Any | Increasing decimal column length causes data loss |
58734 | 2010-12-04 22:05 | 2011-04-27 17:28 | MySQL Enterprise Backup | Closed (4720 days) | S3 | 3.5.2 | Any | Any | Incremental backup with per-table tablespaces failing on Windows |
68055 | 2013-01-09 9:03 | 2014-05-06 14:11 | MySQL Server: Options | Closed (3615 days) | S2 | mysql-5.5.29 | Any | Any | Indeterminate behavior due to empty option values |
32935 | 2007-12-03 15:30 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | Duplicate (5954 days) | S2 | 5.0.46 | Any | Any | Index Bug Errors |
26530 | 2007-02-21 15:39 | 2007-02-26 8:48 | MySQL Administrator | Closed (6241 days) | S3 | 1.2.9 | Windows (XP) | Any | Index Column Length dialog accepts negativ Integers |
111323 | 2023-06-07 20:22 | 2023-06-13 12:00 | MySQL Server | Can't repeat (291 days) | S3 | 8.0.28 | Any | Any | Index column size too large. The maximum column size is 767 bytes. |
75039 | 2014-11-28 9:56 | 2017-08-07 13:05 | MySQL Workbench: Modeling | Verified (3409 days) | S3 | 6.2.4 | Linux (Ubuntu 14.04 LTE) | Any | Index columns length keeps resetting to "0" |
57453 | 2010-10-14 13:01 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (4884 days) | S1 | 6.0.5-alpha-community | Windows | Any | Index error when order by key |
36455 | 2008-05-01 16:07 | 2008-05-06 17:55 | MySQL Server: Documentation | Closed (5806 days) | S3 | 5.0 bk / 4.1 | Any | Any | index hints and incomplete/partial index names |
57427 | 2010-10-13 10:28 | 2011-02-16 23:44 | MySQL Workbench: SQL Editor | Duplicate (4916 days) | S1 | 5.2.29 | Windows (7 64b) | Any | Index is out of range |
84288 | 2016-12-20 21:07 | 2017-01-04 20:43 | MySQL Server: Documentation | Closed (2641 days) | S3 | 5.7, 8.0 | Any | Any | index limits incorrect and out of date |
17042 | 2006-02-02 15:05 | 2008-10-04 18:33 | MySQL Server | Duplicate (5655 days) | S4 | 5.0.18 (MySQL download) | Any (any Linux) | Any | Index limits too small to be useful in multibyte environments |
2446 | 2004-01-19 9:19 | 2004-01-19 11:48 | MySQL Server: MyISAM storage engine | Closed (7375 days) | S3 | 4.0.17 | Linux (Linux) | Any | Index on TEXT column has problems when string length > prefix length |
35855 | 2008-04-05 21:11 | 2008-11-14 8:13 | MySQL Server: Documentation | Closed (5614 days) | S3 | 5.0.23-community-nt | Windows | Any | Index on text columns not used for ORDER BY |
57429 | 2010-10-13 13:25 | 2011-02-16 23:44 | MySQL Workbench | Duplicate (4916 days) | S3 | 5.2.29-win32 | Windows (7) | Any | Index Out of Range |
58725 | 2010-12-03 20:56 | 2012-05-18 20:19 | MySQL Workbench: SQL Editor | Duplicate (4861 days) | S2 | 5.2.30 CE | Windows (Vista) | Any | index out of range |
59430 | 2011-01-11 19:47 | 2011-02-16 23:44 | MySQL Workbench: SQL Editor | No Feedback (4794 days) | S3 | 5.5.8 | Windows (Windows 7 64 Bit) | Any | Index out of range in MySQL Workbench |
61267 | 2011-05-23 18:18 | 2011-07-16 14:10 | MySQL Server: Information schema | Verified (4642 days) | S3 | 5.5.12 | Windows (64-bit) | Any | Index Prefix Length Completely Ignored |
6166 | 2004-10-19 21:27 | 2004-10-26 7:03 | MySQL Server | Closed (7094 days) | S3 | 4.0,4.1,... | Any | index prefix length of 0 not rejected | |
102597 | 2021-02-15 7:18 | 2021-05-28 15:51 | MySQL Server: DDL | Closed (1036 days) | S1 | 5.7.31, 5.7.33 | Any | Any | Index size larger than 767 bytes allowed for InnoDB with redundant row_format |
2197 | 2003-12-23 9:53 | 2012-05-18 20:19 | MySQL Server | Duplicate (7068 days) | S2 | 5.0-bk | Any | index_merge query causes crash with some server, table and query parameters. | |
22398 | 2006-09-15 17:25 | 2006-09-18 18:12 | MySQL Server: General | Closed (6402 days) | S1 | 5.1.12 | Linux (Linux) | Any | index_merge_innodb.test fails on wrong result file |
22404 | 2006-09-15 18:28 | 2006-09-18 18:13 | MySQL Server: General | Closed (6402 days) | S1 | 5.1.12 | Linux (Linux) | Any | index_merge_myisam.test fails on wrong result file |
39605 | 2008-09-23 16:35 | 2011-02-16 23:43 | MySQL Server: General | Verified (5665 days) | S3 | 5.1.28-rc | Any | Any | index_type dumped by show create table not at the right position |
7725 | 2005-01-07 4:00 | 2005-01-09 9:27 | MySQL Cluster: Cluster (NDB) storage engine | Closed (7019 days) | S3 | 4.1.8 | Linux (Red Hat ES 3.0) | Any | Indexed DATETIME Columns Return Random Results |
87578 | 2017-08-29 10:37 | 2022-05-09 22:17 | Connector / Python | Closed (690 days) | S2 | 8.0.4 | CentOS (7) | Any | IndexError: list index out of range --with-mysql-capi=mysql_config |
35561 | 2008-03-25 21:12 | 2008-03-26 0:10 | MySQL Server: DDL | Closed (5847 days) | S3 | 5.0 | Windows | Any | Indexes don't work correctly with TEXT fields |
6230 | 2004-10-23 18:30 | 2004-10-24 3:03 | Connector / NET | Closed (7096 days) | S2 | 1.0.0 beta | Windows (Windows 2003) | Any | IndexOutOfBounds when reading BLOB with DataReader with GetString(index) |
62416 | 2011-09-12 17:06 | 2011-10-26 16:36 | Connector / NET | Closed (4538 days) | S3 | 6.4.3 | Windows | Any | IndexOutOfRangeException when using return parameter with no name |
21500 | 2006-08-08 10:41 | 2006-08-08 10:41 | MySQL Server | Open | S4 | 5.0 | Linux (Linux (but n/a)) | Any | Indirect parameters for prepared statmets |
78884 | 2015-10-20 12:01 | 2015-10-23 15:38 | MySQL Server: Optimizer | Closed (3080 days) | S3 | 5.5.43,5.7.10 | Any | Any | INET_ATON accepts more than four groups of digits and returns INT bigger than 4G |
2310 | 2004-01-07 9:50 | 2004-01-19 9:10 | MySQL Server | Closed (7375 days) | S3 | 4.0.16 | Linux (Debian Linux) | Any | INET_ATON() handles short-form addresses incorrectly |
15359 | 2005-11-30 17:27 | 2006-01-02 7:50 | MySQL Query Browser | No Feedback (6661 days) | S3 | 1.1.17 | Windows (Windows XP Pro, SP2) | Any | inet_ntoa output truncated when data is grouped |
26720 | 2007-02-28 14:46 | 2007-03-09 1:18 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6230 days) | S2 | 4.1 5.0 5.1 | Linux (Linux) | Any | Infinite loop on unknown signal in logging function |
79654 | 2015-12-16 0:52 | 2020-02-11 4:56 | MySQL Server: Security: Audit | Closed (2046 days) | S3 | 5.6 | Any | Any | Information missing in LOG connect events |
12501 | 2005-08-10 15:18 | 2005-09-14 12:00 | MySQL Server | Can't repeat (6771 days) | S2 | 5.0.11 | MacOS (OS X 10.4 (x86), also FreeBSD) | Any | Information schema problems |
27190 | 2007-03-15 21:30 | 2007-03-15 21:54 | MySQL Server: Compiling | Can't repeat (6224 days) | S2 | 5.0.37 | Linux (Linux (tar.gz download)) | Any | Information Schema test fails |
8156 | 2005-01-27 5:26 | 2005-02-15 13:10 | MySQL Server | Closed (6982 days) | S1 | MacOS (Mac OSX 11.6, Darwin 7.6.0) | Any | information_schema and lowercase_table3 fail on OSX | |
107739 | 2022-07-02 21:28 | 2022-07-05 12:07 | MySQL Server: Information schema | Verified (634 days) | S4 | Any | Any | Information_schema TABLES.AVG_ROW_LENGTH does not return the average row length. | |
27397 | 2007-03-23 13:12 | 2012-05-18 20:19 | MySQL Server: Tests | Duplicate (5997 days) | S3 | 5.0.37 Community | Linux (Linux, Solaris 8 SPARC,Solaris 10 x86) | Any | information_schema test fails |
27035 | 2007-03-11 16:53 | 2008-01-03 15:21 | MySQL Server: Packaging | Closed (5930 days) | S3 | 5.0.37 binaries | Linux (Linux, Mac OS X) | Any | information_schema test fails on MySQL 5.0.37 |
14064 | 2005-10-17 7:11 | 2005-10-19 1:45 | MySQL Server | Closed (6736 days) | S2 | 5.0.15 | Other (SCO_SV) | Any | information_schema test fails on opnsrv6c |
7215 | 2004-12-13 1:22 | 2005-02-23 14:06 | MySQL Server | Closed (6974 days) | S3 | 5.0.3-alpha-debug | Linux (SUSE 9.2) | Any | information_schema: columns are longtext instead of varchar |
11057 | 2005-06-03 0:30 | 2005-07-20 15:05 | MySQL Server | Closed (6827 days) | S3 | 5.0.7-beta-debug | Linux (SUSE 9.2) | Any | information_schema: columns table has some questionable contents |
42832 | 2009-02-13 13:45 | 2009-02-13 14:02 | MySQL Server: Information schema | Not a Bug (5523 days) | S3 | 5.1.30-debug | Linux (OpenSuse 10.3) | Any | INFORMATION_SCHEMA.COLUMNS reports wrong CHARACTER_MAXIMUM_LENGTH for SET |
84757 | 2017-01-31 21:05 | 2017-03-03 1:00 | MySQL Server: Information schema | No Feedback (2584 days) | S3 | 5.5.43-enterprise-commercial-advanced | CentOS (6.5) | Any | information_schema.tables doesn't report corrupted tables when columns are spec |
35427 | 2008-03-19 8:38 | 2011-02-16 23:43 | MySQL Server: Information schema | Closed (5251 days) | S3 | 5.1.23-rc, 5.0.56 | Any | Any | INFORMATION_SCHEMA.TABLES.TABLE_CATALOG is NULL, should be "def" |
28002 | 2007-04-21 15:39 | 2007-04-23 4:18 | MySQL Server: Information schema | Not a Bug (6185 days) | S1 | Windows | Any | information_schema/character_sets/utf8_general_ci maxlen wrong | |
15803 | 2005-12-16 5:19 | 2011-02-16 23:43 | MySQL Server | No Feedback (5265 days) | S4 | 5.0.16 | Windows (Windows XP) | Any | Information_schemas not standard compliant |
51378 | 2010-02-22 9:57 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5001 days) | S3 | 5.1+ | Any | Any | Init "ref_length" to correct value, in case an out of bound MySQL primary_key |
99892 | 2020-06-15 15:32 | 2021-01-22 13:07 | MySQL Server: Data Dictionary | Closed (1163 days) | S3 | 8.0.18, 8.0.20 | Any | Any | initialize with innodb_page_size=4096 gets "Specified key was too long" errors |
39657 | 2008-09-26 2:46 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | Verified (5069 days) | S4 | 5.0.40 Enterprise | Linux (Cent OS 4.5) | Any | InnDB - 2 simple update queries cause deadlock. |
34591 | 2008-02-15 11:56 | 2016-10-09 20:45 | MySQL Server: Optimizer | Duplicate (5182 days) | S1 | 6.0.4 | Any | Any | Innob crash in row_sel_store_mysql_rec() on multi-table delete |
53472 | 2010-05-06 23:27 | 2012-04-09 22:43 | MySQL Enterprise Backup | Can't repeat (4372 days) | S3 | mysql-5.1-meb | Linux | Any | Innobackup followed by ibbackup test execution in mtr changes the file format. |
81429 | 2016-05-16 8:53 | 2016-05-16 9:05 | MySQL Server: Command-line Clients | Verified (2874 days) | S1 | 5.7.12 | CentOS (7) | Any | innochecksum rises an error with encryption enabled table at page 1 |
62563 | 2011-09-28 15:12 | 2011-10-18 22:08 | MySQL Server: InnoDB storage engine | Closed (4546 days) | S2 | 5.5.8 | Windows (XP) | Any | INNOD DB CRASH |
107900 | 2022-07-18 7:07 | 2022-07-18 12:44 | MySQL Server: InnoDB storage engine | Verified (620 days) | S5 | 8.0 | Any | Any | InnoDB crash recovery optimize |
59699 | 2011-01-24 16:03 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4795 days) | S3 | 5.5 | Any | Any | InnoDB - Hidden bug would cause a crash for unknown tablespace flags. |
113706 | 2024-01-22 11:46 | 2024-01-22 13:20 | MySQL Server: Errors | Can't repeat (67 days) | S3 | mysql Ver 8.0.35 for Linux on 86_64 | Linux (Centos 7 Linux ) | x86 (x86_64) | InnoDB : Corruption of an index tree which stopped mysqld service |
93326 | 2018-11-24 17:40 | 2018-11-25 1:30 | MySQL Server: InnoDB storage engine | Unsupported (1951 days) | S2 | 5.7.23-23 | Ubuntu (16.04.5 LTS) | x86 (NPTL 2.23) | InnoDB ACTIVE (PREPARED) threads were marked/converted to XA transactions |
46650 | 2009-08-11 12:51 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5031 days) | S1 | 5.1,5.4 | Any | Any | Innodb assertion autoinc_lock == lock in lock_table_remove_low on INSERT SELECT |
20521 | 2006-06-17 20:32 | 2006-06-20 9:54 | MySQL Server | Duplicate (6492 days) | S1 | 5.1.11-Beta | Linux (RHEL4) | Any | InnoDB Assertion failure ALWAYS row0sel.c line 2378 |
90637 | 2018-04-26 2:54 | 2018-04-27 13:08 | MySQL Server: InnoDB storage engine | Can't repeat (2163 days) | S3 | 5.7.17 | Any | Any | innodb assertion failure at !trx_commit_disallowed when async io turned off |
6174 | 2004-10-20 9:56 | 2004-10-30 7:51 | MySQL Server: InnoDB storage engine | Duplicate (7090 days) | S1 | standard-4.0.21 | Linux (Slackware Linux 10.0) | Any | InnoDB assertion failure in ha_innodb.cc causes server shutdown |
61972 | 2011-07-25 19:15 | 2011-10-27 17:44 | MySQL Server: InnoDB storage engine | Duplicate (4537 days) | S2 | 5.5.11, 5.5.14, 5.5.15 | Linux (Alpine Linux 2.2.2) | Any | InnoDB assertion failure in page_is_comp(next_page) in btr0pcur.c line 423 |
50366 | 2010-01-15 14:09 | 2013-10-02 17:30 | MySQL Server: InnoDB storage engine | Closed (3831 days) | S1 | 5.0.90, 5.1.43 | Any (CentOS 5.4 x86-64, XP) | Any | InnoDB Assertion failure when converting from MyISAM to InnoDB |
90402 | 2018-04-12 7:39 | 2018-11-26 13:43 | MySQL Server: InnoDB storage engine | Closed (1950 days) | S3 | mysql-5.7.17 | Any | Any | innodb async io error handling in io_event |
4516 | 2004-07-12 15:01 | 2004-07-12 15:12 | MySQL Server: InnoDB storage engine | Not a Bug (7200 days) | S3 | mysql-standard-4.0.20-pc-linux-i686 | Linux (Redhat 7.3) | Any | innodb buffer pool limit |
52020 | 2010-03-12 21:49 | 2017-12-22 8:24 | MySQL Server: InnoDB storage engine | Closed (4468 days) | S3 | 5.0, 5.1.46 | Any | Any | InnoDB can still deadlock on just INSERT...ON DUPLICATE KEY |
35713 | 2008-03-31 18:52 | 2008-04-04 10:12 | MySQL Server: Installing | Not a Bug (5838 days) | S3 | 5.0.51a | Linux | Any | InnoDB cannot allocate memory anymore after increasing RAM |
29475 | 2007-07-02 4:28 | 2007-08-17 14:06 | MySQL Server: InnoDB storage engine | Won't fix (6069 days) | S5 | 5.0 | Any | Any | InnoDB COMPACT format addition reduces INSERT performance by 10 % |
34590 | 2008-02-15 11:51 | 2018-09-09 20:45 | MySQL Server: Optimizer | Duplicate (5182 days) | S3 | 6.0.4 | Any | Any | Innodb crash in build_template() on multi-table delete |
38231 | 2008-07-18 19:15 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5033 days) | S1 | 5.0.22, 5.0.42, 5.0.66a, 5.1.23, 5.1.28, 6.0.5 | Any | Any | Innodb crash in lock_reset_all_on_table() on TRUNCATE + LOCK / UNLOCK |
35045 | 2008-03-04 17:34 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Can't repeat (5411 days) | S3 | 6.0-falcon-team | Any | Any | Innodb crash in row_prebuilt_free row/row0mysql.c line 681 |
1708 | 2003-10-30 0:56 | 2003-11-02 7:33 | MySQL Server: InnoDB storage engine | Closed (7453 days) | S2 | 4.1.1 (2003-10-30) | Any | InnoDB crash on a subquery | |
110668 | 2023-04-12 12:36 | 2023-04-13 11:47 | MySQL Server: InnoDB storage engine | Unsupported (351 days) | S5 | 5.7.26, 5.7.29, 8.0.32 | Any | Any | Innodb crash recovery too slow if have wide table redo during apply phase |
98593 | 2020-02-14 7:13 | 2020-08-28 5:31 | MySQL Server: InnoDB storage engine | Closed (1414 days) | S6 | 8.0.19 | Any | Any | InnoDB crash when drop table in debug mode |
65071 | 2012-04-23 9:52 | 2012-04-25 18:04 | MySQL Server: InnoDB storage engine | Can't repeat (4356 days) | S1 | 5.5.23 | Linux (sles11sp2 x86_64 vmware) | Any | innodb crash with file corruption, probably related to insufficient memory |
71023 | 2013-11-27 11:16 | 2014-01-03 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3739 days) | S1 | MySQL Server 5.5 | Windows (Server 2008 R2 Standard) | Any | InnoDB crashes (purge reached the head of the history list...) |
95928 | 2019-06-22 15:20 | 2019-06-28 4:06 | MySQL Server: InnoDB storage engine | Verified (1736 days) | S3 | 5.7.x, 8.0.x | Linux | Any | InnoDB crashes on compressed and encrypted table when changing FS block size |
54890 | 2010-06-29 9:17 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | Duplicate (4948 days) | S1 | M4 (Dahlia) | Any | Any | InnoDB crashes sporadically |
6633 | 2004-11-15 11:41 | 2004-11-30 16:24 | MySQL Server: InnoDB storage engine | Closed (7059 days) | S1 | 4.1.8 bktree | Linux (Linux) | Any | InnoDB crashes when converting table from MyISAM to InnoDB |
43665 | 2009-03-16 7:15 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | Verified (4884 days) | S4 | 5.0.76, 5.1.41, 5.5.7 | Any | Any | innodb crashes when tablespace reaches maximum configured size |
69519 | 2013-06-20 4:20 | 2013-07-01 7:43 | MySQL Server: Documentation | Closed (3924 days) | S3 | 5.6 | Any | Any | InnoDB data dictionary LRU sizing through table_definition_cache is undocumented |
1887 | 2003-11-19 4:42 | 2004-01-27 10:36 | MySQL Server: InnoDB storage engine | Closed (7367 days) | S1 | 4.1 alpha | Windows (Windows XP) | Any | InnoDb data recovery |
46576 | 2009-08-05 22:22 | 2009-08-07 6:20 | MySQL Server: General | Not a Bug (5348 days) | S3 | 5.4.1 | Any | Any | InnoDB does not appear to be supported in 5.4.1 |
69131 | 2013-05-03 8:26 | 2013-05-31 19:02 | MySQL Server: InnoDB storage engine | Verified (3955 days) | S3 | 5.6 | Any | Any | InnoDB does not honor innodb_read_only when updating file format tag on startup |
68079 | 2013-01-14 12:01 | 2014-02-28 6:40 | MySQL Server: InnoDB storage engine | Closed (3725 days) | S2 | 5.5.29, 5.6.9-rc | Linux (x86_64) | Any | InnoDB does not scale well on 12 core system for specific all in memory SELECT |
67718 | 2012-11-27 0:54 | 2014-09-24 17:15 | MySQL Server: InnoDB storage engine | Closed (3546 days) | S3 | All | Any | Any | InnoDB drastically under-fills pages in certain conditions |
64704 | 2012-03-20 11:36 | 2013-01-30 15:39 | MySQL Server: DDL | Not a Bug (4076 days) | S1 | 5.5.25 | Linux (InnoDB) | Any | InnoDB error |
25484 | 2007-01-09 0:03 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6248 days) | S3 | 5.1.14 | Linux (CentOS 4.4 (RedHat)) | Any | InnoDB Error Message in Log |
41142 | 2008-12-01 4:44 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Can't repeat (5341 days) | S2 | 5.0.67 | Linux (fedora core 8) | Any | innodb errors in .log |
65208 | 2012-05-05 4:39 | 2012-06-09 1:00 | MySQL Server: InnoDB Plugin storage engine | No Feedback (4312 days) | S2 | 5.5 | Linux | Any | InnoDB fails to start if datadir located on btrfs partition |
14578 | 2005-11-02 15:36 | 2005-11-08 12:02 | MySQL Server: Installing | Closed (6716 days) | S3 | 5.0 | Windows (Windows 2003 SP1) | Any | innodb format disabled |
86036 | 2017-04-21 10:08 | 2018-11-13 7:55 | MySQL Server: InnoDB storage engine | Verified (2532 days) | S3 | 5.7/8.0 | Any | Any | InnoDB FULLTEXT index has too strict innodb_ft_result_cache_limit max limit |
83776 | 2016-11-10 20:42 | 2016-11-11 18:51 | MySQL Server: FULLTEXT search | Verified (2695 days) | S3 | 5.6/5.7/8.0 | Any | Any | InnoDB FULLTEXT search returns incorrect result for operators on ignored words |
44541 | 2009-04-29 14:12 | 2013-03-13 19:19 | MySQL Server: DDL | Closed (4034 days) | S3 | 5.1.31, 5.1.34 | Linux | Any | InnoDB generates symbols that are too long, invalid DDL from show create table |
77180 | 2015-05-28 8:26 | 2016-07-15 13:58 | MySQL Server: InnoDB storage engine | Closed (2814 days) | S2 | 5.5.40 | Linux (CentOS release 6.5 (Final)) | Any | InnoDB get corrupted during a SELECT query cause by mydumper |
104646 | 2021-08-17 15:24 | 2021-10-01 1:00 | MySQL Server: Group Replication | No Feedback (911 days) | S2 | 8.0.26 | Debian (10.10) | x86 | InnoDB group replication stalled on large transaction and high network bandwidth |
44338 | 2009-04-17 7:37 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5033 days) | S3 | 5.1.33 | Any | Any | innodb has message about non-existing option innodb_max_files_open |
76750 | 2015-04-20 8:34 | 2018-02-12 15:46 | MySQL Server: InnoDB storage engine | Verified | S3 | 5.5.44 | Any | Any | innodb History list length (trx_rseg_history_len) never reaches 0 |
83026 | 2016-09-16 19:02 | 2016-09-30 7:25 | MySQL Server: InnoDB storage engine | Verified (2737 days) | S3 | 5.6 | Any | Any | innodb history list length missing in 'show global status' |
59849 | 2011-01-31 15:16 | 2012-05-09 19:01 | MySQL Server: Documentation | Closed (4342 days) | S3 | Any | Any | innodb hot backup - missing compatibility info on the doc | |
13315 | 2005-09-19 8:08 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5033 days) | S3 | 5.0 | Any | Any | InnoDB index columns should have a maximum length of 767 |
68453 | 2013-02-21 9:51 | 2015-04-30 15:32 | MySQL Server: InnoDB storage engine | Closed (3256 days) | S3 | 5.6.10, 5.6.17 | Any | Any | InnoDB indexes no longer silently truncated to 767 bytes, produce error instead |
47300 | 2009-09-14 8:19 | 2011-02-16 23:44 | MySQL Server: Locking | No Feedback (5212 days) | S2 | 5.1.30 | Linux | Any | innodb insert dead lock |
37753 | 2008-07-01 1:20 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5740 days) | S3 | any | Any | Any | InnoDB key size limitation is not documented on the InnoDB limitations page |
68659 | 2013-03-13 7:47 | 2013-03-13 9:01 | MySQL Server: InnoDB storage engine | Analyzing (4034 days) | S5 | 5.6.10 | Any | Any | InnoDB Linux native aio should submit more i/o requests at once |
71343 | 2014-01-10 15:49 | 2018-10-01 16:17 | MySQL Server: InnoDB storage engine | Closed (3397 days) | S6 | 5.6.15 | Any | Any | InnoDB lock monitor crashes if table dropped at the right time on debug build |
56716 | 2010-09-10 15:19 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4858 days) | S2 | 5.0, 5.1, 5.5 | Any | Any | InnoDB locks a record gap without locking the table |
47862 | 2009-10-06 13:06 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | Verified | S4 | 5.0+ | Any | Any | InnoDB logging method makes it difficult to read |
72534 | 2014-05-04 19:40 | 2014-05-08 13:33 | MySQL Server: Documentation | Closed (3613 days) | S3 | 5.6 | Any | Any | InnoDB max index length not correct |
16238 | 2006-01-05 20:54 | 2006-01-07 1:13 | MySQL Server | Won't fix (6656 days) | S4 | 4.1.14-max-nt | Windows (Windows XP) | Any | InnoDB Max Key Length is still 1024 |
60776 | 2011-04-06 11:42 | 2013-05-01 20:09 | MySQL Server: InnoDB Plugin storage engine | Closed (3985 days) | S2 | any | Any | Any | InnoDB Max Purge Lag setting is wrongly designed |
35780 | 2008-04-02 23:06 | 2016-02-25 12:24 | MySQL Server: InnoDB storage engine | Not a Bug (5840 days) | S2 | 5.0.51 | Any | Any | InnoDB maximum row size changed |
67026 | 2012-09-30 20:55 | 2012-09-30 20:55 | MySQL Server: Memcached | Open | S4 | 5.6.7-rc | Any | Any | InnoDB memcached plugin - additional output formats |
13404 | 2005-09-22 14:04 | 2005-09-22 20:58 | MySQL Server | Not a Bug (6763 days) | S1 | 4.0.22 ICC | Cent OS 2.6.12-5 | Any | INNODB memory allocation error during startup |
71476 | 2014-01-25 11:22 | 2014-02-27 1:00 | MySQL Server: Errors | No Feedback (3684 days) | S3 | 5.6 | Linux (debian squeeze) | Any | InnoDB memory consumption with "bad" query |
57652 | 2010-10-22 7:58 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (4867 days) | S2 | 5.1.37 | Linux | Any | InnoDB memory crash when restarting... sometimes... |
65225 | 2012-05-07 16:39 | 2014-03-27 14:23 | MySQL Server: InnoDB storage engine | Closed (3700 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | InnoDB miscalculates auto-increment after changing auto_increment_increment |
54455 | 2010-06-12 11:11 | 2022-05-27 12:37 | MySQL Server: InnoDB storage engine | Verified (5039 days) | S4 | 5.7 | Any | Any | innodb needs a way to limit consistent read snapshot age |
77097 | 2015-05-19 14:20 | 2018-05-15 17:20 | MySQL Server: InnoDB storage engine | Verified (2276 days) | S4 | 5.6 | Any | Any | InnoDB Online DDL should support change data type |
113476 | 2023-12-20 17:00 | 2023-12-21 8:10 | MySQL Server: DDL | Verified (99 days) | S3 | 8.0 | Any | Any | InnoDB Online DDL should use multiple read views |
19271 | 2006-04-22 5:24 | 2016-08-18 8:22 | MySQL Server: InnoDB storage engine | Duplicate (2780 days) | S4 | 5.0.21-BK, 5.0.20 | Any | Any | innodb optimizer prefers primary over secondary indexes for count(*) |
112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (151 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
62937 | 2011-10-26 0:32 | 2012-01-23 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4450 days) | S3 | 5.5.15 | Linux | Any | InnoDB Page directory corruption |
113733 | 2024-01-24 6:36 | 2024-02-01 6:39 | MySQL Server: InnoDB storage engine | Verified (57 days) | S2 | 8.0, 8.0.36 | Any | Any | Innodb page has a large proportion of garbage space in certain conditions |
58460 | 2010-11-24 14:21 | 2013-04-14 20:45 | MySQL Server: InnoDB Plugin storage engine | Verified | S2 | 5.1 | Windows (Vista X86_64) | Any | Innodb plugin release built crash debug server built |
5640 | 2004-09-18 9:54 | 2004-10-18 16:35 | MySQL Server: InnoDB storage engine | Closed (7102 days) | S1 | 4.1.4-gamma | MacOS (Mac OS X 10.3.5) | Any | innodb problems with utf8 and prefix-indexes on string column |
82213 | 2016-07-13 9:03 | 2018-01-15 12:37 | MySQL Server: InnoDB storage engine | Closed (2324 days) | S3 | 5.7, 5.7.13 | Any | Any | Innodb reports warning while innodb_undo_log_truncate is enabled |
17041 | 2006-02-02 14:58 | 2006-02-02 15:15 | MySQL Server: InnoDB storage engine | Can't repeat (6630 days) | S3 | 5.0.16 | Windows (Windows) | Any | InnoDB reports wrong error code when index length exceeded |
61239 | 2011-05-20 5:01 | 2013-04-25 9:40 | MySQL Server: InnoDB storage engine | Closed (4006 days) | S3 | 5.6 | Any | Any | InnoDB silently switches to 1 buffer pool instance if size is < 1GB |
51543 | 2010-02-26 9:26 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | No Feedback (4967 days) | S5 | 5.0.81, 5.1.34 sp1, 5.1.44 | Linux (rh5.3) | Any | innodb sorting result very slow(using index,no filesort) |
71175 | 2013-12-18 15:35 | 2013-12-18 20:21 | MySQL Server: Windows | Duplicate (3754 days) | S2 | 5.7.3 | Windows (Windows 7 Entreprise 64-bir) | Any | InnoDB starting crash recovery every time MySQL 5.7.3 service starts |
51587 | 2010-02-28 16:39 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5032 days) | S3 | 5.1.x, 5.5.3-m2 | Any | Any | INNODB STATUS output in plugin weird |
65199 | 2012-05-04 5:24 | 2013-08-27 19:24 | MySQL Server: DDL | Not a Bug (3867 days) | S2 | 5.5.23 | Linux (Fedora 16) | Any | InnoDB tablespace |
2883 | 2004-02-19 0:45 | 2004-02-19 6:18 | MySQL Server: InnoDB storage engine | Closed (7344 days) | S3 | 4.1.2-alpha | Linux (Linux 2.6.3) | Any | InnoDB tablespace format downgraded |
20957 | 2006-07-11 3:27 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6440 days) | S2 | 4.1.13 | Linux (Suse 10) | Any | Innodb warning: purge reached the head of the history list |
67963 | 2012-12-22 6:51 | 2015-11-02 12:52 | MySQL Server: InnoDB storage engine | Closed (3070 days) | S3 | All | Any | Any | InnoDB wastes almost one extent out of every innodb_page_size pages |
73435 | 2014-07-30 12:27 | 2014-07-30 12:33 | MySQL Server: Options | Verified | S3 | 5.6.21 | Any | Any | innodb_api_enable_binlog is not recognized when used on the mysqld command line |
78347 | 2015-09-06 0:15 | 2015-09-22 16:53 | MySQL Server: Documentation | Closed (3111 days) | S3 | 5.7.9 | Any | Any | innodb_default_row_format: Undesireable new behaviour |
49792 | 2009-12-18 0:52 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5009 days) | S3 | Any | Any | innodb_file_format_check: default and allowed values? | |
60737 | 2011-04-02 23:44 | 2013-05-20 19:38 | MySQL Server: Documentation | Closed (3966 days) | S3 | 5.5.10, 5.5.11 | Any | Any | innodb_file_format=Barracuda still creates tables in Antelope format |
74769 | 2014-11-10 15:09 | 2015-04-06 18:45 | MySQL Server: InnoDB storage engine | Closed (3391 days) | S2 | 5.7.6-0.3.m16 | Any | Any | innodb_fts.compatibility got Assertion in file ut0ut.cc line 905 |
52393 | 2010-03-26 14:05 | 2012-07-19 23:17 | MySQL Server: Documentation | Closed (4271 days) | S3 | 5.1 and later | Any | Any | innodb_io_capacity documentation error |
22405 | 2006-09-15 19:39 | 2006-09-18 18:13 | MySQL Server: General | Closed (6402 days) | S1 | 5.1.12 | Linux (Linux) | Any | innodb_mysql.test fail on wrong result file |
108891 | 2022-10-26 20:22 | 2022-10-27 6:07 | MySQL Server: InnoDB storage engine | Verified (519 days) | S3 | 8.0 | Any | Any | innodb_print_all_deadlocks missing information. |
87697 | 2017-09-07 16:33 | 2017-09-26 15:17 | MySQL Server: Documentation | Closed (2376 days) | S2 | 5.7.19 | CentOS (7.x) | Any | innodb_read_only results in the server being unable to start |
98227 | 2020-01-14 21:39 | 2020-01-16 12:11 | MySQL Server: Information schema | Verified (1534 days) | S3 | 8.0.19, 5.7.29 | Any | Any | innodb_stats_method='nulls_ignored' and persistent stats get wrong cardinalities |
62987 | 2011-10-28 0:57 | 2012-02-22 19:01 | MySQL Server: Documentation | Closed (4419 days) | S3 | 5.0, 5.1, 5.5 | Any | Any | innodb_status_file is not documented |
54678 | 2010-06-21 19:43 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (4861 days) | S2 | 5.1,5.5.5-m3 | Any | Any | InnoDB, TRUNCATE, ALTER, I_S SELECT, crash or deadlock |
91917 | 2018-08-07 10:42 | 2018-08-07 11:52 | MySQL Server | Can't repeat (2061 days) | S1 | mysqld 5.7.21 | SUSE | x86 | InnoDB: about forcing recovery. 06:14:17 UTC - mysqld got signal 6 ; |
88046 | 2017-10-10 13:50 | 2018-10-01 16:17 | MySQL Server: DDL | Duplicate (2362 days) | S6 | 5.6.37 | Linux | Any | InnoDB: ALTER TABLE ... CHANGE ... cause mysql server crash |
62581 | 2011-09-30 7:54 | 2012-01-13 11:01 | MySQL Server: InnoDB storage engine | Duplicate (4459 days) | S1 | 5.5.15 | Linux (CentOS 5.5 kernel 2.6.18-238) | Any | InnoDB: Assertion failure ibuf0ibuf.c line 4185 unrecoverable data crash. |
68222 | 2013-01-30 8:20 | 2013-02-05 15:05 | MySQL Enterprise Backup | Duplicate (4070 days) | S3 | 5.5.27 | Linux | Any | InnoDB: Assertion Failure in file |
69825 | 2013-07-23 12:46 | 2013-08-06 14:37 | MySQL Server | Duplicate (3888 days) | S2 | 5.6.12 | Any | Any | InnoDB: Assertion failure in thread ... in file lock0wait.cc line 297 |
64680 | 2012-03-17 23:50 | 2012-12-18 19:43 | MySQL Server: InnoDB storage engine | Can't repeat (4119 days) | S2 | 5.5.21 | Linux (Ubuntu 10.4) | Any | InnoDB: Assertion failure in thread **** in file row0sel.c line 2441 |
54583 | 2010-06-17 12:14 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4914 days) | S3 | 5.5.5pre-debug | Any | Any | InnoDB: Assertion failure in thread <..> in file sync/sync0sync.c line 1226 |
113473 | 2023-12-20 11:29 | 2024-01-08 10:26 | MySQL Server: InnoDB storage engine | Unsupported (92 days) | S3 | 5.7.25 | CentOS (7.3) | Any | InnoDB: Assertion failure in thread 139747416012544 in file ut0ut.cc line 947 |
74187 | 2014-10-02 7:55 | 2015-08-22 11:50 | MySQL Server: InnoDB storage engine | Not a Bug (3142 days) | S1 | 5.5.38-0 | Linux (Ubuntu) | Any | InnoDB: Assertion failure in thread 140575349729088 in file fsp0fsp.c line 2102 |
47774 | 2009-10-01 21:55 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5251 days) | S3 | 5.5 WL#3352 | Any | Any | InnoDB: Assertion failure in thread 1769970576 in file row/row0mysql.c line 1355 |
69513 | 2013-06-19 14:22 | 2013-08-19 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3876 days) | S3 | 5.6 | Windows (Windows 7 Ultimate 64-bit) | Any | InnoDB: Assertion failure in thread 5616 in file ut0lst.h line 271 |
66879 | 2012-09-19 19:51 | 2012-10-21 1:00 | MySQL Server: Installing | No Feedback (4178 days) | S1 | 5.5.21 & 5.5.25a & 5.5.27 | Windows (XP Proj 32 bit) | Any | InnoDB: Assertion failure in thread 940 in file fsp0fsp.c line 2040 |
106868 | 2022-03-30 4:22 | 2022-03-30 13:09 | MySQL Server | Unsupported (730 days) | S3 | 5.6.17 | Windows (win10) | x86 | InnoDB: Assertion failure in thread 9560 in file trx0purge.cc line 699 |
83799 | 2016-11-14 5:50 | 2020-08-23 14:39 | MySQL Server: InnoDB storage engine | Verified (2692 days) | S3 | 5.6.34, 5.7.16 | Any | Any | InnoDB: Assertion failure in thread x in file handler0alter.cc line 5817 |
52351 | 2010-03-25 2:40 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Can't repeat (5105 days) | S1 | 5.6.99-m4-debug | Linux (Ubuntu 10.04 X86_64) | Any | InnoDB: Assertion failure with alter table |
91973 | 2018-08-10 22:53 | 2018-09-25 22:07 | MySQL Server: InnoDB storage engine | Closed (2016 days) | S6 | 8.0.12 | Any | Any | InnoDB: Assertion failure: srv0start.cc:1482:0 |
77537 | 2015-06-29 10:54 | 2016-02-04 18:14 | MySQL Server: InnoDB storage engine | Closed (3174 days) | S2 | 5.7.8 | Any | Any | InnoDB: Bogus check for maximum record length with SPATIAL KEY |
36659 | 2008-05-12 4:31 | 2022-04-10 20:45 | MySQL Server: InnoDB Plugin storage engine | No Feedback (5600 days) | S3 | 1.0 | Linux (Debian 2.6.24-1-amd64) | Any | InnoDB: compressed page checksum mismatch |
12947 | 2005-09-02 11:35 | 2005-09-04 3:02 | MySQL Server: InnoDB storage engine | Closed (6781 days) | S1 | 5.0.8? - 5.0.12 | Linux (Linux/x86) | Any | InnoDB: consistent read can return inconsistent results, even crash possible |
85871 | 2017-04-10 3:56 | 2017-04-11 14:10 | MySQL Server: InnoDB storage engine | Not a Bug (2544 days) | S3 | 5.6.28 | CentOS | Any | InnoDB: Corruption of an index tree |
105817 | 2021-12-07 8:39 | 2021-12-07 13:19 | MySQL Server | Unsupported (843 days) | S2 | 5.7.24 | CentOS (CentOS Linux release 7.2.1511 (Core)) | x86 (Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz) | InnoDB: Corruption of an index tree when I insert into table using pt-archiver |
52136 | 2010-03-17 12:34 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5094 days) | S1 | 5.1.36 | Linux | Any | InnoDB: error clustered record for sec rec not found |
37364 | 2008-06-12 12:52 | 2015-11-07 7:30 | MySQL Server: InnoDB storage engine | Can't repeat (3065 days) | S2 | 5.0.51a, 5.5.21 | Linux (Linux ES release 4) | Any | InnoDB: error in sec index entry update |
67751 | 2012-11-29 8:10 | 2013-01-23 1:00 | MySQL Server: Errors | No Feedback (4084 days) | S4 | 5.5.8 | Windows (Serveur 2008 R2) | Any | InnoDB: error in sec index entry update in |
81106 | 2016-04-16 20:30 | 2016-05-18 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2873 days) | S3 | 5.6.29 | CentOS (7.2) | Any | InnoDB: error in sec index entry update in |
93741 | 2018-12-26 9:28 | 2019-01-29 1:00 | MySQL Server | No Feedback (1887 days) | S1 | 5.7.17 | CentOS (CentOS Linux release 7.3.1611 (Core)) | Any | InnoDB: Failed to restore ibuf position. |
68311 | 2013-02-07 23:21 | 2013-02-08 22:02 | MySQL Server: InnoDB storage engine | Duplicate (4067 days) | S3 | 5.6 | Linux (Ubuntu 12.04 64-bit) | Any | InnoDB: Failing assertion thr in row0upd.cc on concurrent ALTER, UPDATE, HANDLER |
77972 | 2015-08-07 7:41 | 2018-10-01 16:17 | MySQL Server: InnoDB storage engine | Verified (2830 days) | S6 | 5.6.26, 5.7.13 | CentOS (CentOS 7) | Any | InnoDB: Failing assertion: !srv_read_only_mode in mtr0mtr.cc line 323 |
88753 | 2017-12-05 6:54 | 2018-10-01 16:18 | MySQL Server: DDL | Verified (2305 days) | S6 | 5.5.58, 5.6.35 | Any | Any | InnoDB: Failing assertion: *mbmaxlen < 5 |
84825 | 2017-02-06 7:24 | 2018-09-25 22:05 | MySQL Server: DML | Verified (2519 days) | S6 | 5.6.35 | Any | Any | InnoDB: Failing assertion: *mbmaxlen < 5 in ha_innodb.cc line 1725 |
88750 | 2017-12-05 2:46 | 2018-09-25 22:07 | MySQL Server: DML | Verified (2306 days) | S6 | 5.5.58 | Any | Any | InnoDB: Failing assertion: cursor->old_stored == 908467085 |
77976 | 2015-08-07 9:08 | 2017-09-22 14:37 | MySQL Server: Options | Verified (2380 days) | S3 | 5.6.23, 5.6.26, 5.6.37 | CentOS (CentOS 7) | Any | InnoDB: Failing assertion: event in file os0sync.cc line 419 |
76439 | 2015-03-23 0:48 | 2018-09-25 22:04 | MySQL Server: InnoDB storage engine | Closed (3278 days) | S6 | 5.7.5-m16, 5.7.6, 5.7.8, 8.0.0 | Any | Any | InnoDB: Failing assertion: flags & BUF_PAGE_PRINT_NO_CRASH |
90346 | 2018-04-09 8:59 | 2018-04-10 8:41 | MySQL Server: DDL | Can't repeat (2180 days) | S3 | 5.7.19 | MacOS | Any | InnoDB: Failing assertion: format != 0 |
77108 | 2015-05-21 4:52 | 2015-05-21 6:38 | MySQL Server: DML | Verified (3235 days) | S3 | 5.6.23, 5.6.26 | Linux (CentOS 7) | Any | InnoDB: Failing assertion: index == cursor->index in btr0sea.cc line 1782 |
81452 | 2016-05-17 6:06 | 2018-09-25 22:04 | MySQL Server: Information schema | Verified (2873 days) | S6 | 5.5.49 | Any | Any | InnoDB: Failing assertion: index->id == btr_page_get_index_id(page) |
77588 | 2015-07-01 19:56 | 2018-02-06 15:14 | MySQL Server: InnoDB storage engine | No Feedback (3122 days) | S2 | 5.6.25 | Any | Any | InnoDB: Failing assertion: index->table->stat_initialized |
74343 | 2014-10-12 20:24 | 2018-10-01 16:17 | MySQL Server: DML | Verified (3331 days) | S6 | 5.6.20, 5.6.23,5.7 | Any | Any | InnoDB: Failing assertion: inode (sig6 in fsp0fsp.cc line 1887) | error code 47 |
74876 | 2014-11-15 5:02 | 2018-10-01 16:17 | MySQL Server: DML | Verified (3329 days) | S6 | 5.6.20, 5.6.23, 5.7.5-m15, 5.7.6 | Any | Any | InnoDB: Failing assertion: inode in file fsp0fsp.cc line 1887 | fseg_inode_get |
77289 | 2015-06-10 2:49 | 2015-06-10 7:11 | MySQL Server: DML | Verified (3215 days) | S3 | 5.6.23, 5.6.25, 5.7.8 | Linux (CentOS 7) | Any | InnoDB: Failing assertion: lock->index == index | lock0lock.cc line 5573 |
83741 | 2016-11-08 10:16 | 2018-09-25 22:04 | MySQL Server: InnoDB storage engine | Verified (2698 days) | S6 | 5.7.16 | Any | Any | InnoDB: Failing assertion: lock->magic_n == 22643 |
73881 | 2014-09-10 23:39 | 2014-09-12 18:04 | MySQL Server: InnoDB storage engine | Verified (3486 days) | S3 | 5.6 | Any | Any | InnoDB: Failing assertion: state == TRX_STATE_NOT_STARTED on concurrent DDL/DML |
88794 | 2017-12-06 22:26 | 2019-01-23 11:55 | MySQL Server: InnoDB storage engine | Unsupported (1892 days) | S1 | 5.5.58 | Any | Any | InnoDB: Failing assertion: trx_sys_multiple_tablespace_format |
88748 | 2017-12-05 1:11 | 2018-09-25 22:07 | MySQL Server: XA transactions | Verified (2306 days) | S6 | 5.5.58 | Any | Any | InnoDB: Failing assertion: trx->conc_state == 1 |
58895 | 2010-12-13 10:27 | 2017-03-22 22:57 | MySQL Server: InnoDB storage engine | Closed (4825 days) | S2 | 5.6 | Any | Any | InnoDB: Failing assertion: UT_LIST_GET_LEN(buf_pool->flush_list) == 0 |
83794 | 2016-11-13 23:53 | 2016-11-14 0:12 | MySQL Server: InnoDB storage engine | Verified (2692 days) | S3 | 5.6.34 | Any | Any | InnoDB: Failing assertion: zip_size == fil_space_get_zip_size(space) |
73155 | 2014-07-01 6:40 | 2016-04-27 12:02 | MySQL Server: InnoDB storage engine | Closed (2893 days) | S2 | 5.6.19 | Linux (Centos 6.x) | Any | InnoDB: index "CLUST_IND" of table "SYS_TABLES" |
85661 | 2017-03-28 4:02 | 2018-05-26 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2135 days) | S3 | 5.7.16 | Linux | ARM | Innodb: innobase_get_cset_width assertion ut_a(cset == 0); |
32915 | 2007-12-02 22:18 | 2012-10-09 21:18 | MySQL Server: InnoDB storage engine | Closed (4189 days) | S4 | 6.0.4-alpha-debug, 5.5 | Linux (SUSE 10 64-bit) | Any | InnodB: max key length is no longer long enough |
50437 | 2010-01-19 10:31 | 2012-05-18 20:19 | MySQL Server: Charsets | Duplicate (5177 days) | S3 | 5.5, 6.1 | Any | Any | Innodb: Maximum key size limit for 4-byte utf8 is reduced from 255 to 191 chars |
105435 | 2021-11-03 3:23 | 2021-11-16 8:19 | MySQL Server: InnoDB storage engine | Verified (877 days) | S3 | 8.0 | Any | Any | InnoDB: mem_heap_alloc(heap, 0) returns non-null pointer |
76232 | 2015-03-09 16:43 | 2015-04-07 22:00 | MySQL Server: InnoDB storage engine | Closed (3300 days) | S3 | 5.7.7 | Any | Any | InnoDB: Missing brackets in fsp_flags_is_valid() |
11609 | 2005-06-28 12:13 | 2005-06-29 7:06 | MySQL Server: InnoDB storage engine | Not a Bug (6848 days) | S2 | 4.1.11-standard | Linux (Red Hat Linux 9.0) | Any | InnoDB: out of memory error |
53398 | 2010-05-04 7:08 | 2011-02-16 23:44 | MySQL Server | Closed (4956 days) | S1 | mysql Ver 14.12 Distrib 5.0.77 | Linux (Linux Server release 5.4 (Tikanga)) | Any | InnoDB: sec index record PHYSICAL RECORD: n_fields 2; compact format; info bits |
62999 | 2011-10-28 18:26 | 2012-01-19 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4454 days) | S1 | 5.1.41 | Linux (Ubuntu 10.04) | Any | InnoDB: The tablespace free space info is corrupt. |
91434 | 2018-06-27 8:55 | 2020-12-18 7:37 | MySQL Server: InnoDB storage engine | Can't repeat (2086 days) | S3 | 5.7.22 | CentOS (CentOS Linux release 7.2 (Final)) | x86 (Intel(R) Xeon(R) CPU @ 2.50GHz) | InnoDB: Trying to do I/O to a tablespace which does not exist. |
91076 | 2018-05-30 12:30 | 2022-05-10 11:37 | MySQL Server: InnoDB storage engine | Not a Bug (2123 days) | S2 | 5.6.39 | Windows | Other (X64) | InnoDB: Unable to allocate memory of size |
75680 | 2015-01-29 11:43 | 2015-04-10 7:31 | MySQL Server: InnoDB storage engine | Duplicate (3276 days) | S2 | 5.5.41 | Linux (64bit) | Any | InnoDB: unable to purge a record |
79574 | 2015-12-09 12:15 | 2018-07-06 14:57 | MySQL Server: InnoDB storage engine | Can't repeat (2093 days) | S2 | 5.6.27 | Linux (Kernel 3.4.109, x86_64, glibc-2.19) | Any | InnoDB: unable to purge a record |
71720 | 2014-02-14 13:56 | 2015-09-23 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3111 days) | S3 | 5.5.22, 5.6.16 | Linux | Any | InnoDB: unable to purge a record |
73839 | 2014-09-08 15:57 | 2014-12-18 9:03 | MySQL Server: InnoDB storage engine | Duplicate (3389 days) | S3 | 5.6.19 | Linux (CentOS 2.6.32-279.5.1.el6.x86_64) | Any | InnoDB: unable to purge a record |
74208 | 2014-10-03 8:31 | 2014-10-06 22:05 | MySQL Server: InnoDB storage engine | Duplicate (3462 days) | S3 | 5.6.20-68 | Linux (Ubuntu 12.04) | Any | InnoDB: unable to purge a record |
54658 | 2010-06-21 8:48 | 2012-02-08 17:20 | MySQL Server: InnoDB Plugin storage engine | Closed (4903 days) | S3 | Any | Any | InnoDB: Warning: allocated tablespace %lu, old maximum was 0 | |
31123 | 2007-09-21 2:50 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (4793 days) | S2 | 5.0.45, 5.1 | Any | Any | InnoDB: Warning: purge reached the head of the history list |
54965 | 2010-07-02 19:01 | 2022-04-10 20:45 | MySQL Server: InnoDB Plugin storage engine | Verified (4647 days) | S3 | 5.1, mysql-trunk-innodb | Any | Any | InnoDB: Warning: purge reached the head of the history list but it is still long |
68619 | 2013-03-09 21:59 | 2013-12-02 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3771 days) | S1 | 5.1.67 | Linux | Any | InnoDB: Warning: purge reached the head of the history list but its length is... |
45185 | 2009-05-29 10:19 | 2014-08-18 6:44 | MySQL Server: InnoDB storage engine | Can't repeat (3511 days) | S2 | 5.0.81-log, 5.6.6 | Linux (CentOS) | Any | InnoDB: Warning: using a partial-field key prefix in search |
11039 | 2005-06-02 15:07 | 2005-06-16 17:11 | MySQL Server: InnoDB storage engine | Closed (6861 days) | S3 | 5.0 | Any (any) | Any | InnoDB: Warning: using a partial-field key prefix in search. |
94055 | 2019-01-25 8:23 | 2019-01-29 15:08 | MySQL Server: Tests | Closed (1886 days) | S7 | 8.0.14 | Linux | Any | innodb.mysqld_core_dump_without_buffer_pool* tests need not_asan.inc too |
90272 | 2018-04-01 10:34 | 2018-04-04 16:03 | MySQL Server: Data Types | Verified (2186 days) | S3 | Any | Any | input overflow of ZEROS returns maximum of possible value of cell | |
98298 | 2020-01-20 12:44 | 2020-01-20 13:49 | MySQL for Windows: MySQL for Excel | Can't repeat (1530 days) | S1 | Windows (10) | Any | Input string was not correct format | |
61933 | 2011-07-20 20:08 | 2012-05-18 20:19 | Connector / NET | Duplicate (4621 days) | S1 | 6.4.3.0 | Novell NetWare (Windows 7 64) | Any | Input string was not in a correct format - System.Data.Common.DbProviderServices |
100237 | 2020-07-16 17:43 | 2020-11-22 1:00 | MySQL for Windows: MySQL Notifier | No Feedback (1224 days) | S3 | 8.0.20 | Windows (Windows 10 2004) | x86 | Input string was not in a correct format at random times |
78944 | 2015-10-23 14:11 | 2022-09-21 15:49 | Connector / NET | Can't repeat (555 days) | S3 | 6.9.7.0, 6.9.8 | Windows | Any | Input string was not in a correct format in ExecuteNoQuery |
4090 | 2004-06-10 18:11 | 2004-06-22 14:15 | MySQL Server | Closed (7220 days) | S3 | 4.1.3 | Linux (Linux) | Any | INSERT ... SELECT fails with subquery |
92813 | 2018-10-17 4:54 | 2018-10-17 9:47 | MySQL Server: InnoDB storage engine | Verified (1990 days) | S3 | 5.7.15-log MySQL Community Server (GPL) | CentOS | Any | insert ..on duplicate key update return 0 rows affected |
79475 | 2015-12-01 9:27 | 2016-02-04 18:23 | MySQL Server: InnoDB storage engine | Closed (3039 days) | S2 | 5.6+ | Any | Any | Insert a token of 84 4-bytes chars into fts index causes server crash |
112852 | 2023-10-27 7:42 | 2023-11-06 11:25 | MySQL Server: DML | Verified (144 days) | S3 | 8.0 | Linux | x86 | insert and insert onduplicate are executed concurrently, data update error |
7578 | 2004-12-29 18:48 | 2004-12-29 22:47 | MySQL Server: InnoDB storage engine | Closed (7030 days) | S1 | 5.0.3-bk | Any (all) | Any | Insert buffering of prefix indexes works incorrectly with new InnoDB format |
45903 | 2009-07-02 10:42 | 2009-07-03 8:59 | MySQL Server: Data Types | Not a Bug (5383 days) | S3 | 5.1 | Any (SQL) | Any | insert date fields should give an error if inserted Data is not formated correct |
45825 | 2009-06-29 14:55 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4956 days) | S2 | 5.1+ | Any | Any | INSERT DELAYED is not unsafe: logged in statement format |
49567 | 2009-12-09 16:37 | 2015-01-12 15:27 | MySQL Server: Replication | Won't fix (3364 days) | S2 | 5.1+ | Any | Any | INSERT DELAYED uses global binlog_format, should use session |
57355 | 2010-10-10 20:15 | 2018-06-24 20:45 | MySQL Workbench: Administration | Verified (4918 days) | S4 | 5.2.28, 5.2.29 | Any | Any | INSERT FIELD length |
10617 | 2005-05-13 10:44 | 2005-07-07 16:39 | MySQL Server | Closed (6840 days) | S3 | 5.0.5 Beta | Windows (Windows 2000 Server) | Any | Insert from same table to same table give incorrect result for bit(4) column. |
107656 | 2022-06-25 13:55 | 2022-07-01 12:09 | MySQL Server | Not a Bug (637 days) | S3 | 5.7.29 | Linux | x86 | insert into on duplicate key update with PRIMARY cause a deadlock |
16304 | 2006-01-09 16:17 | 2006-01-12 7:43 | MySQL Query Browser | Duplicate (6651 days) | S1 | 1.1.18 | Windows (Windows XP SP2) | Any | insert into made twice |
109141 | 2022-11-18 18:41 | 2023-04-17 8:29 | Connector / NET | Can't repeat (347 days) | S2 | Any | Any | Insert of data into a table results in System.ArgumentException | |
27672 | 2007-04-05 16:35 | 2007-07-29 6:36 | MySQL Server: General | No Feedback (6088 days) | S3 | 5.0.37 Community Edition | Linux (Fedora 5 64-bit) | Any | insert on duplicate key update sometimes delayed |
17801 | 2006-02-28 18:26 | 2006-03-13 12:51 | MySQL Cluster: Cluster (NDB) storage engine | Closed (6591 days) | S1 | 5.1.8 | Linux (Linux 32 Bit OS) | Any | INSERT ON DUPLICATE KEY UPDATE using NDB table cause core |
82642 | 2016-08-19 3:58 | 2016-08-19 7:59 | MySQL Server: DML | Verified (2779 days) | S3 | 5.6, 5.5.51, 5.6.32 | Any | Any | insert string-format value to datetime and timestamp return different status |
1527 | 2003-10-10 16:17 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | No Feedback (7440 days) | S2 | 3.23.57 - 4.0.15 | Linux (Linux ef248.friendfinderinc.com) | Any | Insert update performance hit and dead lock with FULLTEXT indexes |
47100 | 2009-09-03 14:32 | 2011-02-16 23:44 | MySQL Workbench | Closed (5259 days) | S3 | 5.2.2a alpha | Windows | Any | Insert values for datatype BIT are dropped |
85105 | 2017-02-21 14:37 | 2018-01-17 3:10 | MySQL Server: C API (client library) | Closed (2263 days) | S3 | 5.7.17 | Linux | Any | INSERT with CURSOR_TYPE_READ_ONLY hangs |
26281 | 2007-02-12 11:35 | 2007-03-15 4:45 | MySQL Server: General | Closed (6224 days) | S3 | 5.0 BK, 5.1 BK, 5.2.0-falcon-alpha | Linux (Linux, Windows 2000) | Any | INSERT() function mishandles NUL on boundary condition |
62322 | 2011-09-01 13:37 | 2012-02-18 1:00 | MySQL Server: Replication | No Feedback (4424 days) | S2 | 5.1.49 | Linux (Debian squeeze) | Any | Inserting 'NaN' float into a row breaks replication |
47187 | 2009-09-08 7:45 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (5001 days) | S1 | 5.1 | Linux (Ubuntu amd64) | Any | Inserting 4 million rows not possible InnoDB |
93812 | 2019-01-04 6:38 | 2019-03-11 13:50 | MySQL Server: DML | Closed (1845 days) | S6 | 8.0.13 | CentOS (CentOS Linux release 7.2.1511) | x86 (Intel(R) Xeon(R) Gold 6161 CPU @ 2.20GHz) | Inserting a date that exceeds column length when log_bin closed will core dump |
24201 | 2006-11-10 20:17 | 2006-11-21 11:08 | MySQL Server | Not a Bug (6338 days) | S1 | 4.1.18 | Any | inserting data using encode() failed | |
38080 | 2008-07-12 21:56 | 2008-07-12 22:37 | MySQL Server: Charsets | Not a Bug (5739 days) | S3 | 5.0.62 | Any | Any | Inserting hexadecimal in unicode data is not validated |
80556 | 2016-02-29 12:05 | 2016-06-13 16:39 | MySQL Server: Optimizer | Closed (2846 days) | S2 | 5.7.12 | Any | Any | inserting large json data takes an inordinate amount of time |
101877 | 2020-12-05 9:37 | 2020-12-05 10:55 | MySQL Server: DML | Verified (1210 days) | S4 | 5.7.30 | Any | Any | inserting skip check with default value '0000-00-00 00:00:00' in strict sql_mode |
16300 | 2006-01-09 13:12 | 2007-03-08 1:31 | Connector / ODBC | Not a Bug (6231 days) | S2 | 3.51.12 | IBM AIX (aix 5.2 64bit) | Any | inserting with bind values makes assumptions about long size |
42922 | 2009-02-17 9:46 | 2016-11-30 9:47 | Connector / J | Can't repeat (2676 days) | S2 | 5.1.6 | Windows (vista home basic) | Any | insertion of picture on blob or longblob |
29384 | 2007-06-27 11:55 | 2007-07-06 22:34 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (6111 days) | S5 | 5.1.16 | Linux (insertion speed not satishfied) | Any | insertion speed |
59286 | 2011-01-04 18:05 | 2011-02-27 0:00 | MySQL Workbench: Modeling | No Feedback (4780 days) | S2 | 5.2.31 | Any | Any | INSERTS |
59287 | 2011-01-04 18:05 | 2011-02-16 23:44 | MySQL Workbench | Duplicate (4813 days) | S2 | 5.2.31 | Any | Any | INSERTS |
26207 | 2007-02-09 6:18 | 2007-04-13 18:03 | MySQL Server: General | Closed (6195 days) | S2 | 5.0.22, 5.1 BK, 4.1 BK | Windows (windows) | Any | inserts don't work with shortened index |
14955 | 2005-11-15 17:31 | 2007-07-18 17:44 | MySQL Server | Can't repeat (6099 days) | S2 | 5.0.15 & 4.0.15 | Windows (WINXP_PROF_GER SP2) | Any | INSERTs with large blob-data fail on connection through named-pipe-interface |
15111 | 2005-11-21 21:15 | 2006-05-01 20:35 | MySQL Server: Documentation | Closed (6542 days) | S3 | all | Any (All) | Any | Installation procedures for binaries in 'pkg' format(Solaris) is missed |
81861 | 2016-06-15 10:33 | 2016-06-20 7:00 | MySQL Package Repos | Not a Bug (2839 days) | S3 | 5.7 | Ubuntu (elementaryOS 0.3.2) | Any | Installation with MySQL APT Repository causing slow APT UPDATE |
21247 | 2006-07-24 7:36 | 2006-08-30 20:09 | Instance Manager | Closed (6421 days) | S2 | 5.1.12 | Linux (Linux) | Any | Instance Manager: im_instance_conf.imtest fails on trees with test-1 in name |
22124 | 2006-09-08 17:21 | 2007-10-05 15:18 | Instance Manager | Unsupported (6020 days) | S3 | all | Any | Any | Instance Manager: monitors server instances using invalid username |
2051 | 2003-12-08 16:24 | 2011-02-16 23:42 | MySQL Server: DML | Verified (6684 days) | S4 | Any | Any | INSTRREV / LASTINDEXOF | |
14481 | 2005-10-30 1:52 | 2006-05-26 20:44 | MySQL Server: Documentation | Closed (6517 days) | S3 | 5.0.15 | Linux (Linux) | Any | Insufficient upgrade information on VARCHAR |
4082 | 2004-06-09 20:13 | 2011-06-25 0:39 | MySQL Server | Closed (4661 days) | S2 | 5.5, 4.0.21 and 4.1.3 | Linux (Linux) | Any | Integer lengths cause truncation with DISTINCT CONCAT and InnoDB |
7649 | 2005-01-03 23:37 | 2012-09-13 7:31 | Connector / ODBC | Can't repeat (6441 days) | S2 | 3.51.10 | Windows (windows) | Any | Integer retrieval argument fails to retrieve |
97282 | 2019-10-18 8:43 | 2019-10-30 13:11 | MySQL Workbench | Verified (1612 days) | S4 | 8.0.18 | Any | Any | Integrate TREE explain format and EXPLAIN ANALYZE in Workbench |
8947 | 2005-03-04 14:24 | 2005-05-06 11:57 | MySQL Server: Compiling | Closed (6902 days) | S3 | 4.0.24-pre | Linux (Red Hat Advanced Server 3 x86_64) | Any | Intel icc 8.1 EM64T compile problems - mi_search.c and inlining |
22928 | 2006-10-03 11:19 | 2009-03-24 15:10 | MySQL Administrator | Won't fix (5484 days) | S4 | 1.2.4rc | Windows (xp pro sp2) | Any | interface language is being selected from the formats regional setting |
52151 | 2010-03-17 18:29 | 2011-02-16 23:44 | MySQL Workbench: Administration | Closed (4855 days) | S3 | 5.2.15 OSS | Windows (Windows 7) | Any | Intermittent No data for System Health |
57942 | 2010-11-03 2:59 | 2011-02-16 23:44 | MySQL Workbench: Administration | No Feedback (4865 days) | S3 | 5.1 | Any | Any | internal error: file data passed is not in the expected format |
16485 | 2006-01-13 15:51 | 2006-06-23 12:30 | MySQL Server: Documentation | Closed (6489 days) | S3 | 4.0 | Any | Internals documentation is wrong about FIELD wire protocol for 4.0 | |
68387 | 2013-02-15 12:22 | 2013-04-26 17:34 | MySQL Server: Documentation | Closed (3990 days) | S3 | Any | Any | Internals manual reads "length of the packet" should be "length of the payload" | |
81755 | 2016-06-07 15:41 | 2020-01-11 17:02 | Connector / J | Closed (1539 days) | S3 | 6.0.2 | Any | Any | Interpret BIT fails from MysqlaUtils class |
39201 | 2008-09-02 21:22 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5686 days) | S3 | 5.1.26-rc, 4.1, 5.0, 5.1, 6.0 bzr | Linux (2.6.24.5-smp) | Any | INTO OUTFILE Statement |
74353 | 2014-10-13 10:20 | 2015-02-26 17:35 | MySQL Enterprise Backup | Not a Bug (3319 days) | S4 | 3.10.2 | Windows (Server 2012 R2) | Any | Invalid argument during backup operation |
58376 | 2010-11-22 10:31 | 2012-05-18 20:19 | MySQL Server: Charsets | Duplicate (4824 days) | S1 | 5.1.53, 5.6.1 | Any | Any | invalid memory read with trim, format, convert |
65394 | 2012-05-22 15:41 | 2013-01-30 14:45 | MySQL Server: Backup | Can't repeat (4076 days) | S3 | 5.5.30 | Any | Any | Invalid MySQL comment syntax nested within MySQL exports |
43474 | 2009-03-07 16:55 | 2021-05-23 20:45 | MySQL Server: Falcon storage engine | Duplicate (5463 days) | S1 | 6.0-falcon-team | Any | Any | Invalid page number referenced from IndexRootPage::findLeaf() |
25957 | 2007-01-30 23:47 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Won't fix (5428 days) | S3 | 5.0, 5.1, 4.1 | Windows (Windows XP Pro, Linux) | Any | Invalid Single Line Comment syntax recognized in \. command |
51397 | 2010-02-22 18:17 | 2010-02-22 18:59 | MySQL Server | Not a Bug (5149 days) | S3 | 5.1.42-community | Any | Any | Invalid string <-> integer comparison |
13776 | 2005-10-05 17:49 | 2007-11-13 8:12 | Connector / ODBC | Closed (5981 days) | S1 | 3.51.12 | Windows (Windows 2003) | Any | Invalid string or buffer length error |
77716 | 2015-07-14 9:06 | 2016-03-29 4:13 | MySQL Cluster: Cluster (NDB) storage engine | Closed (2929 days) | S2 | 7.5.0 | Any | Any | InvalidAttrInfo returned from execTUX_BOUND_INFO while scanning |
101687 | 2020-11-20 0:16 | 2020-11-20 5:10 | MySQL Server: Optimizer | Verified (1225 days) | S4 | 8.0.22 | Any | Any | Inverse unix_timestamp(TIMESTAMP_col) function needed |
88847 | 2017-12-11 3:10 | 2018-03-21 10:19 | MySQL Server: Optimizer | Closed (2200 days) | S3 | 8.0.3-rc | Any | Any | Invisible Indexes are not respected by slave under ROW format |
41799 | 2008-12-30 19:53 | 2008-12-30 20:20 | MySQL Server: InnoDB storage engine | Not a Bug (5568 days) | S3 | 5.1.30 | Linux (Debian) | Any | Invisible transaction lock my table |
84086 | 2016-12-07 5:57 | 2022-01-20 12:13 | Connector / J | Can't repeat (799 days) | S3 | 5.1.40 | Windows | Any | Invoking getString on blob data type doesn't return string value |
49579 | 2009-12-10 10:14 | 2011-02-16 23:44 | MySQL Server: General | Closed (5136 days) | S2 | 5.6 (Celosia) | FreeBSD | Any | IPv6 tests fail on FreeBSD |
1285 | 2003-09-15 16:19 | 2004-09-23 14:15 | MySQL Server | Not a Bug (7127 days) | S3 | 4.0.15 | Linux (Linux x86) | Any | Is Max keyfile length settable? What to do when exceeded? |
33649 | 2008-01-03 12:35 | 2008-11-13 3:19 | MySQL Server: Charsets | Closed (5615 days) | S2 | 6.0.4-alpha | Any | Any | Is multi-byte encoding applied twice, leading to squared size ? |
7308 | 2004-12-15 7:10 | 2005-08-08 12:41 | MySQL Server | Closed (6808 days) | S3 | 4.1.8 | Any (Any) | Any | ISO8601 dates are no longer accepted by MySQL |
54673 | 2010-06-21 16:22 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (4853 days) | S3 | 5.1.48, 5.5.5pre | Any | Any | It takes too long to get readlock for 'FLUSH TABLES WITH READ LOCK' |
83062 | 2016-09-20 13:18 | 2018-04-24 20:15 | MySQL Server: Optimizer | Verified (2746 days) | S3 | 5.6.32, 5.7.14, 5.6.33, 5.7.15 | Any | Any | it's no longer possible to determine used key parts by looking at key_length |
107769 | 2022-07-06 8:07 | 2022-07-06 11:34 | MySQL Server | Not a Bug (632 days) | S3 | MySQL5.7.26 | Linux | x86 | It's wrong when io_cache calculate info->write_end |
112848 | 2023-10-27 2:28 | 2023-10-27 11:37 | MySQL Server: Data Types | Verified (154 days) | S3 | 8.0 | Any | Any | Item_func_set_user_var::get_string_value may have potion risk of memory access |
35514 | 2008-03-24 16:26 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5594 days) | S2 | 6.0-falcon-team | Any | Any | Item_func_uuid::val_str(String*): Assertion `tv > uuid_time' failed. |
74418 | 2014-10-16 10:17 | 2019-11-20 21:26 | MySQL Server: DML | Can't repeat (1591 days) | S6 | 5.6.20, 5.6.22, 5.6.35 | Any | Any | Item_in_subselect::val_int(): Assertion `0' failed. in sql/item_subselect.cc:136 |
46629 | 2009-08-10 13:21 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (5215 days) | S2 | 5.1 | Any | Any | Item_in_subselect::val_int(): Assertion `0' on subquery inside a SP |
34620 | 2008-02-16 17:16 | 2008-03-15 8:41 | MySQL Server: DML | Closed (5858 days) | S3 | 5.0+, 5.0.58-BK | Any | Any | item_row.cc:50: Item_row::illegal_method_call(const char*): Assertion `0' failed |
34763 | 2008-02-22 19:20 | 2008-04-14 19:22 | MySQL Server: Optimizer | Closed (5828 days) | S3 | 5.0+ | Any | Any | item_subselect.cc:1235:Item_in_subselect::row_value_transformer:Assertion failed |
33112 | 2007-12-10 11:17 | 2008-03-03 14:36 | MySQL Enterprise Monitor: Documentation | Closed (5870 days) | S1 | 1.3J beta | Any | Any | Japanese documents in PDF format show broken characters |
32075 | 2007-11-03 17:10 | 2007-11-12 15:11 | MySQL Enterprise Monitor: Advisors/Rules | Closed (5982 days) | S3 | Any | Any | Japanese rules don't format properly into HTML from WIKI text | |
32649 | 2007-11-23 10:11 | 2008-02-27 5:38 | Connector / J | Duplicate (5875 days) | S3 | 5.1.5 | Any | Any | java.sql.SQLException: Bad format for DATE '...' |
86159 | 2017-05-02 13:08 | 2018-10-21 20:45 | Connector / J | No Feedback (2491 days) | S2 | 5.1.42 | Any | Any | JConnector driver does not free closed objects |
30990 | 2007-09-13 4:30 | 2012-09-13 8:35 | Connector / J | Closed (5978 days) | S3 | connectorJ 5.0.4 & 5.0.7 | Any | Any | JDBC connections do not properly free up resources when returned a pool |
2654 | 2004-02-05 10:51 | 2004-03-30 7:30 | MySQL Server | Closed (7304 days) | S3 | 4.1.1-alpha-standard | Linux (Linux (2.4.21)) | Any | JDBC Exception: "Column 'column.table' not found" when "order by" in query |
68957 | 2013-04-14 20:09 | 2018-06-26 13:06 | Connector / J Documentation | Closed (2103 days) | S2 | Connector J 5.1.23 | Any (JDBC ) | Any | JDBC SSL connection access denied exception |
35753 | 2008-04-01 21:39 | 2011-02-16 23:43 | Connector / J | Closed (5370 days) | S3 | 5.1 | Any | Any | jdbc useOldAliasMetadataBehavior connection property not set |
30917 | 2007-09-08 16:05 | 2007-09-11 16:35 | Connector / J | Closed (6044 days) | S3 | 5.0.7 | Linux | Any | jdbcCompliantTruncation initialization has no effect |
73438 | 2014-07-30 15:56 | 2018-09-25 21:51 | Tests: Replication | Closed (3367 days) | S7 | 5.6.21 (advanced 64bit) | Any | Any | JET replicationMixedStressTest fails for 5.5->5.6.21 |
73928 | 2014-09-16 10:22 | 2016-02-02 19:10 | MySQL Server: Replication | Closed (3367 days) | S2 | 5.6.21 | Any | Any | JET replicationRowDataTypeConversionTest fails in 5.6.21 and trunk |
19548 | 2006-05-04 22:09 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5104 days) | S4 | 5.0.18-pro, 5.1.40sp1 | Linux (Redhat Linux ES4) | Any | JOIN and composite indexes (not using full length) |
58065 | 2010-11-08 21:31 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (4888 days) | S2 | 5.1.51, 5.1.52, 5.0, 5.1, 5.6.99 bzr | Linux (x64, 2.6.32) | Any | join condition handles date columns differently if there's a unique key |
101272 | 2020-10-22 9:01 | 2020-11-02 14:21 | MySQL Server: Optimizer | Won't fix (1243 days) | S3 | 8.0 | Any | Any | Join cost in explain format tree is wrong |
37690 | 2008-06-27 11:30 | 2011-02-16 23:43 | MySQL Server: Optimizer | Closed (4876 days) | S3 | 6.0-bka-preview | Any | Any | join_buffer_size = 0 + use of JOIN_CACHE_BKA_UNIQUE crash mysqld |
85755 | 2017-04-01 0:53 | 2022-12-04 14:15 | MySQL Server: JSON | Verified (1893 days) | S2 | 5.7.17 | CentOS (centos 7) | Any | JSON containing null value is extracted as a string "null" |
104729 | 2021-08-26 3:44 | 2021-08-31 13:03 | MySQL Websites: bugs.mysql.com | Closed (941 days) | S3 | Any | Any | JSON doesn't get spelled JSOM | |
111357 | 2023-06-12 8:03 | 2023-06-12 8:56 | MySQL Server: Optimizer | Verified (291 days) | S6 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | JSON explain assertion error |
69388 | 2013-06-03 15:25 | 2016-02-25 12:24 | MySQL Server: Security: Privileges | Verified | S4 | 5.6.12 | Any | Any | JSON EXPLAIN needs table_schema attribute |
111112 | 2023-05-22 19:56 | 2023-05-24 15:34 | MySQL Server | Closed (310 days) | S3 | 8.0 | Any | Any | JSON SDI default_value in columns object includes trailing zero bytes |
113514 | 2023-12-26 16:07 | 2023-12-27 5:24 | MySQL Server: JSON | Duplicate (93 days) | S3 | 8.0.35 | Linux | Any | JSON_OBJECT changes order of keys in output |
100974 | 2020-09-28 13:52 | 2023-12-27 5:24 | MySQL Server: JSON | Closed (891 days) | S1 | 8.0 | Any | Any | JSON_OBJECT() performs key sort on output |
92264 | 2018-09-01 10:07 | 2018-09-17 17:45 | Connector / J | Closed (2020 days) | S2 | 8.0.12 | Any | Any | JsonParser puts unnecessary maximum limit on JsonNumber to 10 digits |
2585 | 2004-01-30 11:28 | 2013-06-13 23:57 | MySQL Server | Verified (6052 days) | S4 | all | Any (all) | Any | Julian date character function |
67550 | 2012-11-10 18:09 | 2012-12-11 1:00 | MySQL Workbench: SQL Editor | No Feedback (4127 days) | S3 | 5.2.42 | Windows (Microsoft Windows Server 2008 R2 Enterprise Edition Service Pack 1 (build 7601), 64-bit) | Any | just hold |
67080 | 2012-10-04 13:30 | 2012-11-05 1:00 | MySQL Workbench | No Feedback (4163 days) | S3 | 5.2.43 | Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit) | Any | Just stop working |
37292 | 2008-06-09 18:29 | 2013-03-03 20:45 | MySQL Server: General | Verified (5771 days) | S3 | 5.1.23-rc | Any | Any | KEY array passed into handler::add_index has incomplete information |
14381 | 2005-10-27 9:35 | 2005-11-01 19:17 | MySQL Server: BDB | Closed (6723 days) | S4 | 5.0.16-debug-log | Linux (Linux) | Any | Key length is limited to 255 bytes on BDB |
70341 | 2013-09-13 19:00 | 2013-11-01 9:45 | MySQL Server: Optimizer | Closed (3801 days) | S2 | 5.5.31, 5.6 | Any | Any | Key lengths lead to incomplete result sets; unhinted scans prefer such indexes |
3878 | 2004-05-25 2:20 | 2004-05-25 10:36 | MySQL Server | Closed (7248 days) | S3 | 4.1.1-alpha | Linux (Linux x86/Fedora 2) | Any | key on TEXT column fails |
38834 | 2008-08-16 9:35 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Duplicate (5475 days) | S3 | mysql-5.1.26-rc-winx64 | Windows (64-bit) | Any | key_buffer_size irregularities on 64 bit windows |
4406 | 2004-07-05 5:20 | 2004-09-26 13:56 | MySQL Server | Closed (7124 days) | S3 | 5.0.0alpha | Linux (Linux) | Any | keylength 500 too small for utf8 on 5.0.0 |
31074 | 2007-09-18 5:04 | 2007-11-25 14:41 | MySQL Server: General | Can't repeat (5969 days) | S3 | 5.0.50, 5.1.23BK | Any | Any | keys on innodb spatial columns cause prefix warnings in logs |
44171 | 2009-04-08 23:35 | 2011-02-16 23:43 | MySQL Server: DDL | Closed (4878 days) | S3 | 5.1,6.0 | Any | Any | KILL ALTER EVENT can crash the server |
71070 | 2013-12-04 4:05 | 2014-07-28 9:37 | MySQL Server: Replication | Closed (3607 days) | S2 | 5.6.14,5.5.18, 5.6.15 | Any | Any | kill of truncate table will lead to binary log written while rows remains |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (406 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
26881 | 2007-03-06 16:08 | 2007-03-18 22:36 | MySQL Server: Merge storage engine | Closed (6221 days) | S1 | 5.0.36 | Any (All) | Any | Large MERGE tables report incorrect specification when no differences in tables |
70603 | 2013-10-11 14:11 | 2013-10-11 15:50 | MySQL Utilities | Not a Bug (3822 days) | S2 | 6.0 Comunity | Windows (7, 64bits) | Any | large result set don't show data |
11644 | 2005-06-29 17:10 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Verified (6831 days) | S4 | * | Any (*) | Any | large table with 4 byte pointers |
51086 | 2010-02-11 11:11 | 2010-02-11 16:49 | MySQL Server: Locking | Not a Bug (5160 days) | S2 | 5.0.51a | Linux | Any | last deadlock detected not showing a valid reason for the deadlock |
33629 | 2008-01-02 15:46 | 2011-02-16 23:43 | MySQL Server: DML | Closed (5251 days) | S3 | 5.0.52, 5.1.23, 6.0.3 | Any | Any | last_day function can return null, but has 'not null' flag set for result |
25494 | 2007-01-09 14:23 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5031 days) | S3 | 4.0, 4.1, 5.0, 5.1 | Any | Any | LATEST DEADLOCK INFORMATION is not always cleared |
111604 | 2023-06-28 14:20 | 2023-06-30 11:36 | MySQL Workbench: SQL Editor | Duplicate (273 days) | S3 | 8.0.33 | Windows (Microsoft Windows 10 Enterprise) | Any | Latest Workbench 8 doesn't recognize 'STOP/START REPLICA' as a valid statement. |
37738 | 2008-06-30 11:53 | 2012-05-18 20:19 | MySQL Server: Charsets | Duplicate (5651 days) | S4 | 5.1, 6.0 | Linux (All Linux and Unix systems) | Any | Latin9 for MySQL |
11836 | 2005-07-09 16:17 | 2006-08-05 11:10 | MySQL Server: Compiling | Closed (6446 days) | S3 | Mysql 5.0.24 | Other (IRIX-6.5.28) | Any | ld32: FATAL 11 : Object file format error (../../../ndb/src/.libs/libndbclien |
14081 | 2005-10-17 17:41 | 2006-01-04 15:05 | MySQL Query Browser | Can't repeat (6659 days) | S3 | 1.1.15 | Windows (Windows XP) | Any | Left arrow in query editor incorrectly uses current line length |
41059 | 2008-11-26 16:21 | 2008-12-03 17:47 | MySQL Server: Compiling | Not a Bug (5595 days) | S2 | 5.1.29 | Windows (XP ver 2002, SP2) | Any | Left Join cause date format not recognized in where clause |
16592 | 2006-01-18 2:50 | 2006-02-18 13:53 | MySQL Server | No Feedback (6614 days) | S1 | 5.0.18-standard | Linux (Linux) | Any | Left Join On Views |
41220 | 2008-12-04 9:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5337 days) | S5 | 5.1.30, 5.0, 5.1, azalea bzr | Any | Any | LEFT JOIN with compound clause uses table scan, while INNER JOIN uses indexes |
48868 | 2009-11-18 15:42 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4876 days) | S3 | 6.0 | Any | Any | Left outer join in subquery causes segmentation fault in make_join_select |
10963 | 2005-05-30 14:23 | 2007-04-10 16:16 | MySQL Server | Closed (6198 days) | S3 | 5.0.7-beta-debug | Linux (SUSE 9.2) | Any | LEFT/RIGHT/SUBSTR/.. string functions returns wrong result on large length |
37301 | 2008-06-10 8:10 | 2011-02-16 23:43 | MySQL Server: C API (client library) | Closed (5595 days) | S2 | 5.0.56entSP1, 5.0.64pb, 5.1.26rc-pb | Windows (XP SP2) | Any | Length and Max_length differ with no obvious reason |
68405 | 2013-02-16 22:57 | 2013-03-04 16:59 | MySQL Server: Documentation | Closed (4043 days) | S3 | Any | Any | Length encoded integer defines overlapping intervals for 2 / 3 byte ints. | |
30619 | 2007-08-24 9:20 | 2007-08-24 10:19 | MySQL Server: Data Types | Not a Bug (6062 days) | S2 | 5.0.45 | Linux (kubuntu feistt) | Any | Length for CHAR and VARCHAR supposed to be a number of chars, not bytes |
56487 | 2010-09-02 9:43 | 2017-05-21 20:45 | MySQL Server: Replication | Verified | S3 | 5.1+ | Any | Any | length of arg value in `--replicate-*= value' is not checked |
51206 | 2010-02-16 10:23 | 2011-02-16 23:44 | Connector / NET | Can't repeat (5154 days) | S1 | 6.2.2 | Linux | Any | length of char field return is 3x as big on utf8 then on latin |
325 | 2003-04-25 17:56 | 2003-05-15 1:08 | MySQL Server | Closed (7624 days) | S2 | 4.1.0 | Linux (Linux,Windows and solaris(sparc)) | Any | Length of geometry data type |
99385 | 2020-04-28 9:00 | 2020-04-29 12:11 | MySQL Server: DDL | Not a Bug (1430 days) | S3 | 8.0.19 | Windows (2019) | x86 | Length of integer field will not by stored |
13134 | 2005-09-13 10:45 | 2006-03-04 8:00 | MySQL Server: Stored Routines | Closed (6600 days) | S2 | 4.1.16, 5.0.12, 5.0.17-bk | Windows (Windows/Linux) | Any | Length of VARCHAR() utf8 column is increasing when table is recreated with PS/SP |
33265 | 2007-12-16 0:52 | 2008-03-15 12:25 | MySQL Workbench | Closed (5858 days) | S3 | 5.0.10 SE Beta | Windows (XP SP2) | Any | Length on Table Name, Column Name, View Name, etc |
51565 | 2010-02-26 21:25 | 2012-05-18 20:19 | Connector / NET | No Feedback (4646 days) | S3 | Any | Any | Length shows as -1 for blob columns in query builder | |
58234 | 2010-11-16 16:26 | 2014-02-26 12:47 | MySQL Server: InnoDB storage engine | Verified (4485 days) | S5 | 5.1.49-r1, 5.5.20 | Any | Any | LENGTH() / OCTET_LENGTH() on BLOB field very slow |
43257 | 2009-02-27 11:57 | 2009-03-03 13:58 | MySQL Query Browser | Won't fix (5505 days) | S3 | 1.2.17 | Any | Any | length() function missing syntax-color |
5723 | 2004-09-23 15:20 | 2004-09-26 16:59 | MySQL Server | Closed (7124 days) | S2 | 4.1.6 | any (FreeBSD / Linux) | Any | length(<varchar utf8 field>) returns varying results |
29745 | 2007-07-12 3:03 | 2011-03-29 18:58 | MySQL Server: Data Types | Closed (4749 days) | S1 | 5.1.20 | Any | Any | LENGTH(binary_field) with select from (select table) as tmp_tbl don't working |
18 | 2002-12-31 13:59 | 2003-01-04 14:34 | MySQL Server | Closed (7755 days) | S2 | 4.0.7 | Linux (Linux) | Any | length(quote(...)) kills MySQL server |
81672 | 2016-06-01 9:04 | 2016-09-21 15:11 | MySQL Server: Optimizer | Closed (2746 days) | S3 | 5.6 | Any | Any | Less optimal index is chosen, index length does impact cost |
37462 | 2008-06-17 21:23 | 2011-05-23 22:18 | MySQL Enterprise Monitor | Closed (4694 days) | S4 | 2.0.0.6067 | Any | Any | Let customers export the collected data as .csv , pdf , png files |
82919 | 2016-09-09 5:49 | 2016-12-02 13:02 | MySQL Server: Replication | Verified (2753 days) | S3 | 5.7.14 | Any | Any | Let's break the restriction of `create table select` statement. |
31865 | 2007-10-25 22:33 | 2012-05-18 20:19 | MySQL Server: Compiling | Duplicate (5434 days) | S3 | 5.0+ | Any | Any | LEX_STRING and MYSQL_LEX_STRING mismatch |
25155 | 2006-12-18 21:09 | 2007-03-15 20:54 | Connector / ODBC | Closed (6224 days) | S1 | 3.51.07-ibm-aix5.1 | IBM AIX (AIX 5.2) | Any | libmyodbc3.so from MyODBC-3.51.07-ibm-aix5.1.0.0-powerpc.tar doesn't work |
59848 | 2011-01-31 14:34 | 2011-04-11 23:00 | MySQL Server: C API (client library) | No Feedback (4737 days) | S3 | any | Any | Any | libmysql can't authenticate users who have \0 in their password |
15613 | 2005-12-09 0:38 | 2006-02-02 4:58 | MySQL Server | Closed (6630 days) | S2 | 4.1.15, 5.0.18-BK | Linux (Linux) | Any | libmysqlclient API function mysql_stmt_prepare returns wrong field length |
105707 | 2021-11-25 9:29 | 2021-12-02 18:51 | MySQL Server: Compiling | Closed (848 days) | S3 | 8.0.27 | CentOS (AlmaLinux 8.4) | x86 | libmysqlclient C++20 compilation fails due to reserved 'requires' keyword |
92394 | 2018-09-12 23:52 | 2019-09-24 13:58 | MySQL Server: C API (client library) | Can't repeat (1648 days) | S3 | 5.7.23 | Ubuntu | x86 | libmysqlclient enters infinite loop after signal (race condition) |
10638 | 2005-05-14 5:11 | 2005-07-19 23:19 | MySQL Server: Packaging | Closed (6828 days) | S2 | 4.0 | MacOS (Mac OS X 10.3) | Any | libmysqlclient_r not built with -fno-common |
59345 | 2011-01-07 9:40 | 2018-05-08 9:58 | Connector / C | Not a Bug (3399 days) | S2 | 6.0.2 | Linux (SUSE 10 x86 ) | Any | libmysqlclient_r.so crashed in my_read when mysql_query("LOAD DATA LOCAL") |
53043 | 2010-04-22 1:22 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5076 days) | S3 | 5.0, 5.1 | Linux | Any | LIKE ANY produces syntax error |
59140 | 2010-12-23 18:29 | 2018-04-12 5:27 | MySQL Server: Charsets | Closed (4315 days) | S2 | 5.5.8 | Any | Any | LIKE concat('%',@a,'%') doesn't match when @a contains latin1 string |
11245 | 2005-06-10 13:45 | 2005-06-10 14:13 | MySQL Server | Can't repeat (6867 days) | S3 | 4.1.11 | Windows (Windows XP) | Any | LIKE doesn't return rows when used with index |
59822 | 2011-01-30 16:45 | 2011-03-01 0:00 | MySQL Server: General | No Feedback (4778 days) | S3 | 5.1.41 | Linux | Any | LIKE operator does not work as expected |
68155 | 2013-01-23 14:12 | 2013-10-01 12:33 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (3832 days) | S2 | 7.2.10 | Linux (CentOS 6.3 x86_64) | Any | LIKE operator for VARCHAR fields with full length doesn't work |
87883 | 2017-09-27 9:10 | 2017-09-27 19:42 | MySQL Server: InnoDB storage engine | Not a Bug (2375 days) | S5 | 5.6.37 | Any | Any | LIKE operator significantly slower than MyISAM |
11650 | 2005-06-30 0:44 | 2010-09-25 0:49 | MySQL Server | Closed (6827 days) | S2 | 4.1.12/5.0.8-bk,5.1.46-5.1.49 | Linux (SuSE Linux 9.2/Windows) | Any | LIKE pattern matching using prefix index doesn't return correct result |
24921 | 2006-12-08 17:30 | 2007-05-20 5:37 | MySQL Server: Falcon storage engine | Closed (6158 days) | S2 | 5.1.13-falcon-alpha-debug | Linux (SUSE 10.0 / 64-bit) | Any | LIKE searches fail if index on utf8 column |
4899 | 2004-08-04 21:18 | 2004-08-06 10:34 | MySQL Server | Closed (7175 days) | S3 | mysql-max-4.1.3-beta-pc-linux-i686 | Linux (RH7.3-x86) | Any | limit on index length for blob |
111700 | 2023-07-09 7:31 | 2023-07-12 5:55 | MySQL Server: Optimizer | Verified (261 days) | S3 | 8.0.32, 8.0.33 | Any | Any | LIMIT values are not adequately handled in EXPLAIN. |
68192 | 2013-01-27 20:52 | 2013-01-28 15:40 | MySQL Server: Data Types | Verified (4078 days) | S3 | 5.1, 5.5, 5.6.9 | Any | Any | Limitation on DOUBLE or REAL length is ignored with INSERT .. SELECT |
24577 | 2006-11-24 16:43 | 2023-02-12 20:45 | MySQL Server: Replication | Verified (5656 days) | S4 | * | Any (*) | Any | limited replication for upgrading major versions |
12566 | 2005-08-13 7:41 | 2005-09-19 7:34 | MySQL Server | No Feedback (6766 days) | S3 | 5.x | Windows (Windows 2003) | Any | Line break in stored procedure gives #42000Incorrect number of arguments |
31659 | 2007-10-17 8:09 | 2009-06-09 12:55 | MySQL Query Browser | Won't fix (5407 days) | S3 | 1.2.12 | Windows (XP SP2) | Any | Line breaks always converted to CR/LF on triggers and procedures |
22002 | 2006-09-04 16:07 | 2006-09-11 13:46 | MySQL Administrator | Closed (6409 days) | S3 | 1.2.2 beta | Windows (Windows XP) | Any | line-lenght "Edit View" |
47264 | 2009-09-11 0:56 | 2012-05-18 20:19 | Connector / NET | No Feedback (5280 days) | S1 | 6.1 | Any | Any | linq2ef sort by length not correctly |
49310 | 2009-12-01 22:49 | 2016-02-25 12:24 | MySQL Workbench: SQL Editor | Closed (5026 days) | S2 | 5.2.10 r4680 | Windows (XP) | Any | Live editor limits to 1000 rows, no way to page further or define length? |
14477 | 2005-10-30 0:11 | 2005-10-30 14:22 | MySQL Server | Closed (6725 days) | S2 | 5.0.15-nt | Windows (Windows XP) | Any | LOAD DATA fails if non-ascii character in data |
305 | 2003-04-17 15:35 | 2003-05-16 3:28 | MySQL Server: Documentation | Not a Bug (7623 days) | S3 | 4.1.0-alpha (all?) | Any (all) | Any | LOAD DATA for fixed-row input |
21482 | 2006-08-07 15:05 | 2006-09-05 17:14 | MySQL Server | Won't fix (6415 days) | S2 | 5.0.24 | Windows (Win32) | Any | LOAD DATA FROM MASTER fails with "Failed rebuilding the index of dumped table" |
9125 | 2005-03-11 11:36 | 2006-08-30 18:28 | MySQL Server: Replication | Won't fix (6421 days) | S1 | 4.0.22 | Linux (gentoo linux) | Any | LOAD DATA FROM MASTER: Replication fails to start on slave |
12531 | 2005-08-11 17:08 | 2011-02-16 23:43 | MySQL Server: DML | No Feedback (4820 days) | S4 | 4.1.12 | Linux (Linux 2.6.9) | Any | LOAD DATA INFILE from a named pipe hangs |
78051 | 2015-08-13 8:01 | 2015-08-13 10:32 | MySQL Server: Replication | Verified (3151 days) | S2 | 5.6 5.5, 5.6.26 | Linux | Any | LOAD DATA INFILE is not replicated correctly if master uses relay-log-info-repos |
17683 | 2006-02-24 0:59 | 2006-04-06 19:16 | MySQL Server: Documentation | Closed (6567 days) | S3 | 5.0.18 | Linux (Linux 2.4.31-ow1) | Any | LOAD DATA INFILE loads wrong value for BIT columns |
50759 | 2010-01-30 19:08 | 2018-09-09 20:45 | MySQL Server: DML | Verified (5148 days) | S4 | 5.x | Any | Any | Load data infile support to limit the amount of data to be read into table |
93169 | 2018-11-13 6:09 | 2018-11-13 7:04 | MySQL Server | Not a Bug (1963 days) | S3 | Any | Any | LOAD DATA LOCAL INFILE field substring | |
59267 | 2011-01-04 3:43 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4797 days) | S2 | 5.5.9 | Windows | Any | LOAD DATA LOCAL INFILE not executed on slave with SBR |
1765 | 2003-11-06 4:37 | 2003-11-12 14:22 | MySQL Server | Not a Bug (7443 days) | S2 | 4.0.16 | Windows (Win XP Pro) | Any | LOAD TABLE time-fields set to 00:00:00 when minutes in range 1-12 |
42719 | 2009-02-10 2:05 | 2012-05-18 20:19 | MySQL Server: XML functions | Verified (5524 days) | S3 | 6.0.10 | Linux (x64-debug) | Any | LOAD XML crashes debug build |
86916 | 2017-07-04 3:33 | 2024-02-06 17:20 | MySQL Server: DML | Verified (2459 days) | S3 | 5.7.18 | Any (OS 10.10.5) | Any | LOAD XML does not decode entities |
84245 | 2016-12-17 23:03 | 2022-12-06 9:01 | MySQL Server: DML | Verified (2648 days) | S2 | 5.5/5.6/5.7/8.0 | MacOS | Any | LOAD XML duplicates prior element's values when encountering empty element |
83427 | 2016-10-18 13:22 | 2016-11-19 16:33 | MySQL Server: Optimizer | Closed (2718 days) | S3 | 5.0.47 | Any | Any | LOCATE('he','hello',NULL) should return NULL instead of 0 |
70767 | 2013-10-29 19:09 | 2020-02-14 21:55 | MySQL Server: Charsets | Verified (3602 days) | S2 | 5.5.31, 5.5.34 | Any | Any | LOCATE() and INSTR() claim to be multibyte aware, but are not |
84816 | 2017-02-04 7:48 | 2017-03-08 1:00 | MySQL Server | No Feedback (2579 days) | S1 | 5.6.12-debug | CentOS (7) | Any | lock table write timeout cause server crash |
29154 | 2007-06-16 7:29 | 2007-07-04 1:52 | MySQL Server | Closed (6113 days) | S2 | 5.0.44-BK, 5.0.40 | Linux | Any | LOCK TABLES is not atomic when >1 InnoDB tables are locked |
40737 | 2008-11-14 12:14 | 2009-08-12 21:43 | MySQL Server: Locking | Not a Bug (5343 days) | S2 | 5.0.67 | Any | Any | Lock wait timeout exceeded during inserting row |
38660 | 2008-08-08 8:50 | 2011-02-16 23:43 | MySQL Server: Replication | No Feedback (5587 days) | S2 | 5.0.51a, 5.1.26 | Linux | Any | Lock wait timeout exceeded while failing-over on master-master replication setup |
39897 | 2008-10-07 6:13 | 2018-09-25 21:49 | Tests: Server | Closed (5137 days) | S7 | 5.1, 6.0 | Any | Any | lock_multi fails in pushbuild: timeout waiting for processlist |
8144 | 2005-01-26 13:49 | 2005-01-28 11:39 | MySQL Server: InnoDB storage engine | Closed (7000 days) | S2 | 5.0.3-bk | Any (all) | Any | Locking problem in TRUNCATE TABLE |
76463 | 2015-03-23 17:27 | 2016-02-17 8:52 | MySQL Server: Errors | Verified (3294 days) | S3 | 5.0/5.1/5.5/5.6/5.7 | Any | Any | Log error when AUTO INCREMENT column has reached max value. |
27857 | 2007-04-16 17:59 | 2007-07-11 16:45 | MySQL Server: Logging | Closed (6106 days) | S3 | 5.1.18 | Linux | Any | Log tables supplies the wrong value for generating AUTO_INCREMENT numbers |
17889 | 2006-03-03 9:21 | 2006-03-09 10:52 | MySQL Server | Duplicate (6595 days) | S3 | 4.1 and later | Any (*) | Any | log_queries_not_using_indexes not shown in SHOW VARIABLES output |
86728 | 2017-06-16 10:37 | 2017-10-05 15:54 | MySQL Server: Installing | Closed (2367 days) | S3 | 8.0.2 | Any | Any | log_sink_json service doesn't work with rpm default installation |
107956 | 2022-07-25 7:11 | 2022-08-12 8:09 | MySQL Server: Row Based Replication ( RBR ) | Not a Bug (595 days) | S3 | 5.7.35 | Ubuntu | Any | log_slave_updates not respecting binlog_row_image |
39997 | 2008-10-13 11:59 | 2008-11-12 0:18 | MySQL Server: Backup | Closed (5616 days) | S3 | 6.0-bk | Any | Any | Logger::write_message() causes an assertion failure |
83293 | 2016-10-06 22:22 | 2016-10-18 22:51 | MySQL Server: Logging | Verified (2719 days) | S2 | 5.7.13, 5.7.15 | Any | Any | Logging is missing for interrupted queries |
35165 | 2008-03-08 17:48 | 2022-12-04 20:45 | MySQL Server: CSV | Verified (5861 days) | S5 | 5.1 | Any | Any | Logging to table is slow for large queries |
41593 | 2008-12-18 16:23 | 2011-02-16 23:43 | MySQL Enterprise Monitor: Web | Closed (5538 days) | S3 | 2.0 | Any | Any | Logic error in FileAppender breaks logs tab when files hit rotation limit |
82733 | 2016-08-25 21:56 | 2016-08-27 8:10 | MySQL Server: Security: Privileges | Verified (2771 days) | S3 | 5.6, 5.7, 5.6.32 | Any | Any | Login errors after GRANT ON *.* in sql_mode PAD_CHAR_TO_FULL_LENGTH |
12230 | 2005-07-27 21:10 | 2005-11-22 4:31 | Connector / J | Closed (6702 days) | S4 | 3.1.10 | Windows (XP) | Any | logSlowQueries should give better info |
11753 | 2005-07-05 23:58 | 2005-07-06 4:24 | Connector / ODBC | Can't repeat (6841 days) | S2 | 3.51 | Windows (win2k pro) | Any | long string is truncated on fetch |
79680 | 2015-12-16 20:54 | 2017-01-30 15:58 | MySQL Server: Security: Privileges | Closed (2615 days) | S2 | 5.7.10 | Any | Any | Long user names prevent stored procedure/function creation |
78851 | 2015-10-15 22:19 | 2016-06-02 12:55 | MySQL Server | Not a Bug (3087 days) | S2 | 5.5 | CentOS | Any | longblob |
9890 | 2005-04-14 8:03 | 2006-07-24 23:38 | MySQL Server | Duplicate (6458 days) | S4 | 4.x | Any (any) | Any | Longer User Name Length |
20323 | 2006-06-07 19:17 | 2006-11-29 13:21 | MySQL Query Browser | Closed (6330 days) | S3 | 1.1.20 | Windows (Windows XP) | Any | Longgg Scrollbar Area even if content fits in SQL Query Area |
47800 | 2009-10-02 16:54 | 2011-02-16 23:44 | Connector / ODBC | Verified (4922 days) | S2 | 5.1.5 | Windows | Any | LONGTEXT data is truncated when retrieved using DAO ODBCDirect |
40932 | 2008-11-21 16:49 | 2011-02-16 23:43 | Connector / ODBC | Closed (5279 days) | S2 | 5.1.5 | Windows (XP) | Any | LONGTEXT fields are converted to text(255) in Access 97 |
50939 | 2010-02-05 9:10 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4915 days) | S5 | all | Any | Any | Loose Index Scan unduly relies on engine to remember range endpoints |
39645 | 2008-09-25 9:08 | 2011-02-16 23:43 | MySQL Cluster: Disk Data | Closed (5616 days) | S3 | mysql-5.1.28-ndb-6.3.18 | Any | Any | Losing size info for VARCHAR/CHAR for disk-data could segfault API apps |
93809 | 2019-01-04 2:55 | 2019-02-16 1:00 | MySQL Server: Replication | No Feedback (1869 days) | S3 | 5.7.24 | Any | Any | lost a whole file's gtid |
6729 | 2004-11-20 11:53 | 2005-02-07 15:13 | MySQL Server: MyISAM storage engine | Can't repeat (6990 days) | S2 | bk 4.1.8-latest/5.0 | Linux (Linux) | Any | Lost connection during "regexp" query |
76587 | 2015-04-03 12:16 | 2015-05-08 5:37 | MySQL Utilities: Binlog Events | Duplicate (3248 days) | S1 | 5.6.21-24 | Linux | Any | Lost events on MIXED based replication |
12404 | 2005-08-05 19:59 | 2005-08-26 16:10 | MySQL Server | Won't fix (6790 days) | S2 | 4.1.13 | Any (All) | Any | LOWER() lowercases characters in UTF-8 incorrectly |
3119 | 2004-03-09 10:05 | 2012-05-18 20:19 | MySQL Server | Duplicate (7325 days) | S2 | 4.1.1, 4.1.1a | Any (All) | Any | LPAD broken when string is exactly pad length |
2373 | 2004-01-13 8:03 | 2012-06-10 20:45 | MySQL Server: Compiling | Duplicate (4931 days) | S3 | 4.0.14,5.1 | Linux (Linux) | Any | LSB MySQL Porting Notes: _POSIX_PATH_MAX not defined by LSB |
5321 | 2004-08-31 17:19 | 2004-09-01 18:20 | MySQL Administrator | Not a Bug (7149 days) | S1 | 1.0.11 | Linux (SuSE Linux 9.1 Professional) | Any | MA 1.0.11 does not compiled against MySQL 4.0.20 |
37886 | 2008-07-04 17:21 | 2008-07-04 18:36 | MySQL Server: Documentation | Not a Bug (5747 days) | S3 | Any | Any | mailing list often refuses me, wihtout proper reasons | |
54336 | 2010-06-08 13:33 | 2011-02-16 23:44 | Tests: Server | Can't repeat (5043 days) | S3 | 5.1.47 | Linux (CentOS 5.2) | Any | main.alter_table-big fails |
81295 | 2016-05-03 13:35 | 2016-05-03 16:10 | MySQL Server: Data Types | Verified (2887 days) | S3 | 5.5.49 | Ubuntu (15.10 (Wily)) | Any | main.bigint/rpl.rpl_stm_user_variables fail on Ubuntu 15.10 Wily in release mode |
41013 | 2008-11-25 13:53 | 2011-02-16 23:43 | MySQL Server: General | Closed (5251 days) | S2 | 6.0-rpl | Any | Any | main.bootstrap coredumps in 6.0-rpl |
41535 | 2008-12-17 10:57 | 2017-05-21 20:45 | MySQL Server: General | Duplicate (5581 days) | S2 | 6.0-rpl | Any | Any | main.bootstrap crashes: segmentation fault in intern_plugin_lock |
51907 | 2010-03-10 12:26 | 2021-05-02 20:45 | MySQL Server: Tests | Verified (5106 days) | S3 | 5.5.3 | Any | Any | main.ctype_utf8mb4_ndb fails persistently |
62340 | 2011-09-03 7:55 | 2011-12-26 20:15 | MySQL Server: Tests | Verified (4477 days) | S3 | 5.1.60,5.5.20,5.6.4 | Any | Any | main.endspace sporadic fails |
87936 | 2017-10-02 7:00 | 2018-04-09 11:15 | MySQL Server: Tests | Not a Bug (2181 days) | S3 | 8.0.3 | Any | Any | main.file_contents failing with INFO_SRC not containing git revision id |
62156 | 2011-08-12 15:57 | 2012-05-18 20:19 | MySQL Server: Tests | Verified (4613 days) | S3 | 5.5 | Any | Any | main.func_str fails when run with --repeat=2 |
38523 | 2008-08-01 21:56 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5503 days) | S3 | 6.0.7 | Linux (Redhat 5) | Any | main.gis fails with error message about unable to read data file |
47495 | 2009-09-21 20:07 | 2013-04-12 12:17 | MySQL Server: Packaging | Closed (4004 days) | S3 | 5.1.39 | Other (Ubunty lenny x64_86) | Any | main.innodb-zip fails on Ubuntu9 |
33939 | 2008-01-19 17:46 | 2008-01-19 18:27 | MySQL Server: Tests | Duplicate (5914 days) | S3 | 5.1.22 | Linux (LinuxFromScratch 6.3) | Any | main.join_nested test failure in test suite |
99064 | 2020-03-25 7:11 | 2020-03-25 8:04 | MySQL Server: Tests | Verified (1465 days) | S7 | 8.0.19 | Any | Any | main.mysql_client_test is unstable |
54847 | 2010-06-28 6:14 | 2023-12-16 19:25 | Tests: Server | Patch pending (5023 days) | S7 | M3 (Celosia), M4 (Dahlia) | Any | Any | main.mysql-bug41486 fails sporadically |
38122 | 2008-07-15 7:41 | 2011-02-16 23:43 | Tools: Pushbuild | Closed (5265 days) | S3 | 1 | Any | Any | main.mysqlslap fails sporadically |
70303 | 2013-09-11 19:24 | 2015-11-19 15:57 | MySQL Server: Partitions | Analyzing (3852 days) | S2 | 5.5.32 | MacOS | Any | main.partition sporadically fails when using the embedded server |
47582 | 2009-09-24 7:11 | 2022-12-04 20:45 | MySQL Server | Verified (3930 days) | S3 | 5.1, 5.5 | Windows (XP Russian, Bulgarian) | Any | main.perror-win fails on non-English versions of Windows |
45295 | 2009-06-03 10:49 | 2011-02-16 23:44 | MySQL Server: General | Closed (5388 days) | S3 | 5.4 | Any | Any | main.plugin does not work with utf8mb3 |
111156 | 2023-05-25 16:34 | 2023-05-26 13:11 | Tests: Server | Unsupported (308 days) | S7 | 8.0.33 | Debian (Fails on Debian sid and Ubuntu 20.04-23.04) | Other (s390x) | main.subquery_sj_all_bka_nobnl and main.subquery_sj_mat_bka_nobnl fail on s390x |
40574 | 2008-11-07 11:42 | 2018-09-25 21:49 | Tests: Server | Closed (5546 days) | S7 | 6.0-bugteam | Any (SLES-ia64a) | Any | main.thread_cache_size_func fails in pushbuild when run with pool of threads |
80875 | 2016-03-29 6:32 | 2016-06-07 8:04 | Tests | Closed (2852 days) | S3 | 5.7.11, 5.6.29 | Any | Any | main.wl6443_deprecation cannot run with ./mtr --repeat=2 (or more) |
68236 | 2013-01-31 14:58 | 2016-03-08 14:13 | MySQL Server: Replication | Verified (3697 days) | S4 | 5.6,5.7 | Any | Any | Make binlog and relay sizes dynamically configurable by "maximum size" |
49852 | 2009-12-21 17:43 | 2011-10-14 17:34 | MySQL Server: InnoDB Plugin storage engine | Closed (4550 days) | S4 | 5.0,5.1,5.1 plugin | Any | Any | make innodb checksum faster |
88725 | 2017-12-01 5:08 | 2018-01-31 16:31 | MySQL Workbench: Modeling | Verified (2249 days) | S4 | 6.3.10 | Any | Any | Make model templates better |
49089 | 2009-11-25 8:18 | 2011-02-16 23:44 | MySQL Server: Data Types | Verified | S4 | 5.0+ | Any | Any | Make rounding in expressions more precise |
8063 | 2005-01-21 8:40 | 2005-03-03 11:47 | MySQL Server | Closed (6966 days) | S3 | 4.1.10 | Linux (Linux Solaris) | Any | make test mysqldump [ fail ] |
7677 | 2005-01-05 5:01 | 2008-09-29 20:59 | MySQL Server | Not a Bug (5660 days) | S3 | 4.1.8a | Linux (Fedora Core 3) | Any | Make test (test suite) wierdness in 4.1.8a |
11549 | 2005-06-24 17:00 | 2005-06-24 17:05 | MySQL Server | Duplicate (6853 days) | S2 | 4.1.12 | Linux (CentOS 4) | Any | Make test error |
7373 | 2004-12-17 1:57 | 2012-05-18 20:19 | MySQL Server: Compiling | No Feedback (6959 days) | S2 | 4.1.8 | Linux (Linux Solaris) | Any | make test Errors (client_test) |
7893 | 2005-01-14 4:55 | 2005-01-19 8:01 | MySQL Server | Closed (7009 days) | S3 | 4.1.9 | Solaris (Solaris Linux) | Any | make test Errors (client_test) |
19829 | 2006-05-15 19:31 | 2011-02-16 23:43 | MySQL Server: Charsets | Closed (5435 days) | S2 | 5.0.27,5.0.32.5.0.41 | Linux (Linux x86_64, ia64) | Any | make test Failed in mysql_client_test *with --with-charset=utf8* |
33104 | 2007-12-10 5:34 | 2018-09-25 21:47 | MySQL Server: Tests | Can't repeat (5951 days) | S7 | 5.0.51 | Linux (2.6.22.10 (Debian 4.0 r1)) | Any | make test Failed mysqlcheck (t_bug25347?) |
18176 | 2006-03-13 1:58 | 2011-02-16 23:43 | MySQL Server: Compiling | Closed (5428 days) | S3 | 5.0.19 | Linux (Redhat Linux) | Any | make test fails if server built with --without-innodb |
101720 | 2020-11-23 13:52 | 2020-11-24 5:07 | MySQL Server: DML | Verified (1222 days) | S4 | 8.0 | Any | Any | Make the last argument of the LPAD/RPAD(s, length, c) functions optional |
110945 | 2023-05-08 6:36 | 2023-05-08 9:31 | MySQL Server: Optimizer | Verified (326 days) | S6 | 8.0 | Any | Any | make_year_constant should set max_length=4 |
39902 | 2008-10-07 8:57 | 2011-02-16 23:43 | MySQL Workbench | Won't fix (5489 days) | S4 | 5.0.22 | Any | Any | making "synchronize" more friendly |
9446 | 2005-03-29 9:07 | 2005-06-07 15:35 | MySQL Server | No Feedback (6870 days) | S3 | 5.0 alpha | Windows (win xp) | Any | malayalam characters in unicode format |
18494 | 2006-03-24 17:03 | 2006-04-04 19:55 | MySQL Server: Documentation | Closed (6569 days) | S3 | 4.1 | Any (any) | Any | Malformulation in 4.1 Reference Manual, chapter 11.4.2: BINARY type |
15150 | 2005-11-22 21:12 | 2005-12-30 7:31 | MySQL Server: Command-line Clients | No Feedback (6664 days) | S3 | 5.0.15 | MacOS (OSX Server: Kernel Version 8.2.0) | Any | malloc error when pasting length query |
2550 | 2004-01-29 2:26 | 2005-08-18 15:10 | MySQL Server: Documentation | Closed (6798 days) | S4 | n/a | n/a | Any | manual bundled in tarballs hardly manageable |
61329 | 2011-05-27 15:17 | 2011-05-31 18:55 | MySQL Server: Documentation | Not a Bug (4686 days) | S3 | 5.1 and maybe others | Any | Any | manual conains a bad paragraph on decimal/numeric precision |
71661 | 2014-02-11 1:07 | 2014-02-18 17:08 | MySQL Server: Documentation | Closed (3692 days) | S3 | Any | Any | Manual describes InnoDB log limits incorrectly | |
71638 | 2014-02-09 14:41 | 2016-05-13 19:29 | MySQL Server: Documentation | Closed (2877 days) | S3 | 5.6 | Any | Any | Manual does NOT explain "insert intention" lock mode properly |
72113 | 2014-03-24 17:26 | 2014-06-18 17:17 | MySQL Server: Documentation | Closed (3572 days) | S3 | 5.5, 5.6 | Any | Any | Manual does not explain "silent length reduction" for index prefix |
79688 | 2015-12-17 10:34 | 2016-02-17 19:14 | MySQL Server: Documentation | Closed (2963 days) | S3 | any | Any | Any | Manual does NOT explain Data_length vs Index_length properly for InnoDB tables |
85749 | 2017-03-31 16:45 | 2018-05-15 18:45 | MySQL Server: Documentation | Closed (2145 days) | S3 | 5.7 | Any | Any | Manual does NOT explain gap locks set by SELECT ... FOR UPDATE |
79665 | 2015-12-16 10:50 | 2017-05-31 20:02 | MySQL Server: Documentation | Closed (2494 days) | S3 | any | Any | Any | Manual does NOT explain locks set by INSERT ... ON DUPLICATE KEY UPDATE properly |
71916 | 2014-03-03 16:52 | 2016-10-26 13:43 | MySQL Server: Documentation | Closed (2711 days) | S3 | 5.6 | Any | Any | Manual does NOT explain locks set for UPDATE ... WHERE PK='const' properly |
71346 | 2014-01-11 15:36 | 2017-03-24 7:56 | MySQL Server: Documentation | Won't fix (2562 days) | S3 | 5.6 | Any | Any | Manual does not provide details on mysqladmin debug output |
71821 | 2014-02-24 17:58 | 2014-03-14 14:19 | MySQL Server: Documentation | Closed (3668 days) | S3 | 5.6 | Any | Any | Manual doesn't explain that max_connections is "autosized" when ulimit -n is low |
13845 | 2005-10-07 15:02 | 2008-09-29 22:10 | MySQL Server | Closed (5660 days) | S2 | 4.1.14 | Windows (XP) | Any | Manual error on page 183 (A4 format) |
97995 | 2019-12-16 9:05 | 2020-01-24 19:44 | MySQL Workbench: Documentation | Closed (1526 days) | S3 | 8, revision: 64534 | Any | Any | Manual give preference defaults than show in MWB |
52615 | 2010-04-06 9:27 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5105 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | Manual incorrectly states limit of 31 bytes for table attributes |
6055 | 2004-10-13 1:11 | 2004-10-13 16:39 | MySQL Server: Documentation | Closed (7107 days) | S3 | All | Any (All) | Any | Manual not explicit on display width vs field length for numeric types |
82913 | 2016-09-08 21:49 | 2016-10-18 17:55 | MySQL Server: Documentation | Closed (2719 days) | S3 | 5.7 | Any | Any | manual should clarify storage requirements for variable length character sets |
93882 | 2019-01-10 20:39 | 2019-01-13 18:26 | MySQL Server: DML | Can't repeat (1902 days) | S2 | 5.6.42 | CentOS | x86 | Many queries executing delete returns "starting index read" |
73248 | 2014-07-09 19:51 | 2020-09-30 18:23 | MySQL Server: DML | Closed (1276 days) | S2 | 5.5.8, 5.5.31, 5.5.34, 5.6.20, 5.7.5 | Any | Any | Many, many classes of string-to-integer conversion bug |
38365 | 2008-07-25 9:07 | 2008-09-26 10:44 | MySQL Server: Maria storage engine | Can't repeat (5663 days) | S1 | 6.0.6 | Any | Any | Maria 200% CPU in lf_hash_delete () and initialize_bucket () at lf_hash.c |
42516 | 2009-02-01 14:10 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S2 | 6.0-maria | Any | Any | Maria assertion at ma_key_recover.c:68: _ma_unpin_all_pages() |
39710 | 2008-09-28 11:34 | 2009-01-08 11:05 | MySQL Server: Maria storage engine | Closed (5559 days) | S1 | 5.1-maria, 6.0-maria | Any | Any | Maria assertion in maria_disable_non_unique_index |
43131 | 2009-02-24 8:57 | 2009-03-10 21:00 | MySQL Server: Maria storage engine | Closed (5498 days) | S3 | Windows | Any | Maria compile error 6.0-main | |
38474 | 2008-07-30 21:09 | 2009-03-10 14:33 | MySQL Server: Maria storage engine | Closed (5498 days) | S1 | 6.0-bzr | Any | Any | Maria crash in _ma_setup_live_state (pushbuild2) |
34089 | 2008-01-27 13:34 | 2008-03-04 17:08 | MySQL Server: Maria storage engine | Closed (5869 days) | S1 | 5.1.23-maria | Any | Any | Maria crash on LOAD INDEX after FLUSH TABLES |
39210 | 2008-09-03 11:19 | 2009-01-09 14:58 | MySQL Server: Maria storage engine | Closed (5558 days) | S1 | 5.1-maria, 6.0-maria | Any | Any | Maria deadlock in _ma_bitmap_wait_or_flush |
39446 | 2008-09-15 8:49 | 2020-09-13 20:45 | MySQL Server: Maria storage engine | Duplicate (5631 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in pagecache_read |
40025 | 2008-10-14 16:06 | 2008-11-05 21:11 | MySQL Server: Maria storage engine | Can't repeat (5623 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in translog_buffer_lock, _ma_unlock_key_del, wait_for_update_bin |
40391 | 2008-10-29 10:35 | 2009-01-08 10:39 | MySQL Server: Maria storage engine | Closed (5559 days) | S1 | 6.0-bzr | Any | Any | Maria deadlock in trnman_get_min_trid , trnman_end_trn |
39444 | 2008-09-14 20:04 | 2013-07-04 13:22 | MySQL Server: Maria storage engine | Won't fix (3921 days) | S1 | 6.0.7 | Any | Any | Maria endless loop in lfind on commit |
42916 | 2009-02-17 8:13 | 2010-05-26 17:51 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S3 | 6.-0-tree | Linux (Debian 5.0) | Any | Maria not 'crash-me' safe |
42509 | 2009-02-01 9:20 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S2 | 6.0-maria | Any | Any | Maria write_block_record: Assertion `data_length < ((block_size) * 3 / 4)' |
39665 | 2008-09-26 12:02 | 2009-01-08 11:09 | MySQL Server: Maria storage engine | Closed (5559 days) | S3 | 5.1-maria | Linux | Any | Maria: assertion in block format during table scan |
41038 | 2008-11-25 22:49 | 2010-05-26 18:00 | MySQL Server: Maria storage engine | Unsupported (5056 days) | S3 | 6.0-maria | Any | Any | Maria: assertion in free_block() when dropping open table (pushbuild2) |
40579 | 2008-11-07 15:20 | 2009-03-10 14:39 | MySQL Server: Maria storage engine | Closed (5498 days) | S3 | 5.1-maria | Any | Any | Maria: assertion in page cache in check_and_set_lsn() |
41127 | 2008-11-29 22:09 | 2009-01-08 10:45 | MySQL Server: Maria storage engine | Closed (5559 days) | S3 | 5.1-maria | Linux | Any | Maria: assertion when SHOW ENGINE MARIA LOGS and missing logs |
38484 | 2008-07-31 10:55 | 2008-11-07 15:59 | MySQL Server: Maria storage engine | Closed (5621 days) | S1 | 6.0.6-alpha, 6.0.7pre,6.0.7,6.0.8pre | Any | Any | maria: DELETE causes crash or index corruption |
40990 | 2008-11-24 18:52 | 2009-03-10 13:52 | MySQL Server: Maria storage engine | Closed (5498 days) | S3 | 5.1-maria,6.0-maria | Solaris (sparc64) | Any | Maria: failure of maria.test & maria_notemebedded in deadlock detection |
40425 | 2008-10-30 11:50 | 2008-12-17 10:30 | MySQL Server: Maria storage engine | Can't repeat (5581 days) | S1 | 6.0 | Any | Any | Maria: ha_maria::enable_indexes(uint): Assertion `0' failed. |
40731 | 2008-11-14 9:06 | 2020-09-13 20:45 | MySQL Server: Maria storage engine | Duplicate (5551 days) | S3 | 5.1-maria | Linux | Any | Maria: hang (probably in page cache) under concurrency |
39248 | 2008-09-04 15:06 | 2009-01-09 15:28 | MySQL Server: Maria storage engine | Closed (5558 days) | S3 | 5.1-maria, 6.0-bk | Linux | Any | Maria: INSERT ON DUPLICATE KEY UPDATE gives error if using a view |
37276 | 2008-06-09 8:25 | 2008-07-10 14:57 | MySQL Server: Maria storage engine | Closed (5741 days) | S2 | 5.1-maria | Linux | Any | Maria: various index corruption, block format assertion failure |
50440 | 2010-01-19 11:26 | 2012-02-10 14:23 | MySQL Server: Replication | Closed (4431 days) | S2 | 5.1+ | Any | Any | mark [INSERT|REPLACE|CREATE]...SELECT unsafe if updated table has autoinc column |
50439 | 2010-01-19 11:16 | 2011-09-30 18:19 | MySQL Server: Replication | Closed (4564 days) | S2 | 5.1+ | Any | Any | mark INSERT...SEL...ON DUP KEY UPD,REPLACE...SEL,CREATE...[IGN|REPL] SEL unsafe |
57250 | 2010-10-05 14:07 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (4924 days) | S2 | 5.1+ | Any | Any | mark INSERT...SELECT with autoinc column unsafe when innodb_autoinc_lock_mode=2 |
49222 | 2009-11-30 17:46 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5128 days) | S2 | 5.1+ | Any | Any | Mark RAND() as unsafe |
48382 | 2009-10-28 16:12 | 2016-10-16 20:45 | MySQL Server: Replication | Verified | S2 | 5.1+ | Any | Any | mark reads from mysql.* and information_schema.* as unsafe |
47995 | 2009-10-12 12:10 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5128 days) | S2 | 5.1+ | Any | Any | Mark system functions as unsafe |
67615 | 2012-11-16 16:21 | 2018-01-26 16:20 | MySQL Server: InnoDB storage engine | Not a Bug (2254 days) | S2 | 5.5.28 | Linux (6.2) | Any | Massive conccurent inserts and lock wait timeout |
64300 | 2012-02-11 12:57 | 2012-06-27 1:00 | MySQL Server: Replication | No Feedback (4294 days) | S1 | 5.5.19 | Linux (FC15 32 bit) | Any | master crashes with sigfault as slave connects |
62290 | 2011-08-29 2:40 | 2014-01-16 5:37 | MySQL Server: Replication | Closed (3725 days) | S3 | 5.1.52 | Any | Any | master does not recover from partial event at end of binlog after crash |
69249 | 2013-05-16 4:14 | 2013-09-19 13:33 | MySQL Server: Replication | Closed (3844 days) | S3 | 5.6.11 | Any | Any | master_delay does not perform proper type checking |
71387 | 2014-01-15 7:25 | 2014-01-20 16:43 | MySQL Server: Documentation | Closed (3721 days) | S3 | 5.6.14, 5.5.15 | Any | Any | master_info_repository option file format not documented |
41525 | 2008-12-17 0:07 | 2011-02-16 23:43 | MySQL Enterprise Monitor: Agent | Closed (5504 days) | S3 | 2.0.4.7141 | Any | Any | master_uuid discovery does not work with mysql < 5.1 |
52185 | 2010-03-18 15:40 | 2010-03-29 6:33 | MySQL Server: Replication | Not a Bug (5114 days) | S2 | 5.1.44 | Linux | Any | master-master-slave replication recovery |
38352 | 2008-07-24 17:56 | 2012-05-18 20:19 | MySQL Server: FULLTEXT search | Verified (5727 days) | S4 | 5.1 | Any | Any | MATCH ... AGAINST ... WITH PARSER ... |
26726 | 2007-02-28 18:21 | 2007-09-12 18:47 | MySQL Server: Documentation | Closed (6043 days) | S3 | 5.0.38 4.1.23 | Linux (Linux) | Any | max amount of columns not/unsufficient documented |
35191 | 2008-03-10 19:48 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (5862 days) | S4 | 5.x | Any | Any | max datafile length is shown in'show table status' but not max index file length |
5365 | 2004-09-02 9:01 | 2004-09-02 11:42 | MySQL Server: ISAM storage engine | Not a Bug (7148 days) | S2 | 4.0.18 - nt | Windows (windows XP) | Any | MAX fuction from integer column from empty set returns null insted... |
13835 | 2005-10-07 10:54 | 2006-02-02 1:02 | MySQL Server | Closed (6630 days) | S3 | 5.0.13, 5.0.15-rc-BK | Linux (Linux) | Any | max key length is 1000 bytes when trying to create a fulltext index |
2130 | 2003-12-16 9:55 | 2004-02-21 11:37 | MySQL Server | Closed (7342 days) | S2 | 4.1.1 alpha | Linux (Linux) | Any | Max key length problem |
39995 | 2008-10-13 11:39 | 2008-10-15 10:56 | MySQL Server: Documentation | Closed (5644 days) | S3 | 5.1+ | Any | Any | Max number of API nodes for cluster |
1459 | 2003-10-01 14:24 | 2011-02-16 23:42 | MySQL Server: DML | Verified (6698 days) | S4 | 4.0.15a | Any (All) | Any | max_allowed_packet does not just control the maximum allowed packet size |
22853 | 2006-09-30 1:59 | 2011-02-16 23:43 | MySQL Server: General | Verified (6390 days) | S4 | 4.1.14-nt | Windows (Windows XP) | Any | max_allowed_packet misnomer - CONCAT() in SQL command allows for loss of data |
103387 | 2021-04-20 17:27 | 2021-04-26 14:33 | MySQL Server | Duplicate (1068 days) | S3 | 8.0.19 | Any | Any | max_allowed_packet prevents use of LONGBLOB and large JSON |
67448 | 2012-11-01 13:13 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4077 days) | S4 | 5.1.63 | Linux | Any | max_allowed_packet problem on mysql client but not mysqldump |
24698 | 2006-11-29 15:14 | 2006-12-19 18:46 | MySQL Server: Documentation | Closed (6310 days) | S3 | 5.1.14 | N/A | Any | max_binlog_cache_size need better details documented |
111611 | 2023-06-28 18:06 | 2023-06-29 6:45 | MySQL Server: Options | Not a Bug (274 days) | S3 | Any | Any | Max_connection in MySQL | |
37816 | 2008-07-02 18:29 | 2011-02-16 23:43 | MySQL Enterprise Monitor: Advisors/Rules | Closed (5617 days) | S2 | 1.3.2.9118 | Any | Any | max_connections event is blocking with an open "success" alert |
82962 | 2016-09-13 0:52 | 2017-03-13 14:52 | MySQL Server: Documentation | Closed (2573 days) | S3 | 5.6.31 | Any | Any | max_digest_length connected to, not replaced by, performance_schema_max_digest_l |
35074 | 2008-03-05 11:47 | 2008-03-26 18:04 | MySQL Server | Closed (5847 days) | S2 | 5.1 | Any | Any | max_used_connections is not correct |
49939 | 2009-12-26 10:32 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5146 days) | S3 | 5.1 - likely any recent | Any | Any | max_user_connections unclear |
14651 | 2005-11-04 18:30 | 2005-12-09 18:54 | MySQL Server | No Feedback (6685 days) | S3 | 4.1.11-nt | Windows (Windows XP) | Any | MAX() returns -1 on UNSIGNED INT with maximum value |
75027 | 2014-11-27 16:54 | 2014-12-16 18:15 | MySQL Proxy: Core | Verified (3391 days) | S4 | 0.8.5 alpha | Linux | Any | Maximum (debug) logging level doesn't log connections, queries or backend used |
25225 | 2006-12-20 20:40 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5428 days) | S3 | mysql-5.1 | Linux (Linux 2.6.9) | Any | Maximum attribute length has changed? |
42050 | 2009-01-12 14:14 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5474 days) | S5 | all | Any | Any | Maximum constraint name lengths not documented |
79519 | 2015-12-04 9:22 | 2015-12-07 4:25 | MySQL Server: DML | Verified (3035 days) | S3 | 5.7.8, 5.6.29, 5.7.11 | Any | Any | Maximum display width for select list is different for 'utf8' and 'utf8mb4' |
111865 | 2023-07-24 18:39 | 2024-03-26 11:06 | MySQL Server: Documentation | Need Feedback (7 days) | S3 | 8.0 | Any | Any | Maximum file size limit may reduce 64 TiB InnoDB limit substantially |
72744 | 2014-05-26 4:21 | 2014-05-26 11:54 | MySQL Server: General | Not a Bug (3595 days) | S5 | Any | Any | maximum mysql table name length | |
88948 | 2017-12-16 10:58 | 2017-12-20 6:56 | MySQL Cluster: plugin | Verified (2291 days) | S4 | 7.6.3 | Any | Any | Maximum number of NDB nodes is not sufficient |
35209 | 2008-03-11 12:53 | 2008-03-19 13:32 | MySQL Server | Not a Bug (5854 days) | S2 | 5.0.45 | Linux (Trustix Secure Linux 3.0 / 2.6.19.2-1trsmp / glibc-2.3.5-10tr) | Any | maximum number of threads with MySQL binary RPMs |
29413 | 2007-06-28 8:38 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | Closed (5343 days) | S4 | 5.0.41 | Any | Any | Maximum performance of OLTP benchmark is not so scalable on multi-cpu |
29108 | 2007-06-14 15:05 | 2008-01-09 17:32 | MySQL Server: Data Types | Won't fix (5924 days) | S3 | 4.1.23 | IBM AIX (4.3 + 5.2 (32 bit)) | Any | Maximum positive (32 bit) timestamp value turning negative |
29109 | 2007-06-14 15:10 | 2008-01-09 17:31 | MySQL Server: Data Types | Won't fix (5924 days) | S3 | 4.1.23 | Other (SCO) | Any | Maximum positive timestamp value shifted by 3 hours |
559 | 2003-05-31 12:16 | 2003-06-16 7:47 | MySQL Server | Not a Bug (7592 days) | S3 | 4.0.13 | Windows (Windows) | Any | Maximum precision for DECIMAL column in MySQL on Windows |
42026 | 2009-01-11 6:55 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5549 days) | S3 | all | Any | Any | Maximum value for max_heap_table_size in the manual is not correct |
66912 | 2012-09-21 15:28 | 2013-01-15 1:00 | MySQL Server: Options | No Feedback (4092 days) | S3 | 5.6.6 | Windows | Any | Maximum value for open-files-limit |
79872 | 2016-01-07 12:43 | 2019-12-10 0:18 | MySQL Server: Documentation | Closed (1571 days) | S3 | ALL | Any | Any | Maximum value for system variable timestamp is 2147483647 |
21060 | 2006-07-14 14:03 | 2006-07-14 15:06 | MySQL Server | Not a Bug (6468 days) | S3 | 5.0.18 | Linux (CentOS Linux i686 2.6.9-34.ELsmp) | Any | Maximum value of MAX() on string is 9999 |
57320 | 2010-10-07 16:47 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (4824 days) | S3 | 5.1.47 | Any | Any | Maximum width of row documented at 65,535 bytes is wrong |
80312 | 2016-02-09 8:14 | 2016-02-09 8:23 | MySQL Server: Options | Verified (2971 days) | S3 | 5.7.11 | CentOS (6.6) | Any | maximum_query_cache_size cannot be set |
79214 | 2015-11-10 21:39 | 2016-02-08 12:58 | MySQL Cluster: Documentation | Closed (3055 days) | S2 | 7.3+ | Any | Any | MaxNoOfExecutionThreads documentation wrong for 7.3.3+ |
13048 | 2005-09-07 19:43 | 2005-11-22 21:17 | Connector / J | Closed (6702 days) | S3 | 3.1.7+ | Any | maxQuerySizeToLog is not applied | |
105895 | 2021-12-14 18:47 | 2023-06-06 17:37 | MySQL Cluster: Cluster (NDB) storage engine | Closed (331 days) | S3 | 8.0.27 | Any | Any | maxRecordSize required to update in BACKUP_FRAGMENT_REQ for LCPs |
68609 | 2013-03-08 0:28 | 2014-10-09 16:07 | MySQL Server: Replication | Won't fix (3459 days) | S3 | 5.5.30, 5.6.10 | Any | Any | MBR: Unique key updates are not marked unsafe, replication fails |
15539 | 2005-12-06 21:58 | 2007-03-15 20:41 | Connector / ODBC | Closed (6224 days) | S3 | 3.51.12 | Solaris (Solaris) | Any | MD5 Wrong For 3.51.12 Solaris 8 (pkg format, SPARC, 64-bit) |
48940 | 2009-11-20 11:51 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (4955 days) | S3 | 6.0-codebase-bugfixing | Any | Any | MDL deadlocks against mysql_rm_db |
49988 | 2009-12-30 9:25 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5136 days) | S2 | 4.1, 5.0, 5.1, 5.5.99, next-4284 | Any | Any | MDL deadlocks with mysql_create_db, reload_acl_and_cache |
50784 | 2010-02-01 9:01 | 2011-02-16 23:44 | MySQL Server: Locking | Closed (5136 days) | S1 | mysql-next-4284-stage | Any | Any | MDL: Assertion `m_tickets.is_empty() || m_tickets.front() == m_trans_sentinel' |
31891 | 2007-10-26 21:02 | 2008-03-06 13:02 | MySQL Server: General | Closed (5867 days) | S4 | 5.1 | Linux | Any | Meaningful stack trace |
75722 | 2015-02-02 10:31 | 2015-06-10 18:57 | MySQL Enterprise Backup | Closed (3215 days) | S2 | 3.11.1 | Linux | Any | MEB 3.11.1 Failed trying to flush for export |
75899 | 2015-02-13 18:55 | 2015-02-26 20:37 | MySQL Enterprise Backup | Won't fix (3319 days) | S1 | 3.10.1 | Linux | Any | meb fails to apply log intermittently |
46348 | 2009-07-23 11:06 | 2011-02-16 23:44 | MySQL Enterprise Monitor: Server | Closed (5303 days) | S3 | 2.1.0 | Any | Any | MEM cookie lengths with other apps on server make everything unusable |
83938 | 2016-11-23 22:27 | 2016-11-24 11:49 | MySQL Enterprise Monitor | Not a Bug (2682 days) | S3 | 3.2.4 | Red Hat | Any | MEM purge of the statements by server table fails causing it to continue growing |
112304 | 2023-09-09 18:07 | 2024-01-03 15:22 | MySQL Server: Optimizer | Closed (86 days) | S3 | 8.0 | Any | Any | MEM_ROOT::AllocBlock() does not satisfy minimum_length bigger than wanted_length |
62210 | 2011-08-19 11:47 | 2012-02-02 19:59 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (4439 days) | S2 | 5.1.48 (1.0.9) | Linux (2.6.18-164.el5) | Any | memory corruption for THD after deadlock in foreign key reference constrain |
19885 | 2006-05-17 14:08 | 2006-05-19 23:39 | MySQL Cluster: Replication | Closed (6524 days) | S1 | 5.1.11 | Linux (Linux/x86 (32 bit)) | Any | memory corruption with ndb binlog in conjunction with online alter table |
12460 | 2005-08-09 14:44 | 2005-08-24 17:41 | MySQL Server | Closed (6792 days) | S2 | 4.1.13 | Linux (Linux) | Any | MEMORY engine: table is full error, btree index / 64bit |
21798 | 2006-08-23 17:36 | 2006-10-25 19:21 | MySQL Server: General | Closed (6365 days) | S2 | 5.0.24 | Linux (Linux 2.6.15 (Ubuntu 6.06 LTS)) | Any | memory leak during query execution with subquery in column list using a function |
13471 | 2005-09-25 17:13 | 2005-09-26 9:52 | MySQL Server | Closed (6759 days) | S2 | 5.0.14-rc, tadays pull | Linux (Linux) | Any | Memory leak in ha_tina |
94288 | 2019-02-12 9:54 | 2020-03-03 19:10 | MySQL Server | Can't repeat (1863 days) | S2 | 8.0.13 | Debian (9) | x86 | Memory leak Innodb Cluster |
110518 | 2023-03-27 23:53 | 2023-12-23 13:54 | MySQL Server: Group Replication | Closed (97 days) | S3 | all, 8.0 | Any | Any | Memory leak possible |
34338 | 2008-02-06 1:45 | 2008-03-01 10:59 | Connector / NET | Closed (5872 days) | S2 | Any | Any | Memory leak resulting from procedure cache | |
85970 | 2017-04-17 7:44 | 2017-04-17 13:54 | MySQL Server: InnoDB storage engine | Verified (2538 days) | S3 | 5.6.36 | Linux | Any | Memory leak with transactions greater than 10% of the total redo log size |
15477 | 2005-12-05 9:29 | 2005-12-06 13:05 | Connector / J | Closed (6688 days) | S1 | 3.1.12 | Windows (Windows 2000) | Any | Memory Leak, depending on SQL statement |
293 | 2003-04-15 10:56 | 2019-05-14 14:19 | MySQL Server | Closed (7596 days) | S2 | 4.0.12-debug-log | Other (SCO Openserver 5.0.6) | Any | Memory leaks? |
170 | 2003-03-20 11:10 | 2019-04-08 13:45 | MySQL Server: MyISAM storage engine | Closed (7680 days) | S2 | 3.23 and 4.0 | Any (ALL) | Any | Memory overflow in storing a row with BLOB and many NULL columns |
628 | 2003-06-10 17:44 | 2003-07-03 6:47 | MySQL Server | Closed (7575 days) | S1 | 3.23.56/4.0.13 | Windows (Windows) | Any | Memory overrun with concat("$",format(col_m,2)) |
49353 | 2009-12-02 15:13 | 2010-03-23 15:56 | MySQL Server: Backup | Closed (5120 days) | S3 | 6.0-backup, 6.0.14 | Any | Any | Memory tables + max_heap_table_size can cause backup/restore problems |
48666 | 2009-11-10 12:15 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (4956 days) | S3 | 5.0.88-bzr, 5.1.41, 5.1.42-bzr | Any | Any | Memory tables + max_heap_table_size can cause replication problems |
30591 | 2007-08-23 10:56 | 2013-03-03 20:45 | MySQL Server: Memory storage engine | Verified (6063 days) | S4 | 5.0.46 | Any | Any | memory tables should allow "format=dynamic" |
25007 | 2006-12-12 13:05 | 2011-03-21 4:01 | MySQL Server: Memory storage engine | Verified (4757 days) | S4 | 5.0, 5.1, 5.5 | Any | Any | memory tables with dynamic rows format |
39430 | 2008-09-12 23:23 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5657 days) | S3 | all | Any | Any | Memory usage of Attributes with NULL Value, Cluster |
69490 | 2013-06-17 10:45 | 2015-12-10 16:17 | MySQL Server: Documentation | Closed (3032 days) | S3 | 5.6, 5.7 | Any | Any | Memory usage of P_S |
18160 | 2006-03-12 1:22 | 2006-06-03 13:35 | MySQL Server: Memory storage engine | Closed (6509 days) | S3 | 5.0.18, 4.1,x, 4.0.x | Linux (Debian Linux) | Any | Memory-/HEAP Table endless growing indexes |
80794 | 2016-03-18 18:02 | 2016-04-04 17:12 | MySQL Server: Documentation | Closed (2916 days) | S3 | 5.7 | Any | Any | MEMORYengine memory usage |
85096 | 2017-02-21 7:56 | 2017-02-21 16:15 | MySQL Server: Compiling | Closed (2593 days) | S3 | 5.7.18 | Any | Any | merge_large_tests needs /bigobj in 5.7 |
15884 | 2005-12-20 10:03 | 2006-06-05 17:57 | MySQL Server | Can't repeat (6507 days) | S1 | 5.0.18-nt | Windows (windows/Linux suse) | Any | Message "Column length too big for column" while inserting into temporary table |
42488 | 2009-01-30 18:35 | 2009-02-24 8:24 | MySQL Server: Prepared statements | Not a Bug (5512 days) | S3 | 5.1.30 | Any | Any | metadata field 'length' is 0 after preparing statement: "select ?" |
109834 | 2023-01-30 6:54 | 2023-02-28 17:13 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (395 days) | S3 | Linux | Any | Metadata is wrong after failure to invoke set_primary_instance | |
29303 | 2007-06-22 14:39 | 2007-07-13 21:01 | MySQL Server: General | Won't fix (6104 days) | S3 | Any | Any | Metadata of user variables varies between 5.0 and 5.1 | |
7458 | 2004-12-21 16:52 | 2004-12-23 8:03 | MySQL Server | Closed (7036 days) | S3 | 4.1.8 | Any | Microseconds are gobbled from the result of STR_TO_DATE() function | |
10238 | 2005-04-28 17:27 | 2008-01-09 7:17 | Connector / ODBC | Closed (5924 days) | S3 | 3.51 | Windows (Windows XP) | Any | Microsoft VB6 DataGrid control causes catastrophic failure |
90795 | 2018-05-09 1:23 | 2018-06-10 1:00 | MySQL Workbench: Migration | No Feedback (2120 days) | S2 | 6.3.9 | Windows (8.1) | x86 (64-bit) | Migration of BIT data from MSSQL to MySQL |
22859 | 2006-09-30 13:46 | 2007-09-06 5:32 | MySQL Migration Toolkit | Closed (6049 days) | S1 | 5.0-r4 | Windows (Windows) | Any | Migration Toolkit fails when migrating from Sybase - jdbc and workaround |
55626 | 2010-07-29 13:20 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4854 days) | S3 | all | Any | Any | MIN and MAX reading a delete-marked record from secondary index |
84758 | 2017-01-31 22:31 | 2017-02-03 18:40 | MySQL Server | Not a Bug (2611 days) | S1 | 5.1.17-log MySql Community Server (GPL) | Ubuntu (Ubuntu ("Ubuntu 14.04.3 LTS")) | Any | Min Max Functionality |
28184 | 2007-05-01 18:26 | 2007-11-27 19:11 | MySQL Server: Compiling | Closed (5967 days) | S3 | 5.1.17, 5.0.37,6.0 | Any | Any | min() and max() macro defines in my_global.h conflict with c++ headers |
59132 | 2010-12-23 14:15 | 2011-04-19 17:05 | MySQL Server: Data Types | Closed (4728 days) | S3 | 5.1.51, 5.1.54, 5.1.55 | Windows | Any | min() and max() remove unsignedness |
88918 | 2017-12-14 11:54 | 2018-02-05 13:33 | MySQL Server: Data Dictionary | Closed (2244 days) | S3 | 8.0.5 | Any | Any | Minimized serialized dictionary information |
11145 | 2005-06-07 17:02 | 2022-12-04 20:45 | MySQL Server: General | Verified (4853 days) | S4 | 4.0/4.1 | Any (All) | Any | Minor suggections for additional TimeZone support |
32707 | 2007-11-26 7:32 | 2008-01-14 18:47 | MySQL Server: General | Closed (5919 days) | S2 | Any | Any | misdimensioned buffer in protocol layer | |
46808 | 2009-08-19 11:34 | 2012-08-01 11:17 | MySQL Server: GIS | Duplicate (4258 days) | S3 | 5.1.36/5.4 | Any | Any | Misleading error message when trying to create a SPATIAL index on a BLOB column |
72601 | 2014-05-09 22:21 | 2015-01-29 13:12 | MySQL Server: Documentation | Closed (3347 days) | S4 | all | Any | Any | Misleading replication documentation |
68328 | 2013-02-09 19:34 | 2013-06-13 5:59 | MySQL Workbench: Administration | Closed (3942 days) | S2 | 5.2.46 | Windows (Can't Export Data) | Any | Mismatch on version of "mysqldump.exe" and "mysqld.exe" mak failure in Workbench |
34183 | 2008-01-31 0:36 | 2008-05-20 23:16 | MySQL Server: Logging | Closed (5792 days) | S3 | 5.1.24 | Any | Any | Missing DBUG_RETURN in alloc_root |
51488 | 2010-02-25 8:18 | 2011-02-16 23:44 | MySQL Server: Compiling | Closed (5130 days) | S3 | 5.5.99-m3 | Any (Unix) | Any | missing features and change behavior in cmake runs compared to autotools runs |
11098 | 2005-06-04 17:37 | 2005-08-12 17:38 | MySQL Migration Toolkit | Closed (6804 days) | S2 | Any | Missing length on creating indexes (UNIQUE INDEX or PK) with MEDIUMTEXT | ||
81179 | 2016-04-22 15:39 | 2020-07-30 17:02 | Connector / NET | Closed (1338 days) | S2 | 6.9.8.0 | Any | Any | missing length specifier for binary in resulting sql code |
68610 | 2013-03-08 7:32 | 2013-08-08 21:22 | MySQL Utilities | Closed (3886 days) | S3 | 1.2.x | Linux (Fedora) | Any | Missing man pages |
88738 | 2017-12-03 16:47 | 2018-10-03 2:09 | MySQL Server: Errors | Closed (2004 days) | S4 | 5.7, 8.0 | Any | Any | Missing vital error information in error message when failing to convert charset |
107224 | 2022-05-05 17:01 | 2022-09-19 9:19 | MySQL Server: Logging | Verified (693 days) | S3 | 8.0.29 | Any | Any | missleading Redo log format is error |
10177 | 2005-04-26 13:54 | 2005-04-27 15:47 | MySQL Websites: MySQL.com | Closed (6911 days) | S3 | Any | mistake | ||
27340 | 2007-03-21 15:56 | 2007-03-24 0:09 | MySQL Server: Tests | Can't repeat (6215 days) | S3 | Ver 8.41 Distrib 5.0.27 | Solaris (Solaris 8 SPARC) | Any | mix_innodb_myisam_binlog test fails |
39701 | 2008-09-27 16:59 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Closed (5462 days) | S2 | 5.1.28, 5.1, 6.0 bzr | Any | Any | Mixed binlog format does not switch to row mode on LOAD_FILE |
43046 | 2009-02-20 8:40 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5350 days) | S2 | 5.1.26+, 5.1, 6.0 bzr | Any | Any | mixed mode switch to row format with temp table lead to wrong result |
40013 | 2008-10-14 10:18 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5490 days) | S2 | 5.1.26+, 5.1, 6.0 bzr | Any | Any | mixed replication: row based format could lead to stale tmp tables on the slave |
49019 | 2009-11-24 2:11 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (4915 days) | S3 | 5.1+, 5.5.99-m3 | Any | Any | Mixing self-logging eng. and regular eng. does not switch to row in mixed mode |
26873 | 2007-03-06 13:51 | 2012-05-18 20:19 | MySQL Enterprise Monitor: Installing | No Feedback (6188 days) | S3 | 1.1 r4876 | MacOS (OS X 1.4.8 (Intel)) | Any | MNMAS Installation on OS X does not set correct permissions |
75515 | 2015-01-15 13:18 | 2015-01-19 16:00 | MySQL Cluster: Cluster (NDB) storage engine | Closed (3357 days) | S3 | 7.4 | Any | Any | Modify SHOW CREATE TABLE output for better OpenStack integration |
56330 | 2010-08-27 17:53 | 2015-11-09 15:24 | MySQL Enterprise Monitor: Web | Won't fix (3063 days) | S3 | 2.2.2.1730 | Any | Any | Monitor error messages without an error code |
45826 | 2009-06-29 15:04 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5198 days) | S3 | 5.1+ | Any | Any | More than one unsafe-warning per stmt can be returned to client |
72419 | 2014-04-22 10:40 | 2016-02-24 14:17 | MySQL Server: Documentation | Closed (2956 days) | S3 | 5.6.16 | Any | Any | More troubleshooting info for "unable to purge a record" message |
58584 | 2010-11-30 7:59 | 2011-03-10 16:50 | MySQL Server: Replication | Closed (4768 days) | S2 | trunk | Any | Any | Move timestamps in Slave_[SQL|IO]_Error to separate columns |
12272 | 2005-07-29 14:56 | 2005-07-29 15:12 | MySQL Migration Toolkit | Closed (6818 days) | S2 | 1.0.11 beta | Windows (Windows XP) | Any | MS access relationships not migrated |
97851 | 2019-12-02 16:15 | 2019-12-03 11:31 | Connector / ODBC | Not a Bug (1578 days) | S2 | 8.0.15 | Windows | Any | MS Access timeout using ODBC |
54320 | 2010-06-08 6:06 | 2012-05-18 20:19 | MySQL Workbench: SQL Editor | Duplicate (4656 days) | S4 | 5.2.22 RC2 | Any | Any | MS Excel compatible Query Result Export |
16384 | 2006-01-11 19:33 | 2006-01-12 14:09 | MySQL Migration Toolkit | Can't repeat (6651 days) | S3 | 1.0.21-rc | Windows (Windows 2003 SP1) | Any | MS SQL TEXT datatypes are incorrectly converted to VARCHAR(16) |
13515 | 2005-09-27 5:42 | 2005-09-30 17:53 | MySQL Server | Duplicate (6755 days) | S3 | 5.0.12-nt, 5.0.13 | Windows (WIN XP) | Any | Ms Visual Foxpro read 0.0 AS character field rather then decimal |
64127 | 2012-01-25 9:29 | 2015-01-09 10:18 | Tools: MTR / mysql-test-run | Closed (3367 days) | S3 | 5.1 bzr revno 3670, 5.5 | Any | Any | MTR --warnings option misses some of InnoDB errors and warnings |
44905 | 2009-05-15 14:46 | 2009-05-16 23:55 | MySQL Server: Tests | Not a Bug (5431 days) | S3 | 6.0.11 | Any | Any | MTR adds incorrect parameter for startup options in combinations file |
55003 | 2010-07-05 14:59 | 2011-02-16 23:44 | Tools: MTR / mysql-test-run | Closed (4825 days) | S3 | next-mr | Any | Any | Mtr does not get core dump information in next-mr and related trees. |
50940 | 2010-02-05 11:11 | 2018-09-25 21:51 | Tools: MTR / mysql-test-run | Can't repeat (5140 days) | S7 | 5.1, 6.0-codebase | Windows (Windows XP, cygwin 1.7) | Any | mtr doesn't work with cygwin 1.7 |
41054 | 2008-11-26 13:59 | 2011-02-16 23:43 | Tools: MTR / mysql-test-run | Won't fix (4847 days) | S3 | mtr_version=1 | Any | Any | mtr reports wrong binlog-format for skipped tests when combinations are used |
97844 | 2019-12-02 8:31 | 2020-07-01 2:46 | Tests: Replication | Verified (1367 days) | S7 | 8.0.17, 8.0.20 | CentOS | x86 | MTR rpl_gtid.rpl_multi_source_mtr_includes unstable |
53103 | 2010-04-23 9:34 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4875 days) | S3 | 6.0.14 | Any | Any | MTR test ps crashes in optimize_cond() when running with --debug |
89464 | 2018-01-30 7:32 | 2018-02-07 10:34 | MySQL Server: Document Store: X Plugin | Closed (2242 days) | S3 | 8.0.4 | Any | Any | MTR test x.connection_unixsocket_invalid failure |
62075 | 2011-08-03 17:37 | 2011-10-06 3:31 | Tools: MTR / mysql-test-run | Closed (4558 days) | S3 | 5.1.52 | Any | Any | mtr tests should not have to save & reset innodb_file_format_check |
38555 | 2008-08-05 7:14 | 2018-09-25 21:49 | MySQL Server: Tests | Won't fix (5684 days) | S7 | 6.0 | Any | Any | mtr_ping_with_timeout() failed in pushbuild |
40742 | 2008-11-14 13:10 | 2018-09-25 21:49 | Tests | Closed (5537 days) | S7 | 5.1-rpl | Any | Any | MTR_VERSION=1 perl mysql-test-run.pl --start-and-exit rpl_alter does not work |
39071 | 2008-08-27 12:10 | 2018-09-25 21:49 | MySQL Server: Tests | Closed (5537 days) | S7 | 5.1-rpl | Any | Any | mtr's check-testcase reports extra failures for correct test cases |
44054 | 2009-04-02 20:44 | 2011-02-16 23:43 | Tools: MTR / mysql-test-run | Closed (5034 days) | S3 | 5.1+ | Linux | Any | MTR2: --no-reorder does not prevent reordering |
44055 | 2009-04-02 21:05 | 2012-06-10 20:45 | Tools: MTR / mysql-test-run | Duplicate (4918 days) | S3 | 6.0-bzr | Linux | Any | MTR2: check-testcase is wrong when a previous test was skipped |
90361 | 2018-04-10 3:48 | 2021-08-06 13:44 | MySQL Server: Replication | Can't repeat (2156 days) | S2 | 5.7.17/5.7.21 | CentOS (7.0.1406(3.10.0-123.el7.x86_64)/7.4.1708(3.10.0-693.el7.x86_64)) | Any | MTS hang on Waiting for dependent transaction to commit |
77406 | 2015-06-18 15:03 | 2017-06-21 10:15 | MySQL Server: Replication | Closed (2473 days) | S3 | 5.6.25 | Any | Any | MTS must be able handle large packets with small slave_pending_jobs_size_max |
87489 | 2017-08-21 8:15 | 2021-09-06 12:47 | MySQL Server: Replication | Can't repeat (2388 days) | S2 | 5.7.16 | Any | Any | MTS ordered commit may cause deadlock with "FLUSH TABLES WITH READ LOCK"of slave |
60227 | 2011-02-23 21:56 | 2012-06-11 16:37 | MySQL Server: DDL | Closed (4309 days) | S5 | 5.1.54, 5.5.26 | Any | Any | Much overhead for MD5() and SHA1() on short strings |
49491 | 2009-12-06 23:14 | 2011-02-16 23:44 | MySQL Server: General | Closed (5131 days) | S5 | 5.1.38 and above | Any | Any | Much overhead for MD5() and SHA1() on short strings |
97955 | 2019-12-11 4:26 | 2019-12-11 11:28 | MySQL Server: Replication | Verified (1570 days) | S2 | 5.6/5.7/8.0, 8.0.18 | Any | Any | Multi 'show binary logs' statement may block transaction commit |
50095 | 2010-01-05 18:52 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5030 days) | S3 | 5.1.42, 5.5.99-m3,6.0.14-alpha | Any | Any | Multi statement including CREATE EVENT causes rotten binlog entry |
111027 | 2023-05-15 10:49 | 2023-10-27 17:07 | MySQL Server: Replication | Closed (172 days) | S2 | 5.7.42, 8.0.33 | Any | Any | Multi-column indexes with writest will cause HA_ERR_FOUND_DUPP_KEY |
110683 | 2023-04-13 13:21 | 2023-04-14 7:59 | MySQL Server: Replication | Verified (350 days) | S3 | 5.7, 8.0 | Any | Any | Multi-threaded slave statistics output is incorrect |
106580 | 2022-02-26 9:41 | 2022-03-02 14:56 | MySQL Server: Optimizer | Verified (758 days) | S3 | 8.0 | Any | Any | Multi-Valued Indexes only takes into account a portion of a whole data. |
75392 | 2015-01-02 14:45 | 2015-01-19 16:03 | MySQL Server: Stored Routines | Verified (3357 days) | S3 | any - case from 5.6.22 | Any | Any | Multiline comments treated inconsistently |
79437 | 2015-11-27 12:42 | 2015-11-27 12:42 | MySQL Server | Open | S4 | Any | Any | Multiple autonumber in the table | |
15087 | 2005-11-20 23:31 | 2006-03-14 8:19 | MySQL Server | No Feedback (6590 days) | S2 | 4.1.15 | Linux (GNU/Linux) | Any | multiple failures in testsuite |
57528 | 2010-10-18 15:01 | 2011-02-16 23:44 | MySQL Server: Embedded Library ( libmysqld ) | Verified | S4 | Any | Any | Multiple major version compatable embedded server/engine | |
4036 | 2004-06-07 12:41 | 2004-06-08 10:04 | MySQL Server | Closed (7234 days) | S3 | 4.0.18-max-debug | Windows (Windows XP) | Any | multiple SELECT DATE_FORMAT, incorrect results |
15976 | 2005-12-24 21:46 | 2005-12-27 20:44 | MySQL Server | Closed (6667 days) | S1 | 5.1-20051225 | Linux (Linux) | Any | Multiply warnings about unfreed memory |
33738 | 2008-01-08 10:45 | 2009-02-16 11:25 | MySQL Query Browser | Not a Bug (5520 days) | S2 | 1.2.12 | Windows (VISTA Home Basic) | Any | My MySQL Browser & Administrator do not use kerning when editing SPs&Functions |
18143 | 2006-03-10 19:01 | 2014-04-01 9:16 | MySQL Server | Duplicate (6544 days) | S2 | 4.1 and others? | Any | my_aes.c : AES_ENCRYPT pads unnecessarily when strlen(source) % 16==0 | |
55124 | 2010-07-09 12:44 | 2022-09-04 20:45 | MySQL Server: Data Types | Duplicate (4965 days) | S2 | 5.1.49-debug, 5.5.6-m3-debug | Any | Any | my_decimal_precision_to_length_no_truncation(): Assertion `precision || !scale' |
86357 | 2017-05-17 14:28 | 2017-05-19 8:23 | MySQL Server: Documentation | Won't fix (2506 days) | S3 | 5.7.18 | Ubuntu | Any | my_make_scrambled_password() changed behavior, can overflow buffer |
79092 | 2015-11-03 9:52 | 2016-02-24 23:18 | MySQL Server: Security: Audit | Closed (2956 days) | S3 | 5.7.9 | Any | Any | my_message fails to abort MYSQL_AUDIT_SERVER_STARTUP_CLASS event |
74641 | 2014-10-31 1:31 | 2014-10-31 14:42 | MySQL Server: DML | Verified (3437 days) | S1 | 5.6.20, 5.6.21 | Any | Any | my_seek.c:57: my_seek: Assertion `fd != -1' failed. Table corruption on opt |
81453 | 2016-05-17 6:43 | 2018-09-25 22:04 | MySQL Server: DDL | Verified (2873 days) | S6 | 5.5.49 | Any | Any | my_tell: Assertion `fd >= 0' failed. |
31566 | 2007-10-12 14:23 | 2007-12-20 0:38 | MySQL Server | Closed (5944 days) | S1 | 5.0.46 | Linux ( ) | Any | my_write(fd, 0x0, 0, flags) fails with EFAULT on some platforms |
4095 | 2004-06-10 20:06 | 2004-06-17 9:48 | MySQL Server: MyISAM storage engine | Can't repeat (7225 days) | S1 | 4.0, 4.1, 5.0 | Any (any) | Any | MyISAM corruption happens with concurrent INSERTs |
23175 | 2006-10-11 13:28 | 2006-10-20 17:41 | MySQL Server: MyISAM storage engine | Closed (6370 days) | S1 | 5.0.27-BK, 4.1,5.0,5.1 | Linux (Linux) | Any | MYISAM crash/repair failed during repair |
50365 | 2010-01-15 14:00 | 2011-02-16 23:44 | MySQL Enterprise Monitor: Advisors/Rules | Closed (5092 days) | S3 | All | Any | Any | MyISAM Key Buffer Usage graph allocated calculation wrong |
36915 | 2008-05-23 12:38 | 2008-05-28 16:49 | MySQL Server: Documentation | Closed (5784 days) | S3 | 5.1.23 | Any | Any | MyISAM max table size |
39502 | 2008-09-17 17:21 | 2008-11-01 4:43 | MySQL Server: MyISAM storage engine | No Feedback (5627 days) | S2 | 4.1.22+4.1.20 | Linux (Centos 4.7) | Any | myisam table crash on update or replace into periodically |
14213 | 2005-10-21 15:49 | 2005-12-15 15:05 | MySQL Server | Not a Bug (6679 days) | S3 | 5.0.13 rc | Windows (Windows XP with sp2) | Any | MYISAM Table Handler |
17116 | 2006-02-04 11:54 | 2006-02-28 0:51 | MySQL Server: MyISAM storage engine | Closed (6604 days) | S3 | 5.1 | Any | myisam_ftdump doesn't work with fulltext indexes using a parser plugin | |
49347 | 2009-12-02 13:06 | 2011-02-16 23:44 | MySQL Server: FULLTEXT search | No Feedback (5200 days) | S2 | 5.1.34-community | Windows | Any | myisam_ftdump repeating rows in -c mode |
25000 | 2006-12-12 10:42 | 2007-01-30 3:34 | MySQL Server: MyISAM storage engine | Closed (6268 days) | S1 | 4.1.23 | unknown | Any | myisam.test fails on 'pb-valgrind-*' Valgrind |
1869 | 2003-11-18 5:29 | 2003-11-24 10:04 | MySQL Server: MyISAM storage engine | Closed (7431 days) | S2 | Linux (Suse/Windows XP) | Any | myisamchk fails fixing a table with blob column | |
50457 | 2010-01-19 20:37 | 2011-02-16 23:44 | MySQL Server: Documentation | Closed (5155 days) | S3 | 5.1.42 | Any | Any | myisamchk incorrectly reports a table as Packed |
29182 | 2007-06-18 19:15 | 2008-03-30 9:43 | MySQL Server: MyISAM storage engine | Closed (5843 days) | S3 | 5.1.18 | Any | Any | MyISAMCHK reports wrong character set |
43950 | 2009-03-30 6:14 | 2011-02-16 23:43 | MySQL Server: MyISAM storage engine | Closed (5432 days) | S3 | 5.0.80, 5.1.32 | Linux | Any | myisamchk shows negative value for 'Max keyfile length' |
60850 | 2011-04-13 10:13 | 2011-04-28 17:22 | MySQL Server: MyISAM storage engine | Can't repeat (4719 days) | S2 | 5.5.10 | FreeBSD (amd64) | Any | myisamchk: Error reading file '/storage/5/tmp/STVhtaM4' (Errcode: 22) |
8321 | 2005-02-04 16:47 | 2005-07-10 15:52 | MySQL Server: Command-line Clients | Closed (6837 days) | S2 | 4.0 and above | Any (any) | Any | myisampack bug in compression algorithm |
28823 | 2007-06-01 5:59 | 2007-06-01 20:05 | MySQL Server: Documentation | Closed (6146 days) | S3 | 4.0.x, 4.1.x, 5.0.x | Any | Any | myisampack does NOT support --packlength option |
22755 | 2006-09-27 18:56 | 2013-12-30 13:22 | MySQL Server | Verified (3742 days) | S4 | 5.1.11-beta-log | Linux (RHEL 4 AS U3) | Any | myisampack on partitioned tables |
72879 | 2014-06-04 15:53 | 2018-08-02 7:28 | MySQL Workbench: Modeling | Won't fix (2066 days) | S2 | Workbench 5.1 and later | Windows (Windows 8.1) | Any | MyModel.wb51.wb51.mwb is a backup file but that is counter-intuitive |
14149 | 2005-10-19 19:00 | 2005-12-15 16:13 | Connector / ODBC | Can't repeat (6679 days) | S3 | MyODBC-3.51.11-2-win | Windows (Windows 2000 SP4) | Any | MyODBC 3.51 driver and SQLTables call. Column truncation on the call |
27790 | 2007-04-12 18:32 | 2007-05-03 17:45 | Connector / ODBC | Closed (6175 days) | S2 | 3.51.14 | Windows (2000 SP4) | Any | MyODBC 3.51.14 returns wrong length for varchar binary columns |
4321 | 2004-06-29 2:57 | 2004-06-29 23:01 | Connector / ODBC | Can't repeat (7213 days) | S1 | Windows (windows 2000) | Any | MyODBC 3.51.8(windows) return '????' when using Date format | |
28343 | 2007-05-09 22:59 | 2023-02-19 20:45 | Connector / ODBC | Duplicate (4865 days) | S2 | 3.51.14 | Windows (XP sp2) | Any | MyODBC 3/ADO error after updating long text field (invalid string or buffer len) |
25902 | 2007-01-29 0:28 | 2007-06-12 10:45 | Connector / ODBC | Can't repeat (6135 days) | S1 | 3.51.12 | Windows (XP) | Any | MyODBC ADO recset with client side cursor is lost after a given # of recs read |
25846 | 2007-01-25 13:52 | 2007-03-09 11:25 | Connector / ODBC | Closed (6230 days) | S2 | 3.51.12 | Any (All OS) | Any | MyODBC does not recognize TIME (hh:mm:ss) and DATE (yy:mm:dd) |
24867 | 2006-12-07 0:26 | 2007-03-02 18:31 | Connector / ODBC | Duplicate (6237 days) | S1 | 3.51 | Windows (XP sp 2) | Any | MyODBC failure when using a table with MySQL TIME data type |
11381 | 2005-06-16 13:13 | 2007-09-03 14:21 | Connector / ODBC | Duplicate (6052 days) | S3 | 3.51.11 | Any | Any | MyODBC leaks |
9111 | 2005-03-10 23:18 | 2005-03-24 2:22 | Connector / ODBC | Closed (6945 days) | S3 | MyODBC 3.51.11 | Windows (XP) | Any | MyODBC returns wrong character field widths in Visual Foxpro |
3303 | 2004-03-26 6:39 | 2004-07-22 16:31 | Connector / ODBC | Closed (7190 days) | S1 | 3.51.06 | HP/UX (HPUX 11.11) | Any | MyODBC ver. 3.51.06 not fully-compliant with MySQL RDBMS ver. 4.0.16 |
40354 | 2008-10-27 18:39 | 2008-10-28 14:14 | Connector / ODBC | Not a Bug (5631 days) | S3 | 5.1.5 | Windows (Vista) | Any | MyODBC Version 5.1.5 Returns AsianCharacters on date_format() function |
6777 | 2004-11-23 19:03 | 2004-12-01 4:33 | MySQL Administrator | Closed (7058 days) | S2 | 1.0.14 | Windows (windows xp and fedora core 2) | Any | myqsl administrator 1.0.14 restore function fails - more information |
38498 | 2008-07-31 16:24 | 2008-08-01 8:08 | MySQL Server | Closed (5719 days) | S2 | 10.11 Distrib 5.0.51b | Windows (XP) | Any | myslqdump cannot dump tables with names that are 64 characters long |
103336 | 2021-04-15 18:22 | 2021-04-16 7:39 | MySQL Server: DDL | Duplicate (1078 days) | S3 | Any | Any | MySQL - Blackhole max index key length < InnoDB | |
4058 | 2004-06-08 14:31 | 2005-10-04 17:01 | MySQL Server: Command-line Clients | Not a Bug (6751 days) | S4 | any | Any (any) | Any | mysql --csv |
29708 | 2007-07-11 4:42 | 2007-07-19 18:13 | Connector / NET | Not a Bug (6098 days) | S2 | mysql-connector-net-5.0.5/5.0.7/5.1.2 | Windows (XP professional 2002 SP 2) | Any | Mysql .NET Connector installation problems |
5090 | 2004-08-18 12:40 | 2004-08-18 20:46 | MySQL Server | Can't repeat (7163 days) | S1 | 4.1.3b | Windows (Windows XP SP1) | Any | MySql (mysqld-nt.exe) service crashes on a simple LEFT function |
28652 | 2007-05-24 12:37 | 2007-06-18 19:26 | MySQL Server | Closed (6129 days) | S2 | 5.0.32, 5.0.33, 5.0.44-bk | Any | Any | MySQL (with-debug=full) asserts when alter table operations |
28654 | 2007-05-24 12:41 | 2007-05-24 12:44 | MySQL Server | Duplicate (6154 days) | S2 | 5.0.32, 5.0.33 | Any | Any | MySQL (with-debug=full) asserts when alter table operations |
28655 | 2007-05-24 12:47 | 2007-05-24 12:48 | MySQL Server | Closed (6154 days) | S2 | 5.0.32, 5.0.33, bk | Any | Any | MySQL (with-debug=full) asserts when alter table operations |
4985 | 2004-08-11 0:09 | 2004-08-25 18:56 | MySQL Server | Won't fix (7156 days) | S4 | 4.0 | Any | MySQL 4.0 doesn't work with grant tables from MySQL 5.0 | |
5096 | 2004-08-18 17:20 | 2004-08-25 11:48 | MySQL Server: Replication | Closed (7156 days) | S3 | mysql-4.0.20-standard (Official MySQL-st | Linux (Linux 2.4.25) | Any | MySQL 4.0.20 Relay log rotation problem (with workaround) |
4580 | 2004-07-17 11:32 | 2004-10-21 23:09 | MySQL Server: Installing | No Feedback (7099 days) | S2 | 4.1.3 | Linux (Linux 2.6.7) | Any | MySQL 4.1 crashes badly after having upgraded from 4.0. |
13351 | 2005-09-20 13:51 | 2005-09-20 14:18 | MySQL Server | Can't repeat (6765 days) | S2 | 4.1.11 | Linux (Linux (Debian Sarge)) | Any | Mysql 4.1 crashes when we're using union+format function |
22854 | 2006-09-30 2:10 | 2006-09-30 12:30 | MySQL Server | Closed (6390 days) | S3 | 4.1.21 | Linux (Linux) | Any | MySQL 4.1.21 does not recognize several date_format specifiers |
38737 | 2008-08-12 3:52 | 2008-08-12 6:22 | MySQL Server: Documentation | Not a Bug (5708 days) | S3 | 5.0 | Any | Any | MySQL 5.0 Reference Manual Doesn't specify BLOB capacities |
12729 | 2005-08-22 18:19 | 2005-08-23 13:19 | MySQL Server | Can't repeat (6793 days) | S2 | mysql-standard-5.0.11-beta-linux-i686 | Linux (linux) | Any | Mysql 5.0.11 Crash with incorrect date format. |
27513 | 2007-03-29 8:47 | 2007-06-27 13:17 | MySQL Server: Errors | Closed (6120 days) | S1 | 5.0.26, 5.0.34, 5.0.40-debug | Linux (Gentoo Linux) | Any | mysql 5.0.x + NULL pointer DoS |
49985 | 2009-12-30 4:52 | 2018-09-25 21:51 | MySQL Server: Tests | Not a Bug (4666 days) | S7 | 5.1 | Linux (Debian 5.0 64 bit) | Any | MySQL 5.1 Compile on Debian 5.0 64 bit fails make test |
41740 | 2008-12-25 8:51 | 2011-08-16 1:21 | MySQL Server: Optimizer | Closed (4609 days) | S5 | 5.1.25,5.1.30 | Any | Any | MySQL 5.1 optimizer produces inefficient plan for complex queries |
67790 | 2012-12-02 18:24 | 2019-08-12 14:34 | MySQL Server: Compiling | Won't fix (4035 days) | S3 | 5.5 revno 3953, 5.6 revno 4458, 5.5.28, 5.6.8 | Linux (Ubuntu 12.10 x86_64) | Any | MySQL 5.5 and 5.6 fails to build if GCC Link Time Optimization (-flto) is used |
61979 | 2011-07-26 5:41 | 2016-10-04 7:10 | MySQL Server: General | Verified (4630 days) | S3 | 5.5.16 | Any | Any | MySQL 5.5 and PVS-Studio |
70005 | 2013-08-12 22:39 | 2013-08-20 13:12 | MySQL Server: Documentation | Closed (3874 days) | S3 | 5.5.33 | Solaris (Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC) | Any | MySQL 5.5.33 issue with section 14.4.4.3. Identifying the File Format in Use |
70194 | 2013-08-30 8:10 | 2014-01-01 10:35 | MySQL Server: Replication | Duplicate (3740 days) | S1 | 5.6.13 | Windows (Windows Server 2012 Standard x64) | Any | MySQL 5.6 crashes on 'START SLAVE;' command |
72761 | 2014-05-27 10:00 | 2014-05-27 17:03 | MySQL Server: DML | Verified (3594 days) | S3 | 5.6.17 | Any | Any | MySQL 5.6 FROM_UNIXTIME function returns different result than 5.5 |
70185 | 2013-08-29 18:20 | 2014-01-23 0:36 | MySQL Server: InnoDB storage engine | Can't repeat (3718 days) | S1 | 5.6.1x | Linux (3.4.43-43.43.amzn1.x86_64) | Any | Mysql 5.6.13 - InnoDB: Unable to allocate memory of size 18446744073709546280 |
67880 | 2012-12-12 1:20 | 2020-06-09 6:36 | MySQL Server: Installing | Verified (4125 days) | S1 | 5.6.9 | Windows | Any | mysql 5.6.9 on windows does not start if my.ini file is in utf8 format |
92728 | 2018-10-10 8:39 | 2019-01-30 13:41 | MySQL Server: Partitions | Can't repeat (1907 days) | S3 | 5.7.20 | Windows (WIndows Server 2016) | x86 (On a VM) | MySQL 5.7 issue with 16TB disk |
82515 | 2016-08-09 15:01 | 2016-09-28 15:23 | MySQL Server: Compiling | Closed (2741 days) | S2 | 5.7.13, 5.7.14, 5.7.15 | Fedora (rawhide) | Any | MySQL 5.7.1{3,4} does not compile ob gcc 6.1.1 |
88703 | 2017-11-29 21:44 | 2017-12-15 6:47 | MySQL Server: Compiling | Duplicate (2296 days) | S3 | 5.7.20 | Any | Any | MySQL 5.7.20 contains a potential buffer overflow |
104425 | 2021-07-27 10:01 | 2021-08-11 13:45 | MySQL for Windows: Installer | Can't repeat (961 days) | S2 | 5.7.35 | Windows | Any (Not Available) | MySQL 5.7.35 - Windows MSI Installer package is not available |
75939 | 2015-02-17 21:24 | 2015-09-05 1:00 | MySQL Server: Group Replication | No Feedback (3129 days) | S1 | 5.7.5-labs-group-replication | Linux (ubuntu 14.04) | Any | mysql 5.7.5 group replication failed |
33017 | 2007-12-05 20:49 | 2007-12-06 7:53 | MySQL Server: Documentation | Closed (5958 days) | S3 | 6.0 | Any | Any | MySQL 6.0 Reference Manual - entire thing is blue underlined |
112539 | 2023-09-27 12:49 | 2023-10-04 11:10 | MySQL Server | Not a Bug (177 days) | S3 | 8.1.0 | Any | Any | MySQL 8 can not restore dump |
99791 | 2020-06-06 7:29 | 2023-06-09 12:42 | MySQL Server: Data Dictionary | Closed (1289 days) | S3 | 8.0 | Any | Any | MySQL 8 orphaned table due to unchecked non-existent row format check. |
91483 | 2018-06-29 2:25 | 2018-07-02 4:43 | Shell Upgrade Checker | Duplicate (2097 days) | S3 | 8.0.11 | Any | Any | MySQL 8 upgrade checker warns about valid display widths and zerofill |
90634 | 2018-04-25 21:44 | 2018-08-15 0:36 | Shell General / Core Client | Closed (2118 days) | S3 | 8.0.11 | Any | Any | MySQL 8 upgrade checker: remove check for zerofill columns |
108621 | 2022-09-27 8:38 | 2022-10-06 16:25 | MySQL Server: Documentation | Closed (540 days) | S3 | current | Any | Any | mysql 8.0 Chapter (8.2.1.4 Hash Join Optimization) Document content error |
82874 | 2016-09-06 18:20 | 2016-11-29 2:05 | MySQL Server: Errors | Closed (2744 days) | S3 | 8.0.0 | Any | Any | MySQL 8.0 Upgrade - messages in mysqld log without datetime [Note] info |
109361 | 2022-12-13 12:06 | 2023-01-11 1:03 | MySQL Server: Optimizer | Closed (443 days) | S2 | 8.0.29 | Any | Any | MySQL 8.0.29+ is slower than MySQL 8.0.28 with queries using JOINS |
113950 | 2024-02-10 23:25 | 2024-02-19 12:32 | MySQL Server: InnoDB storage engine | Can't repeat (42 days) | S3 | 8.0.30 | Linux | x86 | MySQL 8.0.30 is stuck due to the processing of a large transaction |
67263 | 2012-10-16 12:10 | 2012-11-17 1:00 | MySQL Server: Errors | No Feedback (4151 days) | S2 | 5.5.9 | Linux (Redhat 5.3 x64) | Any | mysql aborted suddenly and restart faild |
7694 | 2005-01-05 21:50 | 2005-05-30 9:43 | MySQL Administrator | Closed (6878 days) | S3 | 1.0.18 | Windows (Windows2000 Server) | Any | MySQL Admin showing incorrect data |
6693 | 2004-11-18 5:23 | 2004-12-24 11:59 | MySQL Administrator | No Feedback (7035 days) | S3 | 1.0.14 | Windows (XP) | Any | mysql admin shows 0 byte index length + data length |
27106 | 2007-03-13 22:22 | 2007-03-14 7:38 | MySQL Administrator | Can't repeat (6225 days) | S1 | 5 | Windows (Windows XP and Vista) | Any | MYSQL Admin truncates my username to four characters and will not login |
24454 | 2006-11-21 8:32 | 2006-12-21 17:40 | MySQL Administrator | No Feedback (6308 days) | S3 | 1.2.4rc (bundled with MySQL 4.1.12) | Linux (RHEL 4.0 Upd2 X86(EM64T/AMD64)) | Any | MySQL Administration tool does not prevent incorrect SQL scripts to be created |
8823 | 2005-02-26 21:56 | 2005-03-04 20:39 | MySQL Administrator | Closed (6965 days) | S3 | 1.05-alpha | MacOS (Mac OS X 10.3.8) | Any | MySQL Administrator - crash 8 sec after connect using return to accept pwd |
109236 | 2022-11-29 13:28 | 2022-12-04 16:47 | MySQL Server | Not a Bug (481 days) | S3 | 8.0.30 | Linux ( 18.04.6 LTS) | x86 | Mysql AES encrypt from 8.0.25 to 8.0.30 |
686 | 2003-06-19 13:58 | 2003-06-19 14:10 | MySQL Server | Can't repeat (7589 days) | S2 | 4.1.0-alpha | Linux (Red Hat 8.0 / Red Hat 7.3) | Any | MySQL allows a no name fieldname, but will not import it properly |
85199 | 2017-02-27 9:51 | 2018-06-08 11:50 | MySQL Server: User-defined functions ( UDF ) | Can't repeat (2121 days) | S3 | 10+ | Any | Any | mysql args lengths incorrect |
73731 | 2014-08-26 20:29 | 2015-03-11 1:00 | MySQL Server | No Feedback (3307 days) | S1 | 5.6.20 | Linux | Any | Mysql bin log issue |
104838 | 2021-09-06 9:33 | 2021-09-06 9:39 | MySQL Server: Replication | Duplicate (935 days) | S3 | 8.21.4 | Any | Any | mysql binlog can't deserialize |
89869 | 2018-03-01 13:45 | 2018-03-02 14:24 | MySQL Server | Not a Bug (2219 days) | S2 | 5.5 | Debian (Debian 8) | Any | MySQL Bug |
95076 | 2019-04-22 17:42 | 2019-05-24 1:00 | MySQL Server: Compiling | No Feedback (1772 days) | S2 | 8.0.15 | Fedora | Any | MySQL build fails with latest icu |
65152 | 2012-04-30 5:39 | 2012-06-04 10:21 | MySQL Server: Replication | Closed (4316 days) | S2 | 5.6.5m8 | Linux (RHEL 6.2 64bits) | Any | MySQL can't start if relay logs are removed and skip_slave_start = 0 |
26851 | 2007-03-05 22:16 | 2007-06-07 16:27 | MySQL Server: Command-line Clients | Closed (6140 days) | S2 | 5.0.38-BK, 5.0.32, 5.0.24a | Linux (Linux) | Any | Mysql Client --pager Buffer Overflow |
72053 | 2014-03-17 7:09 | 2014-03-17 18:53 | MySQL Server: MyISAM storage engine | Verified (3665 days) | S1 | 5.5,5.6,5.7 | Any | Any | mysql client command coredump when disk space is full! |
72054 | 2014-03-17 7:36 | 2014-03-17 12:58 | MySQL Server | Duplicate (3665 days) | S1 | 5.5,5.6,5.7 | Any | Any | mysql client command coredump when disk space is full! |
7616 | 2005-01-02 11:50 | 2005-01-11 15:20 | MySQL Server: Command-line Clients | Not a Bug (7017 days) | S3 | 4.1.8 | Linux (Linux/Fedora Core 3) | Any | mysql client display problem with UTF8 |
48980 | 2009-11-23 10:00 | 2014-11-05 15:25 | MySQL Server: Charsets | Verified (5239 days) | S3 | 5.0.84, 5.0, 5.1 bzr | Any | Any | mysql client field length for utf8 is twice number of letters (is |
33812 | 2008-01-10 23:16 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Closed (5539 days) | S2 | 5.0.52, 5.0.54, 5.1.23-rc | Any | Any | mysql client incorrectly parsing DELIMITER |
36322 | 2008-04-24 15:58 | 2008-04-24 17:29 | MySQL Server: Command-line Clients | Duplicate (5818 days) | S3 | 5.0.54, 5.1.23-rc | Any | Any | mysql client segfaults with empty input in non-interactive mode |
2596 | 2004-01-31 11:17 | 2005-04-28 2:29 | MySQL Server | Closed (6910 days) | S3 | 5.0 alpha | Solaris (Solaris 9 sparc 64) | Any | MySQL Client Segmentation Fault on Solaris 9 |
32271 | 2007-11-12 8:55 | 2014-03-28 6:54 | MySQL Server: Command-line Clients | Closed (3654 days) | S3 | 5.0.38, 5.0.50 | Linux (Ubuntu) | Any | mysql client unicode output incorrectly padded |
46323 | 2009-07-21 12:50 | 2011-02-16 23:44 | MySQL Server: Command-line Clients | Verified (5365 days) | S3 | any | Any | Any | mysql client, prettier HTML output |
44127 | 2009-04-07 8:13 | 2011-02-16 23:43 | MySQL Server: Command-line Clients | Verified (5470 days) | S3 | 4.1, 5.0, 5,1, 6.0 bzr | Any | Any | mysql client: Unclear description of batch mode |
47573 | 2009-09-23 23:18 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5299 days) | S2 | mysql-5.1-telco-6.2 | Any | Any | MySQL Cluster : Internal blob read buffer not always freed correctly |
31414 | 2007-10-04 23:12 | 2007-10-05 12:12 | MySQL Cluster: Cluster (NDB) storage engine | Not a Bug (6020 days) | S3 | 5.1.22 rc1 | Linux (Debian4) | Any | MySQL Cluster 5.1 Row size too large |
16145 | 2006-01-03 3:53 | 2006-04-07 10:12 | MySQL Server: Documentation | Closed (6566 days) | S3 | 5.0 | Any | MySQL Cluster Clusterlog definitions | |
35393 | 2008-03-18 12:45 | 2008-07-02 18:53 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5749 days) | S5 | 5.1 | Any | Any | MySQL Cluster condition pushdown sends full length for VAR* types |
35772 | 2008-04-02 14:27 | 2011-02-16 23:43 | MySQL Cluster: Cluster (NDB) storage engine | Closed (5579 days) | S1 | teleco version mysql-5.1.23 ndb-6.3.8 | Linux (Linux 2.6.18-4-686 #1 SMP i686 GNU/Linux) | Any | MySql Cluster Crashes and fails to recover |
112990 | 2023-11-07 13:21 | 2023-11-09 14:59 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (141 days) | S2 | 5.7.43 | Any | Any | MySQL cluster hang forever |
58280 | 2010-11-18 9:48 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Closed (4872 days) | S2 | 5.1.51-ndb-7.1.9 | Any | Any | MySQL Cluster may return duplicated rows when WHERE-predicate contains 'OR' |
66495 | 2012-08-22 9:31 | 2016-07-22 12:53 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (2807 days) | S2 | 7.2.6 | Linux (SLES12 (using SLES11 package)) | Any | MySQL Cluster node failure with no activity |
11776 | 2005-07-06 14:48 | 2013-10-06 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Duplicate (6825 days) | S1 | 4.1.12 | Linux (Linux (AMD64)) | Any | mysql cluster unable to restart after clean shutdown |
75802 | 2015-02-05 17:33 | 2022-09-04 20:45 | Connector / J | Duplicate (3332 days) | S3 | 5.1.34 | Any | Any | mysql cmdline behave different then jdbc app with regards to InnoDB max key |
104638 | 2021-08-17 5:08 | 2021-09-01 22:46 | MySQL for Windows: Installer | Closed (940 days) | S3 | 8.0.26.0 | Windows (10 Pro) | x86 | MySQL Community Installer (8.0.26.0) fails to install MySQL Server 5.6.51 |
42500 | 2009-01-31 14:42 | 2009-02-11 15:14 | Connector / NET | Not a Bug (5525 days) | S2 | 5.2.5.0 | Windows (XP Pro Visual Studio 2008) | Any | Mysql Connector .net 5.2 Character Set problem |
72602 | 2014-05-09 22:35 | 2014-07-11 14:27 | Connector / Python | Closed (3564 days) | S3 | 1.1.6 | Linux (Ubuntu) | Any | MySQL connector / python (v1.1.6) fails when querying for many columns and using |
36198 | 2008-04-18 9:01 | 2008-04-22 13:08 | Connector / ODBC | Can't repeat (5820 days) | S1 | 3.1 AND 5.1 | Any | Any | MYSQL Connector 3.1 AND 5.1 : Strings with a length of 255 chars = ODBC Error |
94235 | 2019-02-07 9:50 | 2021-11-17 17:31 | Connector / ODBC | Closed (863 days) | S5 | 8 | Linux | Any | MySQL Connector 8 uses depreciated 'COM_FIELD_LIST’ |
102820 | 2021-03-04 20:22 | 2021-04-22 10:36 | Connector / ODBC | Analyzing (1072 days) | S1 | 8.0.19-8.0.23 | Windows (10) | Other (x64) | MySQL Connector/ODBC 8.0.19 and later versions error - client program crashes |
1787 | 2003-11-09 19:22 | 2004-01-29 13:35 | MySQL Server: InnoDB storage engine | Not a Bug (7365 days) | S1 | mysql-4.0.12 | FreeBSD (FreeBSD-4.8 PRE-RELEASE) | Any | mysql cores |
70115 | 2013-08-22 3:19 | 2013-10-01 1:00 | MySQL Server: Pluggable Authentication | No Feedback (3833 days) | S1 | 5.6.12 | Linux (OpenSUSE 12.3) | Any | MySQL corrupts sha256 password RSA keys on crash |
64050 | 2012-01-17 13:39 | 2012-03-04 8:05 | MySQL Server | Closed (4408 days) | S1 | 5.5.20 | Windows (2008R2 x64) | Any | MySql Crash |
72237 | 2014-04-04 13:08 | 2014-05-08 1:00 | MySQL Server | No Feedback (3614 days) | S1 | 5.5.35-0ubuntu0.12.04.2 | Linux (ubuntu0.12.04.2) | Any | MySQL Crash |
36900 | 2008-05-22 23:52 | 2008-06-23 4:25 | MySQL Server: InnoDB storage engine | No Feedback (5758 days) | S2 | 4.1.20 | Linux (RHEL 4) | Any | Mysql Crash |
48192 | 2009-10-20 18:05 | 2013-04-14 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5004 days) | S1 | 5.0.86-enterprise-nt-log | Windows (XP Pro and 2003 Server) | Any | MySQL Crash (InnoDB: We intentionally generate a memory trap.) |
33283 | 2007-12-17 8:38 | 2012-04-30 12:55 | MySQL Server: InnoDB storage engine | Not a Bug (4351 days) | S1 | 5.0.27/5.0.45 | Linux (RedHat AS4U4/RedHat AS4U5) | Any | mysql crash unregularly after upgrade table strucat and stored procedure |
63498 | 2011-11-30 5:51 | 2012-01-13 1:00 | MySQL Server | No Feedback (4460 days) | S1 | 5.1.13 | Linux | Any | mysql crashed - mysqld got signal 6 - |
69291 | 2013-05-21 4:08 | 2013-07-11 1:00 | MySQL Server: General | No Feedback (3915 days) | S1 | 5.6.11 | Linux (centos 6.2) | Any | mysql crashed ,restart mysql cant recovery |
109816 | 2023-01-27 7:15 | 2023-01-27 10:32 | MySQL Server | Unsupported (427 days) | S1 | 5.6.19-log | Windows | Any | MySQL crashed after Out of memory (Needed 1048528 bytes) |
76441 | 2015-03-23 2:10 | 2015-07-24 2:40 | MySQL Server | Duplicate (3171 days) | S3 | 5.6.16 | Any | Any | mysql crashed in Item_func::fix_fields |
50403 | 2010-01-18 6:10 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (4967 days) | S1 | 5.1.41 | Linux | Any | MySQL crashed not able to recover (InnoDB) |
100193 | 2020-07-12 15:51 | 2020-08-13 1:00 | MySQL Server | No Feedback (1325 days) | S1 | 8.0.14 | Red Hat (7.5) | x86 | Mysql Crashed Unexpectedly after complaining out of memory |
33227 | 2007-12-13 20:50 | 2008-01-16 3:40 | MySQL Server: FULLTEXT search | No Feedback (5917 days) | S1 | 5.1.22 Beta | Windows (2003 Server) | Any | MySQL crashed when creating FullText Index with large amount of data |
19420 | 2006-04-28 10:04 | 2006-05-15 15:25 | MySQL Server: InnoDB storage engine | Can't repeat (6528 days) | S2 | mysql Ver 14.7 Distrib 4.1.11, for redh | Linux (Fedora 4 Core) | Any | mysql crashed with "Assertion failure in thread" |
67655 | 2012-11-21 9:16 | 2012-12-23 1:00 | MySQL Server | No Feedback (4115 days) | S1 | 5.5.25a | Linux (Red Hat Enterprise Linux Server release 5.7 (Tikanga)) | Any | MySQL crashed: InnoDB Assertion failure |
69264 | 2013-05-17 11:16 | 2013-06-20 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3936 days) | S1 | 5.5.11 | Linux | Any | Mysql crashes |
65156 | 2012-04-30 16:24 | 2013-12-28 1:00 | MySQL Server: Information schema | No Feedback (3745 days) | S1 | 5.1.61-0+squeeze1-log | Linux (Debian Squeeze) | Any | MySql crashes accessing information_schema.PROCESSLIST |
66933 | 2012-09-23 13:47 | 2013-01-30 14:26 | MySQL Server: InnoDB Plugin storage engine | Not a Bug (4076 days) | S1 | 5.5.27-1 | Linux (Debian 6.0) | Any | Mysql Crashes after InnoDB Assertion failure |
1794 | 2003-11-10 9:31 | 2003-12-18 20:27 | MySQL Server | No Feedback (7407 days) | S2 | Mysql Max 4.0.16 Linux RPM | Linux (Red Hat Linux 9 kernel-smp-2.4.2) | Any | MySQL crashes after mysqldump is run on all tables or BDB problem |
20915 | 2006-07-08 13:31 | 2006-12-29 0:27 | MySQL Server | No Feedback (6300 days) | S3 | 5.0.26, 5.0.24, 5.0.22 | Linux (Gentoo Linux) | Any | MySQL crashes during select queries on specific table |
57945 | 2010-11-03 7:59 | 2011-02-16 23:44 | MySQL Server | No Feedback (4835 days) | S1 | 5.1.37 & 5.1.47 | Linux (RED HAT ) | Any | MySQL crashes frequently without any regularity. |
88121 | 2017-10-17 12:38 | 2017-10-17 13:12 | MySQL Server: InnoDB storage engine | Can't repeat (2355 days) | S2 | 5.6.37 | Linux | Any | MySQL crashes in btr_pcur_restore_position_func at btr0pcur.cc |
88095 | 2017-10-14 8:35 | 2017-11-16 1:00 | MySQL Server | No Feedback (2326 days) | S2 | 5.6.37 | Linux | Any | MySQL crashes in handler::ha_reset |
88096 | 2017-10-14 8:38 | 2017-11-15 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2327 days) | S2 | 5.6.37 | Linux | Any | MySQL crashes in os_aio_wait_until_no_pending_writes() |
1434 | 2003-09-29 13:24 | 2003-10-06 10:54 | MySQL Server | Closed (7480 days) | S1 | Any | MySQL crashes on CREATE TABLE IF NOT EXISTS ... SELECT ... | ||
70014 | 2013-08-13 13:34 | 2013-11-19 16:31 | MySQL Server: Optimizer | Closed (3783 days) | S2 | 5.6.12-debug, 5.6.13-debug , 5.7.2-m12-enterprise-commercial-advanced-debug | Linux (Fedora 18) | Any | MySQL crashes on explain with JSON formatting (debug builds) |
84690 | 2017-01-27 8:05 | 2018-05-03 1:00 | MySQL Server | No Feedback (2158 days) | S1 | 5.7.17 | Windows (Nano Server 2016 (64bit)) | Any | MySQL crashes on startup with existing ssl-certificates on Nano Server |
24587 | 2006-11-25 16:08 | 2006-12-28 16:39 | MySQL Server | Closed (6301 days) | S2 | 5.0.22 | Linux (Fedora Core 6) | Any | mysql crashes sometimes on SELECT |
70802 | 2013-11-02 15:04 | 2015-08-19 8:07 | MySQL Server: InnoDB storage engine | No Feedback (3758 days) | S2 | 5.5.34-log MySQL Community Server (GPL) | Linux (RHEL 6.4) | Any | MySQL Crashes when Trying to Start Slave |
107968 | 2022-07-26 2:36 | 2022-07-26 14:24 | MySQL Server | Can't repeat (612 days) | S3 | Debian | x86 | MySQL crashes with InnoDB errors | |
53071 | 2010-04-22 16:34 | 2011-02-16 23:44 | MySQL Server | No Feedback (5006 days) | S1 | > 5.0.51a(5.0.90, 5.1.45) | Linux (CentOS 5, Ubuntu 9.10) | Any | MySQL crashes with various errors when executing CREATE TABLE ... AS SELECT |
21009 | 2006-07-12 17:38 | 2006-07-17 18:12 | MySQL Server | Can't repeat (6465 days) | S1 | 5.0.22 | FreeBSD (FreeBSD) | Any | mysql crashing on signal 11 |
81609 | 2016-05-26 10:42 | 2016-06-27 1:00 | MySQL Server: Errors | No Feedback (2833 days) | S1 | 5.7.12 | Ubuntu (14.04.3) | Any | MySQL Crashing while executing Procedure |
72588 | 2014-05-09 3:41 | 2014-06-10 1:00 | MySQL Server: Optimizer | No Feedback (3581 days) | S3 | 5.5.37 | Any | Any | MySQL creates large temporary tables with UNION ALL and strings |
68985 | 2013-04-17 16:07 | 2013-04-20 5:50 | MySQL Server: General | Can't repeat (3996 days) | S2 | 5.0.45 | Linux (Debian 6.0.6) | Any | MySQL database drop insanely slow |
73154 | 2014-07-01 1:44 | 2014-07-08 4:09 | MySQL Server: Command-line Clients | Verified (3552 days) | S3 | all, 5.5, 5.6, 5.7 | Any | Any | MySQL Doc doesn't specify "mysql -e" to disable --force and history file |
63685 | 2011-12-08 21:38 | 2017-01-05 14:54 | MySQL Server: Options | Verified (4494 days) | S3 | 5.5.19 | Any (Mac OS X, Vista 32-bit Home Premium) | Any | MySQL does not recognize timezone offset UTC +14:00 |
29900 | 2007-07-19 14:39 | 2013-03-03 20:45 | MySQL Server: Information schema | Verified (5169 days) | S3 | 5.1.21-23 | Any | Any | MySQL does not return an error to the client if INFORMAT SCHEMA fill table fails |
43099 | 2009-02-23 7:30 | 2009-02-23 7:51 | MySQL Server: General | Not a Bug (5513 days) | S3 | All | Any | Any | MySQL does not sort datetime formatted in 12 hour format correctly |
27906 | 2007-04-17 23:27 | 2017-10-20 15:16 | MySQL Server: Data Types | Verified (6191 days) | S4 | 5.0 | Any | Any | MySQL doesn't accept ISO8601 date |
72259 | 2014-04-07 6:42 | 2016-11-21 6:38 | MySQL Server: Errors | Verified (3643 days) | S1 | 5.6.16 | Linux (Red Hat 4 Tikanga) | Any | MySQL doesn't show informative error message for read-only filesystem in Linux |
49154 | 2009-11-27 2:48 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Duplicate (5236 days) | S1 | 5.4.3-0 | Linux (CentOS 5.4) | Any | mysql doesn't start normaly after altering innodb table to be compressed |
49155 | 2009-11-27 3:30 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | No Feedback (5169 days) | S1 | 5.4.3-0 | Linux (CentOS 4.8) | Any | mysql doesn't start normaly after altering innodb table to be compressed |
4778 | 2004-07-27 23:38 | 2012-05-18 20:19 | MySQL Server: General | Verified (6960 days) | S4 | 4.0.18 | Any | Any | mysql doesn't try to setrlimit to maximum data size |
34041 | 2008-01-24 19:08 | 2008-01-24 20:14 | MySQL Server | Not a Bug (5909 days) | S5 | 4.1.22 | Linux (2.6.23 gentoo) | Any | MySQL doesn't use col_name(length) indexes to resolve the ORDER BY |
91994 | 2018-08-13 13:56 | 2020-03-04 14:09 | MySQL Server: Security: Audit | Verified (1486 days) | S4 | 5.7.23 | Red Hat (6/7) | Any | MySQL Enterprise Audit JSON log line separator |
83042 | 2016-09-19 13:58 | 2016-09-20 11:57 | MySQL for Windows: MySQL for Excel | Duplicate (2747 days) | S2 | 1.3.6 | Windows (Win10 Pro) | Any | MySQL Error 1064 when appending values formatted as hh:mm:ss |
6604 | 2004-11-13 12:28 | 2004-11-14 18:54 | MySQL Server: MyISAM storage engine | Not a Bug (7075 days) | S2 | 4.1.7 | Linux (Linux (Fedora Core 2)) | Any | mysql Error: 1071 (Specified key was too long; max key length is 1000 bytes) |
74492 | 2014-10-22 5:04 | 2014-10-27 14:48 | MySQL Fabric | Duplicate (3441 days) | S2 | 1.5.2 | Linux (Centos 6.3) | Any | MySQL fabric setup problem |
72606 | 2014-05-10 12:39 | 2023-02-12 20:45 | MySQL Fabric | Duplicate (3363 days) | S3 | 1.4.0 | Any | Any | MYSQL FABRIC: FAILOVER SCENARIO FAILED FOR A GROUP |
3594 | 2004-04-28 21:42 | 2004-05-10 12:45 | MySQL Server | Closed (7263 days) | S2 | 4.0.18 | Linux (Debian Linux) | Any | Mysql fails to drop database if one of the table is named 'pricing' |
71271 | 2014-01-02 11:51 | 2019-09-20 3:53 | MySQL Server: Security: Privileges | Won't fix (1725 days) | S3 | 5.5.30, 5.6.15, 5.7.20, 8.0.3 | Any | Any | MySQL fails to load PKCS#8 private key with YaSSL |
80407 | 2016-02-17 12:32 | 2016-04-15 15:46 | MySQL for Windows: MySQL for Excel | Not a Bug (2905 days) | S3 | 1.3.6 | Windows (Windows 7 Professional -64-bit OS) | Any | MySQL for Excel - table was not created due to errors on rows insertion |
99698 | 2020-05-26 19:30 | 2020-09-21 18:12 | MySQL for Windows: MySQL for Excel | Won't fix (1400 days) | S3 | 1.3.8 | Windows (Windows 10 Pro for Workstation 64bit) | Any | MySQL for Excel plugin shows me error |
72434 | 2014-04-23 22:57 | 2014-06-30 18:39 | MySQL for Windows: MySQL for Excel | Closed (3560 days) | S2 | 1.2.1 | Windows | Any | Mysql for excel will not import table and gives vague error message |
103894 | 2021-06-02 15:05 | 2022-09-06 10:07 | MySQL Visual Studio Integration | Can't repeat (1001 days) | S3 | 1.2.9 | Windows (10.0.19042 Build 19042) | x86 (Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s)) | MySQL for Visual Studio fails to load on Microsoft Visual Studio |
87794 | 2017-09-18 15:10 | 2017-09-19 15:33 | MySQL Server: DML | Not a Bug (2383 days) | S3 | 5.7.17 | Any | Any | MySQL gives invalid value for float column type. |
76584 | 2015-04-03 4:15 | 2015-04-25 10:13 | MySQL Server | Duplicate (3261 days) | S1 | 5.5.30 | Linux (CentOS6.2) | Any | Mysql got crash unexpectedly |
2234 | 2003-12-29 12:07 | 2004-01-11 14:28 | MySQL Server | Closed (7383 days) | S1 | 4.0.16/4.0.17 | Linux (Redhat AS3) | Any | MySQL hang on adding index to 2 tables in the database |
569 | 2003-06-02 10:21 | 2003-06-14 3:39 | MySQL Server | Duplicate (7594 days) | S1 | 4.0.13 | Linux (RedHat Linux 6.2) | Any | MySQL has delete-link errors |
67799 | 2012-12-04 2:50 | 2013-01-29 1:00 | MySQL Workbench | No Feedback (4078 days) | S2 | 5.2.44 | Windows (Microsoft Windows Vista Home Premium Edition Service Pack 2 (build 6002), 32-bit) | Any | MYSQL has encountered a problem and will now close |
71972 | 2014-03-07 13:03 | 2014-08-17 12:30 | MySQL Server: Command-line Clients | Verified (3512 days) | S3 | 5.6.16 | Any | Any | mysql history length limited to 4K |
81207 | 2016-04-27 7:32 | 2016-04-27 9:19 | MySQL Server: InnoDB storage engine | Duplicate (2893 days) | S1 | 5.6.27 | CentOS (6.5) | Any | mysql Innodb crashes from 5.5.38 to 5.6.27 |
45443 | 2009-06-11 8:55 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5370 days) | S3 | 5.0.67 | Linux (RedHat AS5 X64) | Any | mysql innodb error |
82592 | 2016-08-16 3:55 | 2016-09-02 13:11 | MySQL Server: InnoDB storage engine | Not a Bug (2775 days) | S3 | 5.7.14 | Any | Any | MySQL InnoDB update locking |
73924 | 2014-09-16 5:56 | 2014-09-16 7:42 | MySQL Server: FULLTEXT search | Duplicate (3482 days) | S2 | 5.6.15, 5.6.17 | Windows | Any | MySql innodb_ft_max_token_size is not changing |
34714 | 2008-02-21 4:05 | 2008-03-27 11:42 | MySQL Server: General | Closed (5846 days) | S3 | 5.0.22 | Windows (MS 2003 Server, IIS, PHP 5) | Any | mysql insert stops without errors |
71756 | 2014-02-18 8:51 | 2014-02-18 12:14 | MySQL Server | Not a Bug (3692 days) | S1 | 5.6.16 ENT | Linux (Ubuntu 12.04) | Any | MySQL installation issue |
74610 | 2014-10-29 1:17 | 2015-06-02 17:11 | MySQL for Windows: Installer | Closed (3223 days) | S1 | mysql-installer-community-5.6.21.1 | Windows ( Windows 7 64 bit) | Any | MySQL Installer: Failure to Install MySQL Software |
94689 | 2019-03-18 11:32 | 2020-10-05 12:25 | MySQL Server | Closed (1817 days) | S2 | 5.7.25 | Debian (8.11) | Any | MySQL Instance restarts |
67989 | 2012-12-29 17:41 | 2017-07-11 11:06 | MySQL Server: Documentation | Won't fix (2453 days) | S3 | Any | Any | MySQL Internals documentation missing 5.6 binlog protocol parts | |
79826 | 2016-01-03 8:41 | 2018-09-28 12:08 | MySQL Server: User-defined functions ( UDF ) | Can't repeat (2009 days) | S3 | 5.6.27 | Ubuntu | Any | MySql invalid argument reading |
69239 | 2013-05-15 8:43 | 2013-05-15 8:57 | MySQL Server | Duplicate (3971 days) | S1 | Any | Any | Mysql is gone away | |
39482 | 2008-09-16 15:23 | 2008-09-16 17:00 | MySQL Server: Documentation | Closed (5673 days) | S3 | all | Any | Any | MySQL isn't a storage engine |
80126 | 2016-01-23 6:41 | 2016-07-20 16:05 | MySQL Server: Japanese Documentation | Closed (2809 days) | S3 | 5.6 | Any | Any | MySQL Japanese Documentation does not have downloadable PDF format. |
19094 | 2006-04-14 3:21 | 2006-04-24 15:22 | MySQL Server | Can't repeat (6549 days) | S1 | 4.1.18 | Linux (RH 9.0) | Any | MySQL keeping Crash and Restart, log file show a pointer error |
24788 | 2006-12-04 9:08 | 2007-02-22 18:09 | MySQL Server: Documentation | Closed (6245 days) | S3 | All | Any (All) | Any | mysql manpage contains improperly formatted paragraph |
22746 | 2006-09-27 17:54 | 2006-09-28 9:29 | MySQL Server | Closed (6392 days) | S1 | 5.0.24a | Windows (Windows Server 2003) | Any | MySQL memory grows, runs out of memory and process crashes |
48706 | 2009-11-11 22:51 | 2009-11-13 9:22 | MySQL Migration Toolkit | Won't fix (5250 days) | S2 | 1.1.17 | Windows (XP SP3) | Any | MySQL Migration Toolkit copies only a part of long identifiers names |
48707 | 2009-11-11 23:09 | 2009-11-11 23:14 | MySQL Migration Toolkit | Duplicate (5252 days) | S2 | 1.1.17 | Windows (XP SP3) | Any | MySQL Migration Toolkit copies only a part of long identifiers names |
36879 | 2008-05-22 8:32 | 2008-05-23 12:37 | MySQL Server: Documentation | Closed (5789 days) | S3 | 5.0.51a-3ubuntu5.1-log | Linux (Kubuntu 8.04) | Any | mysql monitor "help max" and "help min" provider no help but "help min max" does |
36814 | 2008-05-20 9:02 | 2011-02-16 23:43 | MySQL Server: Documentation | Closed (5433 days) | S3 | 5.0.51a-3ubuntu5.1-log, 5.0.60 | Linux (Kubuntu 8.04) | Any | mysql monitor help documentation does not match time_format() behaviour |
92789 | 2018-10-16 4:54 | 2021-11-23 18:57 | Connector / NET | Closed (857 days) | S2 | 8.0.12 | Windows (Windows 7/10) | x86 | MySQL Net connector 8.0.12 sends illegal connect attributes. |
62883 | 2011-10-22 21:21 | 2011-11-07 21:02 | MySQL Server | Can't repeat (4526 days) | S2 | 5.5.16 | Any | Any | MySQL Normal Shutdown ! |
76151 | 2015-03-04 19:54 | 2015-03-05 14:08 | MySQL for Windows: MySQL Notifier | Can't repeat (3312 days) | S3 | MySQL Notifier 1.1.5 | Windows (8.1) | Any | MySQL Notifier: High Severity Error on "Check for Updates" |
91060 | 2018-05-29 13:00 | 2018-09-13 18:26 | Connector / ODBC | Closed (2024 days) | S2 | MySQL ODBC 8.0 ANSI Driver 64-bit | Windows | Any (x64) | Mysql ODBC causes write access violation when using Recordset.Move |
28640 | 2007-05-24 3:26 | 2012-09-13 10:48 | Connector / ODBC | Duplicate (6003 days) | S2 | 5.00.11 | Windows | Any | MySQL ODBC Connection MS Access shows #Deleted if Primary key alphanumeric |
68976 | 2013-04-16 21:35 | 2013-07-01 6:54 | Connector / ODBC | Closed (3924 days) | S1 | 5.2.4 | Windows | Any | Mysql ODBC Connector and conversion of Boolean issue |
88313 | 2017-11-01 9:33 | 2017-11-16 9:29 | MySQL Server | Can't repeat (2325 days) | S1 | 5.6.37 | CentOS (CentOS release 6.6 (Final)) | Any | MySQL Often crash and restart immediately |
3453 | 2004-04-13 4:39 | 2004-09-09 13:33 | MySQL Server | Closed (7141 days) | S3 | 4.1 | Any (all) | Any | MySQL output formatting in multibyte character sets |
51239 | 2010-02-17 12:00 | 2011-02-16 23:44 | Connector / NET | Closed (5152 days) | S1 | 6.2.2 | Linux | Any | mysql parameters parse values with the current culture |
74133 | 2014-09-29 11:04 | 2017-12-24 1:00 | MySQL Server | No Feedback (2288 days) | S3 | 5.5.37 | Linux (2.6.32-431.17.1.el6.x86_64) | Any | MySQL periodically crashes with message 'mysqld got signal 11' |
47162 | 2009-09-07 5:55 | 2011-02-16 23:44 | MySQL Server | No Feedback (5287 days) | S2 | 5.0.45 | Linux (Linux server34 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:12 EDT 2008 i686 i686 i386 GNU/Linux) | Any | Mysql predefined query is blocked in |
52672 | 2010-04-07 22:21 | 2013-03-06 10:08 | MySQL Server: Packaging | Closed (4041 days) | S1 | 5.0.90, 5.0.87, maybe others | Linux | Any | MySQL product archive tarballs are corrupted |
68420 | 2013-02-18 19:18 | 2013-02-18 19:33 | MySQL Server: Command-line Clients | Verified (4057 days) | S3 | 5.5+ | Any | Any | MySQL programs produce out of order --help entries |
31225 | 2007-09-27 8:28 | 2011-02-16 23:43 | MySQL Proxy | Closed (5413 days) | S4 | 0.6.0 | Windows | Any | MySQL Proxy is packaged in .tar.gz instead of .zip |
48979 | 2009-11-23 8:54 | 2011-02-16 23:44 | MySQL Server: Query Cache | No Feedback (5178 days) | S5 | 5.0.45 | Linux (red hat 5) | Any | mysql query cache limit size |
38079 | 2008-07-12 21:24 | 2008-07-14 10:08 | MySQL Server: DML | Not a Bug (5737 days) | S4 | 1.2.4 | Windows (XP) | Any | MySQL QueryBrowser ver 1.2.4 |
101990 | 2020-12-14 21:40 | 2020-12-28 11:47 | MySQL Server: Replication | Can't repeat (1187 days) | S2 | 8.0.22 | Ubuntu (20.04 LTS) | x86 (Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz) | MySQL replica fails to recover after an unsafe shutdown |
64325 | 2012-02-14 18:07 | 2012-02-15 12:05 | MySQL Server: Replication | Duplicate (4426 days) | S2 | 5.1.49 | Linux (CentOS 5.5) | Any | MySQL Replication not applying changes |
46382 | 2009-07-25 7:33 | 2011-02-16 23:44 | MySQL Server | No Feedback (5328 days) | S1 | 5.1.35 | Other (Centos 5) | Any | MySQL reports running out of memory |
47681 | 2009-09-28 15:51 | 2009-09-28 17:03 | MySQL Server | Not a Bug (5296 days) | S2 | 5.1.29 - 5.1.38 | Any | Any | MySQL resets Auto-Inc counter when you delete the maximum values & restart |
66564 | 2012-08-28 6:05 | 2012-10-01 1:00 | MySQL Server | No Feedback (4198 days) | S2 | 5.5.23 | Linux (ubuntu) | Any | mysql restars in middle of long run query |
« Show Previous 1000 Entries | Showing 2001-3000 of 5008 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |