Showing 1-1000 of 1226 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
53752 | 2010-05-18 13:47 | 2012-05-18 20:19 | Tools: Random Query Generator | Verified (5262 days) | S2 | bzr | Any | Any | Simplifier unable to produce test file upon simplifying a crash |
53532 | 2010-05-10 8:24 | 2012-05-18 20:19 | Tools: Random Query Generator | Verified | S3 | Any | Any | RQG: internal mysqldump commands fail if mysqldump is not in PATH | |
72615 | 2014-05-12 8:29 | 2014-10-29 15:14 | Tools: MTR / mysql-test-run | Verified (3637 days) | S3 | 5.6+ | Any | Any | MTR --mysqld=--default-storage-engine=foo incompatible w/ dynamically-loaded foo |
44903 | 2009-05-15 13:30 | 2012-06-10 20:45 | Tools: MTR / mysql-test-run | Verified (5611 days) | S3 | 5.1,5.4,6.0 | Any | Any | MTR should try to free disk space if available disk space is below some limit |
31599 | 2007-10-15 9:43 | 2012-06-10 20:45 | Tools: MTR / mysql-test-run | Verified (6194 days) | S3 | 5.0, 5.1 BK | Any | Any | Attaching debugger to MTR valgrind session with --db-attach is unusable |
46967 | 2009-08-28 4:43 | 2011-02-16 23:44 | Tools | Verified (5525 days) | S2 | 5.0, 5.1 | Any | Any | mysqlslap: setting --engine does not get replicated |
45727 | 2009-06-24 19:04 | 2012-05-18 20:19 | Tests: Server | Verified | S3 | 5.4 | Any | Any | Parts of index_merge_innodb.test are disabled due to EXPLAIN diffs |
87190 | 2017-07-26 3:07 | 2018-02-01 5:10 | Tests: Server | Verified (2446 days) | S3 | 8.0.2,8.0.4 | Any | Any | Test main.group_by is unstable |
47826 | 2009-10-05 8:24 | 2015-08-23 20:45 | Tests: Server | Verified | S3 | 5.1-bk | Any | Any | main.partition_innodb fails sometimes with the innodb plugin |
42707 | 2009-02-09 16:56 | 2012-05-18 20:19 | Tests: Cluster | Verified | S3 | Any | Any | Test "partition_auto_increment_ndb" seems not suitable for NDB 6.4 | |
52883 | 2010-04-16 10:12 | 2021-05-02 20:45 | Tests: Cluster | Verified | S3 | Any | Any | testBackup and testSystemRestart uses ssh directly | |
47666 | 2009-09-28 3:02 | 2021-05-02 20:45 | Tests: Cluster | Verified (5493 days) | S3 | mysql-5.0 | Any | Any | ndb_basic test fails due to incorrect result file |
51984 | 2010-03-12 11:17 | 2012-05-18 20:19 | Tests | Verified (5329 days) | S3 | 5.1.44, 5.5.3 | Windows | Any | mysqldump test will not succeed if not preceeded by a test that succeeds as well |
110564 | 2023-03-30 9:09 | 2023-03-30 10:24 | Tests | Verified (563 days) | S3 | 8.0.32 | Any | Any | Router tests failing on macOS |
110594 | 2023-04-03 11:28 | 2023-04-05 7:20 | MySQL Server: XA transactions | Verified (557 days) | S2 | 8.0.32 | Any | Any | Race condition between xa recover and xa start on Transaction_ctx object |
97966 | 2019-12-12 11:59 | 2019-12-14 9:48 | MySQL Server: XA transactions | Verified (1765 days) | S3 | 5.7, 5.7.28 | Any | Any | XA COMMIT in another session will not write binlog event |
102661 | 2021-02-19 11:20 | 2021-02-19 12:17 | MySQL Server: XA transactions | Verified (1332 days) | S3 | 8.0.22, 8.0.23, 5.7.33 | Any | Any | xa prepare failed lead replication error |
87560 | 2017-08-28 9:14 | 2021-04-19 4:25 | MySQL Server: XA transactions | Verified (2496 days) | S2 | mysql-5.7.17 | Any | Any | XA PREPARE log order error in replication and binlog recovery |
60395 | 2011-03-08 17:40 | 2021-10-05 12:05 | MySQL Server: Windows | Verified | S3 | 5.1.56, 5.5.9 | Windows | Any | show global variables requrns weired warnings on JP MS Windows. |
74516 | 2014-10-22 21:34 | 2016-06-30 16:30 | MySQL Server: Windows | QA review (3027 days) | S3 | 5.6.21-log MySQL Community | Windows (developer) | Any | Windows Service Not Recognized by MySQL Notifier |
73017 | 2014-06-17 2:50 | 2014-06-17 5:17 | MySQL Server: Windows | Verified (3771 days) | S3 | 5.6.15 | Windows | Any | slow MySQL recovery logs "MySQL service hung on starting" |
45547 | 2009-06-17 5:26 | 2022-04-10 20:45 | MySQL Server: Windows | Verified (5597 days) | S2 | Windows | Any | Bug&Feature request: Make innodb_fast_shutdown=2 default on Windows | |
104122 | 2021-06-26 21:29 | 2021-06-28 9:17 | MySQL Server: Windows | Verified (1204 days) | S3 | 8.0.25 | Windows (21H1 build 19043.1052) | x86 (Intel x64) | mysqld.exe has weird established local connections with itself on high ports |
56350 | 2010-08-29 20:52 | 2018-09-09 20:45 | MySQL Server: Views | Verified (5158 days) | S3 | 5.0, 5.1 | Other (Win XP) | Any | View of Union with literals compiles with wrong data types. |
35916 | 2008-04-08 22:58 | 2012-05-18 20:19 | MySQL Server: User-defined functions ( UDF ) | Verified (5471 days) | S2 | 5.1.23 | Windows (xp pro) | Any | logging to stderr in a UDF does not work if MySQL is run as service |
15301 | 2005-11-29 0:10 | 2022-12-04 20:45 | MySQL Server: User-defined functions ( UDF ) | Verified (5860 days) | S3 | 5.0.15 | Windows (WinXP pro) | Any | Server mode to reject UDF calls with type mismatched arguments |
38257 | 2008-07-21 12:45 | 2011-02-16 23:43 | MySQL Server: User-defined functions ( UDF ) | Verified (5913 days) | S3 | 5.0, 5.1 | Any | Any | Documentation for initid->max_length not correct |
45620 | 2009-06-19 15:53 | 2011-02-16 23:44 | MySQL Server: User-defined functions ( UDF ) | Verified (5590 days) | S3 | 5.1, 5.4.0-beta | Linux | Any | Server process restart after calling functions from ha_innodb |
26374 | 2007-02-14 17:17 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (6157 days) | S3 | 5.0 BK. 5.1 BK | Linux (Linux) | Any | insert/update of unsigned bigint column fails when using variable larger than |
27475 | 2007-03-27 15:25 | 2013-07-17 16:02 | MySQL Server: Data Types | Verified (6404 days) | S2 | Mysql 5.0.37/5.BK/4.1BK | Windows (Wincows/Linux) | Any | mysql_fetch_field do NOT report correctly certain field types |
38915 | 2008-08-20 13:30 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (5898 days) | S3 | 5.0.45, 5.0.67, 5.1.26 | Linux | Any | LIKE query on DATETIME raises warning |
39049 | 2008-08-26 16:18 | 2018-09-09 20:45 | MySQL Server: Data Types | Patch pending (5786 days) | S3 | 5.0, 5.1, 6.0 | Any | Any | Wrong warning when comparing some decimal values to NULL |
39737 | 2008-09-29 20:09 | 2018-09-09 20:45 | MySQL Server: Data Types | Patch approved (5574 days) | S1 | 5.1.28 | Windows | Any | Assignment operator does not allocate memory for spatial variables |
45004 | 2009-05-21 8:46 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (5624 days) | S2 | 5.0.81, 5.0.83-bzr | Any | Any | Date Value |
49524 | 2009-12-08 5:15 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (5423 days) | S3 | mysql-next-mr(-alik), 5.0, 5.1 | Linux (SUSE 11.1, 2.6.27.37-0.1-default #1 SMP 2009-10-15 14:56:58 +0200 x86_64 x86_64 x86_64 GNU/Linux) | Any | rejecting the maximum value of double when parsing is not enough. |
49639 | 2009-12-12 10:57 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (5419 days) | S3 | 5.0+, 5.1+ | Any | Any | NULL union all with unsigned column should return unsigned type |
57426 | 2010-10-13 9:26 | 2011-02-16 23:44 | MySQL Server: Data Types | Verified (5114 days) | S3 | 5.5 | Any | Any | Mark tables containing old DECIMAL data type as corrupt in 5.5. |
64224 | 2012-02-03 22:15 | 2016-02-04 10:22 | MySQL Server: Data Types | Verified (4635 days) | S2 | 5.1.52, 5.1.56, 5.5.20, 5.6.28 | Any | Any | bug in fractional part of unsigned decimals |
69999 | 2013-08-12 17:44 | 2014-11-27 21:06 | MySQL Server: Data Types | Verified (3608 days) | S2 | Any | Any | Questionable RAND() argument range/type/error | |
70091 | 2013-08-20 12:30 | 2013-08-21 17:26 | MySQL Server: Data Types | Verified (4071 days) | S2 | 5.6.13 | Linux (Ubuntu x86_64) | Any | tinyint(1) column type returned by jdbc connector becomes Integer with ORDER BY |
71754 | 2014-02-17 19:48 | 2014-02-18 7:21 | MySQL Server: Data Types | Verified (3891 days) | S3 | Any | Any | TIMESTAMP approacing End Of Lifetime :-) | |
72672 | 2014-05-16 18:17 | 2014-05-22 9:21 | MySQL Server: Data Types | Verified (3797 days) | S2 | 5.5.31,5.5.34, 5.7.5, 5.6.19 | Any | Any | Zero-valued DATETIME column can be simultaneously NULL and NOT NULL |
73249 | 2014-07-09 20:06 | 2014-07-14 17:18 | MySQL Server: Data Types | Verified (3744 days) | S3 | 5.5.36-log, 5.6.38, 5.6.20 | Linux | Any | Inconsistent behavior when doing subtraction on columns |
81116 | 2016-04-18 2:14 | 2016-05-02 9:11 | MySQL Server: Data Types | Verified (3100 days) | S2 | 5.6.30, 5.5.49 | CentOS (6.7) | Any | Evaluating between DECIMAL and string returns different result depends on index |
84558 | 2017-01-18 17:07 | 2017-01-18 19:36 | MySQL Server: Data Types | Verified (2825 days) | S3 | 5.5/5.6/5.7/8.0 | Any | Any | Cast to NUMERIC not working |
103289 | 2021-04-12 15:00 | 2021-05-11 5:28 | MySQL Server: Data Types | Verified (1251 days) | S3 | 8.0 | Any | Any | bit type display confusing |
105170 | 2021-10-08 9:03 | 2021-10-08 14:24 | MySQL Server: Data Types | Verified (1101 days) | S3 | 5.7 | Any (v10) | Any | wrong data returned grouping on substring and bit |
105819 | 2021-12-07 9:48 | 2021-12-07 14:38 | MySQL Server: Data Types | Verified (1041 days) | S3 | 8.0 | Any | Any | Conversion from Blob/Text column value to double does not return a truncation er |
24424 | 2006-11-19 4:28 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (6127 days) | S1 | 5.1.11 | Any (ALL) | Any | CHAR data-type not space-padding |
43100 | 2009-02-23 7:54 | 2022-09-04 20:45 | MySQL Server: Data Types | Verified (5709 days) | S3 | 6.0.10, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | Discrepancy between engines MyISAM/Maria wrong? with Year(2) type |
44874 | 2009-05-14 11:56 | 2018-09-09 20:45 | MySQL Server: Data Types | Verified (5627 days) | S3 | 5.0, 5.1, 6.0 | Linux (debian 7) | Any | select into outfile exports wrong integer width |
63468 | 2011-11-29 8:12 | 2011-11-29 11:20 | MySQL Server: Data Types | Verified (4702 days) | S3 | 5.1/5.5 | Any | Any | different behavior for int/bigint of comparing |
81295 | 2016-05-03 13:35 | 2016-05-03 16:10 | MySQL Server: Data Types | Verified (3085 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 |
105754 | 2021-11-30 15:54 | 2021-12-01 13:45 | MySQL Server: Data Types | Verified (1047 days) | S3 | 8.0 | Any | Any | Selecting from column with type "date" returns weird results when joining |
108207 | 2022-08-21 13:35 | 2022-08-23 13:36 | MySQL Server: Data Types | Verified (783 days) | S3 | 8.0 | Any (Centos, window) | Any | information schema view return wrong data type |
108466 | 2022-09-13 6:03 | 2022-09-24 12:29 | MySQL Server: Data Types | Verified (761 days) | S3 | 5.7.38, 5.7.39 | Any | Any | "create table ... select" generates columns of type BIGINT with illegal width |
66937 | 2012-09-23 21:27 | 2012-12-14 17:38 | MySQL Server: Data Types | Verified (4321 days) | S3 | 5.5 | Any | Any | return type from nullif is described incorrectly as string type |
69042 | 2013-04-23 16:31 | 2017-07-13 18:49 | MySQL Server: Data Types | Verified (4190 days) | S3 | 5.1.68, 5.5.31, 5.6.11 | Any | Any | MEDIUMINT precision/type incorrect in INFORMATION_SCHEMA.COLUMNS |
8485 | 2005-02-13 0:40 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (5858 days) | S3 | 5.0.3-alpha-debug | Linux (SuSE 9.1) | Any | BOOLEAN: Silent data type change to TINYINT |
40747 | 2008-11-14 15:03 | 2020-05-03 20:45 | MySQL Server: Data Types | Verified (5812 days) | S3 | 5.0.70, 5.1.29, 6.0.7 | Any | Any | Duplicate datetime truncation warning if a range optimizer is used. |
45300 | 2009-06-03 11:52 | 2022-12-04 20:45 | MySQL Server: Data Types | Verified (4944 days) | S3 | 5.1.37 | Any | Any | MAX() and ENUM type |
62861 | 2011-10-21 11:50 | 2011-10-25 10:17 | MySQL Server: Data Types | Verified (4741 days) | S3 | 5.1.60, 5.5.17 | Linux | Any | Wrong data type for user-variables in MySQL 5.1 |
64058 | 2012-01-18 14:14 | 2012-01-19 14:05 | MySQL Server: Data Types | Verified (4651 days) | S2 | 5.5.20 | MacOS (10.7.2) | Any | DATETIME data type botched in queries. |
69666 | 2013-07-03 19:09 | 2014-07-22 19:40 | MySQL Server: Data Types | Verified (3736 days) | S3 | 5.5.31, 5.6.21 | Any | Any | Strange result types for LPAD/RPAD and CONCAT when mixing binary and non-binary |
65958 | 2012-07-20 9:35 | 2012-07-23 10:13 | MySQL Server: Data Types | Verified (4465 days) | S3 | 5.5.24 | Linux (Ubuntu Server 12.04) | Any | en_ZA number format incorrect |
78507 | 2015-09-22 2:48 | 2015-09-22 7:34 | MySQL Server: Data Types | Verified (3309 days) | S3 | 5.6.22, 5.7.10, 5.6.28, 5.5.47, 5.1.77 | Any | Any | Type for "@a=now()" and "@b=NULL" is MEDIUM_BLOB |
78635 | 2015-09-30 6:56 | 2016-06-18 21:28 | MySQL Server: Data Types | Verified (3301 days) | S3 | 5.7.8, 5.7.10, 8.0.10, 5.6.27 | Any | Any | Non-MySQL data types are not translated in procedure/function params |
62157 | 2011-08-12 15:59 | 2012-05-18 20:19 | MySQL Server: Tests | Verified (4811 days) | S3 | 5.5 | Any | Any | binlog.binlog_bug36391 fails when run with --repeat=2 |
60343 | 2011-03-04 16:39 | 2011-09-13 19:21 | MySQL Server: Tests | Verified (4779 days) | S3 | 5.5 | Any | Any | where are the crash recovery tests? |
61595 | 2011-06-22 7:36 | 2013-12-22 23:58 | MySQL Server: Tests | Verified (3948 days) | S3 | 5.1, 5.5 | Any | Any | [PATCH] mysql-test/include/wait_for_slave_param.inc timeout logic is incorrect |
62156 | 2011-08-12 15:57 | 2012-05-18 20:19 | MySQL Server: Tests | Verified (4811 days) | S3 | 5.5 | Any | Any | main.func_str fails when run with --repeat=2 |
51907 | 2010-03-10 12:26 | 2021-05-02 20:45 | MySQL Server: Tests | Verified (5304 days) | S3 | 5.5.3 | Any | Any | main.ctype_utf8mb4_ndb fails persistently |
84348 | 2016-12-27 19:17 | 2016-12-27 21:54 | MySQL Server: Storage Engines | Verified (2847 days) | S3 | 5.5/5.6/5.7/8.0 | Any | Any | ha_example.cc and ha_example.h confusing comments in source |
74910 | 2014-11-18 0:05 | 2015-02-01 6:30 | MySQL Server: Storage Engines | Verified (3617 days) | S2 | 5.6.20, 5.6.23, 5.7.6, 5.5.42 | Any | Any | ERROR 1030 (HY000): Got error -1 from storage engine for ARCHIVE storage engine |
105982 | 2021-12-27 8:11 | 2022-01-03 8:02 | MySQL Server: Storage Engines | Verified (1014 days) | S5 | all, 5.7, 8.0 | Linux | Any | hard-coded libaio API parameter may not helpful to performance |
84359 | 2016-12-28 12:53 | 2016-12-28 13:41 | MySQL Server: Storage Engines | Verified (2846 days) | S3 | 5.5/5.6/5.7/8.0 | Any | Any | ha_example.cc remove oudated info from comment |
49329 | 2009-12-02 9:21 | 2013-03-03 20:45 | MySQL Server: Storage Engines | Verified (5420 days) | S3 | 5.1.42-bzr | Any | Any | example (and other) engines use wrong collation for open tables hash |
79498 | 2015-12-02 23:21 | 2019-08-27 23:36 | MySQL Server: Storage Engines | Verified (1874 days) | S3 | 5.6.24, 5.6.29, 5.7.11 | Any | Any | default_tmp_storage_engine not always respected |
100750 | 2020-09-05 9:21 | 2020-10-29 10:45 | MySQL Server: Storage Engines | Verified (1499 days) | S3 | 8.0.21, 5.7.31 | Any | Any | Unknown error is given when trying to alter engine for a table |
113300 | 2023-12-01 6:37 | 2023-12-01 14:04 | MySQL Server: Storage Engines | Verified (317 days) | S3 | 8.0 | Any | Any | Inconsistent error message when create table using partition |
36518 | 2008-05-05 21:32 | 2022-12-04 20:45 | MySQL Server: Stored Routines | Verified (6004 days) | S3 | 5.1 and up | Any | Any | Plugin refcount leak with cursors and exceptions |
39137 | 2008-08-30 18:53 | 2022-12-04 20:45 | MySQL Server: Stored Routines | Verified (5887 days) | S2 | 5.0.51, 5.0.66a | Linux (Ubuntu hardy) | Any | DELETE makes stored function to fail (if table type is MyISAM) |
60300 | 2011-03-02 1:30 | 2011-03-03 9:03 | MySQL Server: Stored Routines | Verified (4973 days) | S2 | 5.5.9 | Windows (XP Prof.) | Any | Corrupted values using variable of type TEXT in trigger or stored procedure |
39173 | 2008-09-02 8:39 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Verified (5885 days) | S3 | 5.1.26, 5.1 bzr | Any (Linux, Windows) | Any | Unable to remove event's ENDS |
78144 | 2015-08-19 22:34 | 2015-11-24 9:07 | MySQL Server: Stored Routines | Verified (3341 days) | S3 | 5.6.19-log | Linux (RDS) | Any | Error handler not being triggered for multi-table update |
31643 | 2007-10-16 15:26 | 2022-12-12 5:54 | MySQL Server: Stored Routines | Verified (5793 days) | S3 | 5.1.22 | Any | Any | Setting an event to 'disable on slave' disables it on the master |
113835 | 2024-01-31 13:48 | 2024-02-03 16:56 | Shell VSCode Extension | Verified (255 days) | S3 | v1.14.2 | MacOS | ARM (m2 chip) | Copy and paste not working |
111589 | 2023-06-27 18:37 | 2023-07-21 16:31 | MySQL Operator | Verified (450 days) | S3 | Any | Any | MySQL Operator - split brain on all data nodes | |
111999 | 2023-08-08 14:50 | 2023-08-09 19:39 | MySQL Operator | Verified (432 days) | S3 | Any | Any | MySQL Operator - backup jobs are not clear | |
108544 | 2022-09-19 16:50 | 2023-02-17 15:04 | MySQL Operator | Verified (745 days) | S1 | 5.0.30 | Any | Any | MySQL Operator unable to login using SSH |
111831 | 2023-07-20 16:27 | 2023-07-24 15:49 | MySQL Operator | Verified (447 days) | S3 | Any | Any | MySQL Operator - initdb with PVC | |
108956 | 2022-11-01 16:17 | 2022-11-08 16:00 | MySQL Operator | Verified (705 days) | S1 | 8.0.30 | Any | Any | Mysql Operator backups |
113244 | 2023-11-28 7:35 | 2023-12-08 9:44 | MySQL Operator | Verified (318 days) | S2 | 8.2.0-2.1.1 | Linux | Any | set ‘deleteBackupData’ field, no effect |
114696 | 2024-04-19 3:43 | 2024-05-07 8:07 | MySQL Operator | Verified (159 days) | S3 | 8.3.0-2.1.2 | Any | Any | deleteBackupData not work when delete mbk cr |
111269 | 2023-06-05 0:13 | 2023-06-05 15:38 | MySQL Operator | Verified (496 days) | S3 | 8.0.33-2.0.10 | Linux | x86 | Increasing pvc storage request amount has no effect |
116231 | 2024-09-25 15:01 | 2024-09-25 15:03 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Verified (18 days) | S3 | 8.4.1 | Red Hat (8.9) | x86 | Router reports: Ignoring unsupported instance <host:port>, type: 'group-member' |
101968 | 2020-12-11 1:09 | 2020-12-17 22:32 | Shell General / Core Client | Verified (1396 days) | S1 | 8.0.22 | Windows | Any | MySQL Shell 8.0.22 crashes every time when loading a dump into MySQL 5.7.27 |
90468 | 2018-04-17 9:30 | 2018-05-09 11:18 | Shell General / Core Client | Analyzing (2349 days) | S3 | 1.0.11,8.0.4 | Red Hat (7.4) | x86 | "Access denied" when execute cluster.forceQuorumUsingPartitionOf |
99795 | 2020-06-07 12:06 | 2020-08-03 14:33 | Shell General / Core Client | Verified (1532 days) | S2 | 8.0.20, 8.0.21 | Any | Any | shell.dump_rows()/shell.dumpRows() does ont work with SqlResult |
104795 | 2021-09-01 19:06 | 2023-10-31 15:58 | Shell General / Core Client | Verified (1137 days) | S3 | 8.0.26 | Ubuntu (20.04) | x86 | Impossible to type upper-case cyrillic letter И in MySQL Shell |
111915 | 2023-07-28 16:57 | 2023-08-10 12:11 | MySQL Server: Security: Encryption | Verified (431 days) | S3 | 8.0 | Windows (10) | Other (8th Gen Intel(R) Core(TM) i7-1165G7) | Fail to configurate Component keyring in windows 11 and 10 |
114856 | 2024-05-02 16:32 | 2024-05-22 7:07 | MySQL Server: Security: Encryption | Verified (144 days) | S2 | 8.4.0 | Any | Any | Odd errors after starting mysqld with ssl_mode=disabled in my.cnf |
82452 | 2016-08-04 7:46 | 2016-08-04 8:29 | MySQL Server: Security: Encryption | Verified (2992 days) | S2 | 5.7.12-enterprise-commercial-advanced, 5.7.14 | Windows (Windows 7) | Any | CSV storage engine shouldn't have TDE option |
56846 | 2010-09-17 16:26 | 2013-03-03 20:45 | MySQL Server: Storage Engine API | Verified (5140 days) | S3 | next-mr | Any | Any | Performance of ha_check_if_table_exists() is not the best |
109444 | 2022-12-21 4:59 | 2022-12-21 7:45 | MySQL Server: Storage Engine API | Verified (662 days) | S3 | 8.0.31 | Any | Any | Handler table flag HA_REQUIRES_KEY_COLUMNS_FOR_DELETE is unused |
109445 | 2022-12-21 5:14 | 2022-12-21 7:45 | MySQL Server: Storage Engine API | Verified (662 days) | S3 | 8.0.31 | Any | Any | Handler table flag HA_DUPLICATE_KEY_NOT_IN_ORDER is unused |
44373 | 2009-04-20 20:57 | 2012-09-11 19:37 | MySQL Server: Storage Engine API | Verified (4415 days) | S2 | 5.1.30, 5.1, azalea bzr | Any | Any | handler::column_bitmaps_signal not called before handler::rnd_pos |
46228 | 2009-07-16 14:45 | 2013-03-03 20:45 | MySQL Server: Storage Engine API | Verified (5556 days) | S3 | 5.1 | Any | Any | Inconsistent key_part definition for index creation |
68697 | 2013-03-17 13:56 | 2013-03-18 19:43 | MySQL Server: Storage Engine API | Verified (4228 days) | S5 | 5.5.31, 5.6.11 | Any | Any | loose rec_per_key precision according to whole integer type |
45876 | 2009-07-01 13:14 | 2017-12-16 9:57 | MySQL Server: Storage Engine API | Verified | S3 | 5.1.35 | Any | Any | SHOW ENGINES output is inaccurate |
35544 | 2008-03-25 9:19 | 2013-04-14 20:45 | MySQL Server: Storage Engine API | Verified (5029 days) | S3 | 5.1+ | Any | Any | ABI compatibility of pluggable storage engines |
41801 | 2008-12-31 1:21 | 2018-09-09 20:45 | MySQL Server: Storage Engine API | Verified (5758 days) | S2 | 5.0.67, 5.1.30, 6.0.8 | Any | Any | Read Only Archive storage engine tables crashes MySQL |
43681 | 2009-03-16 17:32 | 2011-02-16 23:43 | MySQL Server: Storage Engine API | Verified (5690 days) | S3 | 5.1+ | Any | Any | Need a way to pass extra info to storage engine during create |
78050 | 2015-08-13 7:29 | 2016-12-14 4:54 | MySQL Server: Storage Engine API | Verified (3349 days) | S3 | 5.6.26 | Linux | Any | Crash on when XA functions activated by a storage engine |
111184 | 2023-05-29 12:20 | 2023-05-29 13:23 | MySQL Server: Storage Engine API | Verified (503 days) | S3 | 8.0 | Any | Any | Execution plan display error |
82370 | 2016-07-28 14:46 | 2016-08-10 14:03 | MySQL Server: Replication | Verified (2999 days) | S3 | 5.6,5.7 | Any | Any | Testcase for bug 32228 (rpl_cant_read_event_incident) missing from 5.6+ trees? |
86685 | 2017-06-13 18:51 | 2017-09-21 16:15 | MySQL Server: Replication | Verified (2649 days) | S1 | 5.6.25 | Windows | Any | Binolog corruption when using MEB 3.12.1 on mysql server on windows 2012 r2 |
89395 | 2018-01-25 8:37 | 2018-09-08 20:17 | MySQL Server: Replication | Verified (2330 days) | S2 | 5.7.18 | CentOS (Linux version 2.6.32-696.18.7.el6.x86_64 (mockbuild@c1bl.rdu2.centos.org)) | Any | Slave unable to start with err message - could not locate rotate events |
95249 | 2019-05-05 8:11 | 2023-05-04 16:25 | MySQL Server: Replication | Verified (1987 days) | S2 | mysql-5.7 | Any | Any | stop slave permanently blocked |
107928 | 2022-07-20 23:09 | 2022-07-26 2:17 | MySQL Server: Replication | Verified (815 days) | S2 | 8.0 | Any | Any | MySQL 8.0 Replication breaks when tmpdir space is filled |
95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (1962 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
71111 | 2013-12-09 2:45 | 2014-03-25 6:54 | MySQL Server: Replication | Verified (3959 days) | S3 | 5.6.15 | Any | Any | strange replication broken on slave |
75203 | 2014-12-13 14:45 | 2014-12-15 11:44 | MySQL Server: Replication | Verified (3590 days) | S3 | 5.7.5-m15 | Any | Any | Misleading error when binlog name contains 4 byte utf8 on chaning to table |
88754 | 2017-12-05 8:07 | 2017-12-05 13:14 | MySQL Server: Replication | Verified (2504 days) | S3 | 5.5.24, 5.5.58 | Any | Any | table id overflow causes replication out of sync |
112364 | 2023-09-15 21:40 | 2023-09-22 23:44 | MySQL Server: Replication | Verified (389 days) | S3 | 8.0.34 | Any | Any | Create table like doesn't write the charset on binlog if its created from a temp |
52537 | 2010-04-01 19:20 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5309 days) | S3 | 5.1+, 4.1, 5.0, 5.1, 5.6.99 | Any | Any | slave data inconsistency due to the magic version comments |
104015 | 2021-06-15 0:31 | 2022-05-27 20:28 | MySQL Server: Replication | Verified (1210 days) | S2 | 8.0.25, 5.7.34 | Any | Any | Loosing semi-sync acks could stall the primary. |
80670 | 2016-03-09 9:16 | 2016-03-09 11:17 | MySQL Server: Replication | Verified (3140 days) | S3 | 5.7.11 | CentOS | Any | Assertion `thd->variables.gtid_next.type == AUTOMATIC_GROUP' failed |
77252 | 2015-06-05 6:01 | 2019-05-10 1:04 | MySQL Server: Replication | Verified (2029 days) | S2 | 5.6 | Any | Any | MASTER POS IN MYSQL BINARY LOG IS WRONG. |
72591 | 2014-05-09 8:36 | 2014-05-09 8:37 | MySQL Server: Replication | Verified | S3 | 5.6.20 | Any | Any | minor memory leak on failure in function check_temp_dir |
74908 | 2014-11-17 22:58 | 2015-07-07 8:40 | MySQL Server: Replication | Verified (3386 days) | S2 | 5.6.21, 5.6.27 | Linux (Ubuntu 14.04 LTS x86_64) | Any | Unable to detect network timeout in 5.6 when using SSL (regression from 5.5) |
80402 | 2016-02-17 9:44 | 2016-02-17 12:13 | MySQL Server: Replication | Verified (3161 days) | S3 | 5.6, 5.6.29 | Any | Any | Delayed replication configuration does not support sub-second precision |
48062 | 2009-10-14 23:09 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5477 days) | S2 | 5.0.85, 5.1.41 | Linux | Any | Date artithmetic in stored procedure breaks replication |
83613 | 2016-10-30 14:36 | 2016-11-16 16:12 | MySQL Server: Replication | Verified (2888 days) | S3 | 5.6.32 | Any | Any | compile error: size of array ‘compile_time_assert’ is negative added SQL command |
95064 | 2019-04-19 11:05 | 2021-04-27 20:23 | MySQL Server: Replication | Verified (2004 days) | S2 | 5.7.22 | Any | x86 | slave server may has gaps in Executed_Gtid_Set when a special case happen |
97780 | 2019-11-26 6:05 | 2020-04-14 14:27 | MySQL Server: Replication | Verified (1781 days) | S3 | MySQL5.7, 5.7.28 | Any | Any | Two different type engines in Mysql cause error (assert in debug) in Binlog Xa |
98799 | 2020-03-02 12:08 | 2021-01-14 8:43 | MySQL Server: Replication | Verified (1684 days) | S2 | 5.7, 5.7.29 | Any | Any | Replication failing on valid scenario |
103943 | 2021-06-08 11:42 | 2022-08-15 3:26 | MySQL Server: Replication | Verified (1146 days) | S1 | 5.7.33 | CentOS (7.6) | x86 (64) | Semi-Replication Rotate And Purge Relaylog Leads To Increased Response |
109217 | 2022-11-28 9:51 | 2022-12-12 3:19 | MySQL Server: Replication | Verified (671 days) | S2 | 5.7.40 | Any | Any | The datas of master and standby are inconsistent for Spatial Data Formats |
109977 | 2023-02-08 8:05 | 2023-02-08 8:30 | MySQL Server: Replication | Verified (613 days) | S3 | 8.0.32,5.7.41 | Any | Any | Contribution by Tencent: semisync plugin may print a negative server id |
114361 | 2024-03-15 1:53 | 2024-08-14 9:34 | MySQL Server: Replication | Verified (209 days) | S5 | 8.0 | Any | Any | Unaligned Delegate's lock reduces performance |
115741 | 2024-08-01 11:13 | 2024-08-22 6:55 | MySQL Server: Replication | Verified (67 days) | S1 | 8.0 | Any | Any | Slave stops with HA_ERR_KEY_NOT_FOUND with HASH_SCAN and index used to search fo |
49533 | 2009-12-08 13:08 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (5423 days) | S3 | 5.1,mysql-5.1-rep+3,mysql-6.0-codebase-b | Any | Any | Overflow in DECIMAL, SBR out of sync |
66733 | 2012-09-07 13:45 | 2019-05-30 9:34 | MySQL Server: Replication | Verified (4149 days) | S3 | 5.6 | Any | Any | Need to be able to set binary_log_space_limit |
72195 | 2014-04-01 18:50 | 2016-02-25 12:24 | MySQL Server: Replication | Verified | S3 | 5.6.17 | Any | Any | GTID restriction with non-transactional storage engines unclear |
80168 | 2016-01-27 8:21 | 2018-05-21 1:44 | MySQL Server: Replication | Verified (3182 days) | S3 | 5.7.10, 5.7.12 | CentOS | Any | Assertion `get_state() >= 0' failed in sql/rpl_gtid.h:535 |
80663 | 2016-03-09 4:54 | 2018-11-24 15:24 | MySQL Server: Replication | Verified (2150 days) | S3 | 5.7.10, 5.7.11, 8.0.13 | CentOS | Any | Assertion `thd->owned_gtid.is_empty()' failed in sql/rpl_gtid_state.cc:613 |
80665 | 2016-03-09 6:17 | 2016-03-09 7:18 | MySQL Server: Replication | Verified (3140 days) | S3 | 5.7.10, 5.7.11 | CentOS | Any | Assertion `thd->owned_gtid. sidno == THD::OWNED_SIDNO_ANONYMOUS' failed |
80694 | 2016-03-10 16:32 | 2016-03-11 8:44 | MySQL Server: Replication | Verified (3138 days) | S3 | 5.7.11 | CentOS | Any | Assertion `!xid->is_null() || !(thd->variables.option_bits & (1ULL<< 18))' faild |
83432 | 2016-10-18 20:07 | 2016-10-19 10:12 | MySQL Server: Replication | Verified (2916 days) | S2 | 5.7.15, 5.7.16 | Any | Any | slave failes to start after inport of a logical dump from master |
83970 | 2016-11-25 21:10 | 2016-12-05 16:13 | MySQL Server: Replication | Verified (2869 days) | S3 | Any | Any | Unclear error from engines not supporting sql_exec_mode=IDEMPOTENT | |
85064 | 2017-02-20 2:39 | 2017-02-20 8:42 | MySQL Server: Replication | Verified (2792 days) | S1 | 5.7.17 | Any | Any | end_anonymous_gtid_violating_transaction(): Assertion `old_value >= 1' failed. |
85142 | 2017-02-23 6:40 | 2017-03-06 9:35 | MySQL Server: Replication | Verified (2778 days) | S3 | 5.6, 5.7 | Any | Any | reducing MTS checkpointing causes high IO load |
85220 | 2017-02-28 8:34 | 2017-05-04 4:17 | MySQL Server: Replication | Verified (2719 days) | S1 | 5.7.17 | Any | Any | Assertion `(*thd)->get_transaction()->xid_state()-> has_state(XID_STATE::XA_... |
85695 | 2017-03-30 5:34 | 2019-11-07 17:39 | MySQL Server: Replication | Verified (2752 days) | S1 | 5.7, 5.7.17 | Any | Any | An incident event has been written to the binary log which will stop the slaves |
87326 | 2017-08-05 3:21 | 2017-08-23 17:58 | MySQL Server: Replication | Verified (2608 days) | S2 | 5.6.27 - 5.6.35 | Any | Any | deadlock in binary log. |
87576 | 2017-08-29 9:48 | 2017-08-29 10:11 | MySQL Server: Replication | Verified (2602 days) | S3 | 5.7.19 | Ubuntu | Any | Assertion `bitmap_is _clear_all(&table->tmp_set)' failed |
91477 | 2018-06-28 16:12 | 2018-07-16 16:22 | MySQL Server: Replication | Verified (2298 days) | S3 | 5.7.22 | Any | Any | Slave writes less when connected intermediary master with blackhole engine |
98665 | 2020-02-19 12:27 | 2020-03-04 5:20 | MySQL Server: Replication | Verified (1690 days) | S3 | 8.0.19, 5.7.29 | Any | Any | replication broken on blackhole node if binlog_rows_query_log_events on master |
104034 | 2021-06-16 10:04 | 2021-06-17 6:11 | MySQL Server: Replication | Verified (1214 days) | S3 | 5.7.20, 8.0, 5.7.34 | Any | Any | sub_iv may be NULL in Gtid_set::is_interval_subset |
109016 | 2022-11-07 11:51 | 2022-11-08 15:57 | MySQL Server: Replication | Verified (705 days) | S3 | 5.7.38 | Any | Any | Slave crashed when master restart |
111540 | 2023-06-23 3:41 | 2023-06-23 5:15 | MySQL Server: Replication | Verified (478 days) | S5 | 8.0.32 | Any | Any | binlog compress optimize |
36574 | 2008-05-07 18:13 | 2017-05-21 20:45 | MySQL Server: Replication | Verified (6003 days) | S3 | 5.1, 6.0 | Any | Any | ROLLBACK trxs with no logged non-trx updates should not be written to binlog |
85623 | 2017-03-25 10:21 | 2021-04-08 9:46 | MySQL Server: Replication | Verified (2756 days) | S3 | 5.7.17 | Any | Any | Unable to skip replication error Query caused different errors on master-slave |
85292 | 2017-03-03 14:48 | 2017-03-03 14:49 | MySQL Server: Row Based Replication ( RBR ) | Verified | S2 | 5.6+ | Any | Any | unreachable statement in function process_event with event type QUERY_EVENT |
91822 | 2018-07-28 3:56 | 2018-07-30 10:55 | MySQL Server: Row Based Replication ( RBR ) | Verified (2267 days) | S3 | 5.6, 5.6.41, 5.5.60 | Debian | Any | incorrect datatype in RBR event when column is NULL and not explicit in query |
54249 | 2010-06-05 2:32 | 2017-05-21 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified (5243 days) | S3 | 5.1 | Any | Any | More verbose RBR error logging |
60784 | 2011-04-06 22:13 | 2014-09-25 19:58 | MySQL Server: Row Based Replication ( RBR ) | Verified (4937 days) | S1 | 5.5.8-log MySQL Communit | Linux | Any | Last_SQL_Errno: 1677 |
78265 | 2015-08-28 20:48 | 2015-08-31 22:37 | MySQL Server: Row Based Replication ( RBR ) | Verified (3331 days) | S3 | 5.6.26, 5.7.8, 5.7.9 | Any | Any | utf8 on master and utf8mb4 on slave leads to "cannot be converted from type" err |
88595 | 2017-11-21 22:12 | 2022-11-24 12:06 | MySQL Server: Row Based Replication ( RBR ) | Verified (2447 days) | S2 | 5.6.37 | Any | Any | Row-based master-master replication broken by add column or drop column |
56007 | 2010-08-16 10:54 | 2023-02-12 20:45 | MySQL Server: Row Based Replication ( RBR ) | Verified | S2 | 5.6.99-m5 | Any | Any | Blackhole slave replication: 2nd slave stops with an error for UPDATE statement |
88057 | 2017-10-11 12:42 | 2018-06-13 12:32 | MySQL Server: Row Based Replication ( RBR ) | Verified (2559 days) | S3 | 5.7.19, 8.0.3 | Any | Any | Intermediary slave does not log master changes with binlog_rows_query_log_events |
96142 | 2019-07-09 13:24 | 2019-07-10 8:48 | MySQL Server: Row Based Replication ( RBR ) | Verified (1922 days) | S3 | 5.6,5.7, 5.6.44, 5.7.26 | Any | Any | Inconsistent error on slave for Update event on table with non-exists partition |
111310 | 2023-06-07 6:51 | 2023-06-08 8:30 | MySQL Server: Prepared statements | Verified (493 days) | S3 | 8.0.33 | Ubuntu (22.04) | x86 (x86_64) | Prepared statement with CTE memory leak |
1382 | 2003-09-23 9:40 | 2022-12-04 20:45 | MySQL Server: Prepared statements | Verified (6473 days) | S2 | 4.0, 4.1, 5.0, 5.1 | Any (all) | Any | SQLDescribeParam returns the same type information |
113301 | 2023-12-01 7:22 | 2023-12-01 8:53 | MySQL Server: Prepared statements | Verified (317 days) | S2 | 8.0.35, 8.0.31 | Any | Any | using preparation statement to query the time type data, some data is not found |
82139 | 2016-07-07 8:41 | 2016-07-07 10:33 | MySQL Server: Prepared statements | Verified (3020 days) | S2 | 5.7.13 | Any | Any | MySQL server sends internal column type over the wire |
111921 | 2023-07-31 7:57 | 2023-08-11 12:14 | MySQL Server: Prepared statements | Verified (439 days) | S3 | 8.0 | Any | Any | Reusing prepared statement for different data types, different outcomes are obse |
114338 | 2024-03-13 16:41 | 2024-03-19 11:10 | MySQL Server: Prepared statements | Verified (213 days) | S3 | 8.0 | Any | Any | Client might receive incorrect data in ps-protocol |
104118 | 2021-06-26 2:42 | 2022-08-23 8:45 | MySQL Server: Security: Privileges | Verified (1202 days) | S2 | 8.0.24 | Any | Any | MGR all second node abnormal stop |
70431 | 2013-09-26 8:05 | 2015-07-15 7:11 | MySQL Server: Security: Privileges | Verified (3378 days) | S1 | 5.6.13 | Any (CentOS) | Any | 5.6 CRASHES WHEN READING ANCIENT SYSTEM TABLES |
20235 | 2006-06-02 18:03 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified (6101 days) | S3 | 5.0.21-community-nt | Windows (win32 - XP SP2, Fedora core 5) | Any | Unable to SHOW CREATE PROCEDURE without SELECT grant |
50238 | 2010-01-11 15:08 | 2022-12-04 20:45 | MySQL Server: Security: Privileges | Verified | S3 | 5.5.1-m2 | Any | Any | 'GRANT SUPER' doesn't give 'TABLESPACE' priv in fresh 5.5, upgrade from 5.1 does |
110421 | 2023-03-18 4:02 | 2023-03-26 8:13 | MySQL Server: Security: Privileges | Verified (567 days) | S3 | 8.0.32 | Linux | Any | MySQL server not honoring connection_memory_limit for user created temp tables |
82733 | 2016-08-25 21:56 | 2016-08-27 8:10 | MySQL Server: Security: Privileges | Verified (2969 days) | S3 | 5.6, 5.7, 5.6.32 | Any | Any | Login errors after GRANT ON *.* in sql_mode PAD_CHAR_TO_FULL_LENGTH |
70030 | 2013-08-14 9:27 | 2014-07-22 18:43 | MySQL Server: Security: Privileges | Verified (3737 days) | S3 | 5.6.12 | Any | Any | current_user does not reflect expected value |
73258 | 2014-07-10 11:19 | 2014-07-10 12:27 | MySQL Server: Security: Privileges | Verified (3748 days) | S3 | >= 5.6.3, 5.6.20 | Linux | Any | Unable to analyze ALL queries with EXPLAIN on read-only account |
78303 | 2015-09-02 10:02 | 2016-09-22 7:50 | MySQL Server: Performance Schema | Verified (3329 days) | S3 | 5.7 | Any | Any | Add some DNS latency timings to performance_schema (host_cache?) |
94925 | 2019-04-06 0:15 | 2019-04-24 13:37 | MySQL Server: Performance Schema | Verified (1999 days) | S3 | 8.0.15 | Any | Any | Wrong Query Sample Text in Performance Query |
81394 | 2016-05-12 13:40 | 2023-09-18 15:54 | MySQL Server: Performance Schema | Verified (391 days) | S3 | 5.7.12,5.7.15 | Any | Any | Unable to change performance_schema whilst super_read_only is enabled |
101391 | 2020-10-30 3:04 | 2020-11-19 16:59 | MySQL Server: Performance Schema | Verified (1424 days) | S5 | 8.0, 8.0.22 | Any | Any | Performance Schema storage engine doesn't use index optimizations on group by |
84655 | 2017-01-24 22:59 | 2017-06-27 7:44 | MySQL Server: Performance Schema | Verified (2818 days) | S3 | 5.7.17 | Any | Any | replication worker thread status not showing on performance_schema.threads |
99204 | 2020-04-07 20:52 | 2020-04-13 15:53 | MySQL Server: Performance Schema | Verified (1649 days) | S3 | 5.7.29, 8.0.19 | Any | Any | performance_schema threads table PROCESSLIST_INFO incorrect behaviour |
110857 | 2023-04-28 5:56 | 2023-05-02 13:01 | MySQL Server: Performance Schema | Verified (534 days) | S3 | 8.0.30, 8.0.33, 5.7.42 | CentOS (CentOS (CentOS Linux 7 (Core))) | Any ((Linux 3.10.0-1160.49.1.el7.x86_64)) | invalid NO_INDEX_USED=1 metric when using UNION in queries. |
113659 | 2024-01-17 7:55 | 2024-01-18 11:22 | MySQL Server: Performance Schema | Verified (269 days) | S3 | 8.0 | Any | Any | explain output "Using temporary" but query dosent create temporary table |
71204 | 2013-12-22 15:42 | 2014-01-06 13:43 | MySQL Server: Performance Schema | Verified (3946 days) | S3 | 5.6.14, 5.6.16 | Any | Any | Timing for stages in P_S is different from what SHOW PROFILE reports |
71293 | 2014-01-04 18:35 | 2021-08-08 20:45 | MySQL Server: Performance Schema | Verified (3933 days) | S3 | 5.6 | Any | Any | Manual page for P_S.FILE_INSTANCES table does not explain EVENT_NAME values |
84609 | 2017-01-23 12:21 | 2017-06-27 7:43 | MySQL Server: Performance Schema | Verified (2820 days) | S3 | 5.7, 8.0, 5.7.17 | Any | Any | Lock information in TABLE_HANDLES misplaced |
96196 | 2019-07-13 7:17 | 2019-07-16 10:28 | MySQL Server: Performance Schema | Verified (1917 days) | S3 | 5.7.26, 8.0.16 | Any | Any | performance_schema_accounts_size and p_s_hosts_size limited by 16384 |
109452 | 2022-12-21 10:22 | 2022-12-21 12:12 | MySQL Server: Performance Schema | Verified (662 days) | S3 | 8.0.31 | Any | Any | Misleading error message on storage engine failing to collect its log info |
62568 | 2011-09-28 21:54 | 2011-11-09 16:34 | MySQL Server: Partitions | Verified (4763 days) | S3 | 5.5.12, 5.5.17 | Any | Any | Partition options not supported by storage engine are silently ignored |
70303 | 2013-09-11 19:24 | 2015-11-19 15:57 | MySQL Server: Partitions | Analyzing (4050 days) | S2 | 5.5.32 | MacOS | Any | main.partition sporadically fails when using the embedded server |
71630 | 2014-02-07 19:36 | 2014-02-08 20:57 | MySQL Server: Partitions | Verified (3901 days) | S3 | 5.1, 5.5, 5.6, 5.7 | Any | Any | Assertion `! is_set()' fails on UPDATE on a partitioned table with subquery |
84370 | 2016-12-29 13:42 | 2016-12-30 4:14 | MySQL Server: Partitions | Verified (2844 days) | S2 | 5.7.17 | Any | Any | It is possible to enable compression for partitioned table in general tablespace |
88916 | 2017-12-14 10:59 | 2021-01-11 3:59 | MySQL Server: Partitions | Verified (2495 days) | S3 | 5.6, 5.7, 5.6.38, 5.7.20 | Any | Any | Assertion `table->s->db_create_options == part_table->s->db_create_options' |
53819 | 2010-05-19 17:42 | 2022-12-27 1:25 | MySQL Server: Partitions | Analyzing (5261 days) | S3 | mysql-next-mr-wl3561 | Any | Any | assert in my_seek, concurrent workload |
84362 | 2016-12-28 17:11 | 2016-12-28 17:52 | MySQL Server: Partitions | Verified (2846 days) | S3 | 5.6, 5.7,8.0 | Any | Any | PARTITION BY LIST COLUMNS allows unsupported data types |
112181 | 2023-08-25 9:04 | 2023-09-18 8:39 | MySQL Server: Partitions | Verified (412 days) | S3 | 8.0 | Any | Any | TIMESTAMP(N) partitions doesn't prune for inequity |
112738 | 2023-10-16 9:26 | 2023-10-16 9:35 | MySQL Server: Partitions | Verified (363 days) | S1 | 8.0.30, 8.0.34 | Any | Any | can't truncate partition when partition_id exceed INT_MAX |
88639 | 2017-11-24 7:05 | 2017-11-27 9:48 | MySQL Server: Partitions | Verified (2512 days) | S1 | 5.6.38/5.7/8.0 | Any | Any | ERROR 1030 (HY000): Got error -1 from storage engine on PARTITION CREATE TABLE |
96895 | 2019-09-17 5:45 | 2019-09-19 5:10 | MySQL Server: Partitions | Verified (1853 days) | S3 | 5.7.26 | Windows | Any | Test main.partition_rename_longfilename fails on Samba storage |
60298 | 2011-03-01 22:33 | 2021-06-02 2:23 | MySQL Server: Partitions | Verified (4973 days) | S3 | 5.1+ | Any | Any | Geometry columns/spatial indexes unsupported in partitioned tables |
63083 | 2011-11-03 0:47 | 2011-11-29 16:19 | MySQL Server: Partitions | Verified (4702 days) | S2 | 5.x | Any | Any | ERROR 1469 (HY000): The mix of handlers in the partitions is not permitted in th |
46300 | 2009-07-20 9:07 | 2011-02-16 23:44 | MySQL Server: Partitions | Verified (5167 days) | S3 | 5.1.36-log, 5.1.46, 5.5.3 | HP/UX (11.23 PA 2.0, LINUX F12) | Any | Partitioned table: LOAD DATA INFILE "stalls" - HPUX 11.23 PA RISC |
67241 | 2012-10-15 20:03 | 2012-10-17 13:41 | MySQL Server: Partitions | Verified (4379 days) | S3 | 5.5 | Linux | Any | Partition pruning not working utf8 / skip-character-set-client-handshake options |
105075 | 2021-09-29 13:00 | 2021-09-29 13:35 | MySQL Server: Partitions | Verified (1110 days) | S3 | 5.7 | Any | Any | part field of unsigned bigint type |
116222 | 2024-09-25 10:56 | 2024-09-25 11:14 | MySQL Server: Parser | Verified (18 days) | S3 | 9.0.1, 8.4.2, 8.0.39 | Any | Any | mysql_parser_parse() gets different digest for query with trailing semicolon |
34564 | 2008-02-14 19:20 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (6047 days) | S3 | 5.1.22-rc-log | Any | Any | CAST does not accept varchar type |
52421 | 2010-03-28 22:31 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5312 days) | S3 | 5.1.32, 5.1.43 | Any | Any | DECIMAL type given with decimals doesn't return an error. |
53426 | 2010-05-05 8:01 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5275 days) | S3 | 5.1.44 | Any | Any | Not able to parse a ISO9075 compliant 3-table join |
62696 | 2011-10-12 9:36 | 2011-11-09 15:38 | MySQL Server: Parser | Verified (4750 days) | S3 | 5.5.17, 5.6.4-m5 | Any | Any | Using a numeric operator on a TIME column should return an error or warning |
68676 | 2013-03-14 21:25 | 2021-08-10 16:42 | MySQL Server: Parser | Verified (4226 days) | S3 | 5.5.30, 5.0.97, 5.1.70, 5.5.32, 5.6.12, 5.7.2 | Linux | Any | Escaping backslash in identifier name |
83608 | 2016-10-29 10:51 | 2016-10-29 12:15 | MySQL Server: Parser | Verified (2906 days) | S3 | 5.5, 5.6, 5.7 | Any | Any | Assertion `m_cpp_buf <= pt r && ptr <= m_cpp_buf + m_buf_length' failed |
36633 | 2008-05-09 17:52 | 2011-02-16 23:43 | MySQL Server: Parser | Verified (5999 days) | S3 | 5.0 and up | Any | Any | MICROSECOND accepted, SQL_TSI_MICROSECOND not accepted |
46641 | 2009-08-11 0:54 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (5536 days) | S3 | 5.1.36/5.4 | Any | Any | Unclear warning message 'Warning: 1292: Truncated incorrect DOUBLE value: ___' |
80559 | 2016-02-29 14:32 | 2016-02-29 15:17 | MySQL Server: Parser | Verified (3149 days) | S3 | 5.7.11 | Any | Any | EXPLAIN CREATE TABLE .. AS SELECT .. does not work |
36140 | 2008-04-16 14:00 | 2022-12-04 20:45 | MySQL Server: Parser | Verified (6023 days) | S3 | 5.0.60 and up | Any | Any | Inconsistent synonymy of USING and TYPE for index creation |
85778 | 2017-04-04 11:39 | 2017-04-07 12:07 | MySQL Server: Packaging | Verified (2746 days) | S2 | 5.6+ | Ubuntu (ver 14.04) | Any | Custom apparmor profile not correctly replaced if user agrees to replace cnf |
70985 | 2013-11-23 8:24 | 2013-12-05 13:35 | MySQL Server: Packaging | Verified (3967 days) | S3 | 5.6.14 | Any | Any | mysql-community-server should not depend on mysql-community-client |
64666 | 2012-03-15 23:47 | 2012-03-20 7:44 | MySQL Server: Options | Verified (4594 days) | S2 | 5.1,5.5,5.6 | Any | Any | MySQL discards fractional part of the default values of system |
77976 | 2015-08-07 9:08 | 2017-09-22 14:37 | MySQL Server: Options | Verified (2578 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 |
74729 | 2014-11-07 10:19 | 2014-11-07 10:46 | MySQL Server: Options | Verified (3628 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | assertion:mode == BUF_GET_POSSIBLY_FREED || !fix_block->page.file_page_was_freed |
80668 | 2016-03-09 7:27 | 2016-03-16 2:56 | MySQL Server: Options | Verified (3134 days) | S3 | 5.7.10, 5.7.11 | CentOS | Any | InnoDB: Failing assertion: !m_fatal in in file ut0ut.cc line 938 |
74730 | 2014-11-07 10:23 | 2017-08-13 23:25 | MySQL Server: Options | Verified (3628 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion failure in fil0fil.cc line 5594 | abort sig 6 in fil/fil0fil.cc:5594 |
60703 | 2011-03-31 7:26 | 2015-11-19 16:59 | MySQL Server: Options | Verified (4856 days) | S2 | MySQL Community 5.5.9 | Windows (Windows Server 2003 Standard Edition) | Any | " --verbose --help" seems don't read the options in service name based group |
84002 | 2016-11-29 9:33 | 2016-12-02 13:52 | MySQL Server: Options | Verified (2872 days) | S3 | 5.7, 5.6.34, 5.7.16 | Any | Any | Cannot override skip-name-resolve in my.cnf |
63718 | 2011-12-11 18:45 | 2011-12-14 10:30 | MySQL Server: Options | Verified (4689 days) | S3 | 5.1.41, 5.1.61 | Any | Any | Unable to increase ft_max_word_len variable |
65711 | 2012-06-22 13:30 | 2012-06-25 6:24 | MySQL Server: Options | Verified (4496 days) | S3 | 5.5.25, 5.5.26, 5.6.5 | Any | Any | Server crashes in intern_plugin_lock on concurrent install plugin / set variable |
81442 | 2016-05-16 22:12 | 2018-01-24 16:08 | MySQL Server: Options | Verified (2454 days) | S3 | 5.7.12,5.7.15,8.0.0,8.0.4-rc | Any | Any | Unable to analyze table whilst super_read_only is enabled |
69704 | 2013-07-09 23:26 | 2013-07-10 5:36 | MySQL Server: Options | Verified (4113 days) | S3 | 5.5.32, 5.6.12 | Any | Any | Strangeness with max_binlog_stmt_cache_size Settings |
102328 | 2021-01-21 8:58 | 2021-01-21 9:54 | MySQL Server: Options | Verified (1361 days) | S3 | 5.6, 5.7, 8.0, 5.7.33, 8.0.23 | Any | Any | Range of innodb_ft_sort_pll_degree error |
49778 | 2009-12-17 19:02 | 2011-02-16 23:44 | MySQL Server: Options | Verified | S3 | 5.1 | Windows | Any | Mix of forward (/) and backward (\) slashes in show variables paths |
58106 | 2010-11-10 10:24 | 2011-02-16 23:44 | MySQL Server: Options | Verified (5086 days) | S3 | 5.1-bugteam | Any | Any | Wrong directory info in general_log_file/slow_query_log_file. |
79558 | 2015-12-08 16:29 | 2018-01-03 13:50 | MySQL Server: Options | Verified (3012 days) | S2 | 5.7.10 | Any | Any | tls_version accepts invalid arguments |
115503 | 2024-07-04 4:36 | 2024-07-05 8:24 | MySQL Server: Options | Verified (100 days) | S2 | 8.0.37 | Any | Any | The `sql_log_off` parameter is not working as expected at the session level |
72019 | 2014-03-12 12:13 | 2014-03-31 14:21 | MySQL Server: Options | Verified (3849 days) | S3 | any | Any | Any | Is my server 32 bit or 64 bit? |
81690 | 2016-06-02 13:55 | 2017-06-12 16:27 | MySQL Server: Options | Verified (3054 days) | S3 | 5.7.12 | Any | Any | executing prepared statements increases com_stmt_execute but also com_select |
48190 | 2009-10-20 14:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.1,6.0 | Any | Any | Error processing ALL subqueries on empty sets - different than JavaDB/Postgres |
53793 | 2010-05-19 9:52 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5261 days) | S3 | 6.0-codebase-bugfixing | Any | Any | "early NULL filtering" not done for outer join converted to inner join |
54056 | 2010-05-28 6:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5252 days) | S3 | 5.1.47, 5.1.48, 5.6.99 | Any | Any | Incorrect number format in output from SELECT |
59650 | 2011-01-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5014 days) | S3 | mysql-trunk | Any | Any | SELECT Does Not Return Result For "equal / Null safe equal" Operator On BIT |
60185 | 2011-02-20 15:58 | 2011-03-03 8:35 | MySQL Server: Optimizer | Verified (4984 days) | S3 | 5.0.51, 5.5.11 | Linux | Any | index DEPENDENT SUBQUERY |
64791 | 2012-03-28 20:17 | 2015-07-09 8:35 | MySQL Server: Optimizer | Verified (4581 days) | S2 | 5.1.61, 5.5 | Any | Any | Mixed String/Int values in IN list cause full table scan |
68154 | 2013-01-23 13:07 | 2016-10-09 20:45 | MySQL Server: Optimizer | Verified (4280 days) | S3 | 5.6.* | Any | Any | explain output 'Using index condition' not proper |
68919 | 2013-04-10 14:25 | 2013-04-10 14:33 | MySQL Server: Optimizer | Verified (4204 days) | S5 | 5.6.10 | Any | Any | Performance regression when DS-MRR is used for query with small limit |
74962 | 2014-11-21 13:24 | 2014-11-21 14:20 | MySQL Server: Optimizer | Verified (3614 days) | S3 | 5.5/5.6 | Any | Any | Matching in char field type is not correct |
75991 | 2015-02-21 18:12 | 2015-02-23 9:59 | MySQL Server: Optimizer | Verified (3520 days) | S3 | 5.6.14-log, 5.6.24 | Windows (Vista) | Any | writ of ALLOW_INVALID_DATES |
78651 | 2015-09-30 18:44 | 2016-10-20 12:35 | MySQL Server: Optimizer | Verified (3300 days) | S3 | 5.5.45, 5.6.26, 5.7.8, 5.5.47, 5.6.28, 5.7.10 | Any | Any | Optimizer chooses wrong index for ORDER BY |
79203 | 2015-11-10 11:59 | 2021-06-02 7:24 | MySQL Server: Optimizer | Verified (3260 days) | S3 | 5.6.25 | Debian (Debian GNU/Linux 7.8 (wheezy)) | Any | incorrect result set with block_nested_loop=on |
84416 | 2017-01-04 23:11 | 2017-01-05 11:26 | MySQL Server: Optimizer | Verified (2838 days) | S3 | 5.6 and 5.7 | Any | Any | MySQL updates 0000-00-00 00:00:00 for datetime type |
85126 | 2017-02-22 10:42 | 2017-02-28 7:19 | MySQL Server: Optimizer | Verified (2784 days) | S1 | 5.6.35 | Any | Any | Delete by range in presence of partitioning and no PK always picks wrong index |
88127 | 2017-10-17 21:45 | 2021-11-23 7:22 | MySQL Server: Optimizer | Verified (2551 days) | S3 | 5.7.19, 5.7.20 | Any | Any | Index not used for 'order by' query with utf8mb4 character set |
92297 | 2018-09-05 16:29 | 2018-11-12 21:51 | MySQL Server: Optimizer | Verified (2229 days) | S3 | 8.0.12, 5.7.23, 5.6.41, 5.5.61 | Any | Any | GROUP_CONCAT doesn't work properly with FLOAT(M,D) fields with value of M digits |
94611 | 2019-03-10 2:14 | 2019-03-10 5:32 | MySQL Server: Optimizer | Verified (2044 days) | S2 | 8.0.15-rds-dev, 8.0.15, 5.7.25,5.6.43 | CentOS | Any | Wrong results returned with "group by" |
95543 | 2019-05-27 12:37 | 2019-05-29 12:34 | MySQL Server: Optimizer | Verified | S2 | 5.7.26 | Any | Any | optimizer prefers index for order by rather than filtering - (70x slower) |
99684 | 2020-05-25 12:19 | 2022-06-08 12:02 | MySQL Server: Optimizer | Verified (1599 days) | S3 | 5.6, 5.7, 8.0 | Any | Any | incorrect determination of big test |
99994 | 2020-06-26 7:57 | 2020-06-26 13:08 | MySQL Server: Optimizer | Verified (1570 days) | S5 | 8.0 | Any | Any | Index range scan is chosen where table scan takes 40% less time |
101459 | 2020-11-04 13:05 | 2022-02-28 15:34 | MySQL Server: Optimizer | Verified (974 days) | S5 | 5.6.50,5.7.32 | Any | Any | With more than one value in IN() clause, query skip index use. |
101796 | 2020-11-30 8:52 | 2020-11-30 8:59 | MySQL Server: Optimizer | Verified (1413 days) | S2 | 5.6.34, 5.6.50, 5.7.32 | Any | Any | Incorrect query result for index_subquery type IN subquery |
102160 | 2021-01-06 8:31 | 2021-01-06 9:01 | MySQL Server: Optimizer | Verified (1376 days) | S3 | 8.0.22, 5.7.32 | CentOS | Any | Simple SELECT query returns different results when an index exists or not |
102681 | 2021-02-22 5:29 | 2021-02-22 6:05 | MySQL Server: Optimizer | Verified (1329 days) | S3 | 8.0,5.7.33, 8.0.23 | Any | Any | result of "datetime_val not between NULL and NULL" is unexpected |
104083 | 2021-06-22 8:09 | 2022-09-22 3:56 | MySQL Server: Optimizer | Verified (1209 days) | S5 | 8.0.25 | Any | Any | MySQL optimizer chooses the wrong index due to 'range_uses_more_keyparts' |
108192 | 2022-08-18 13:16 | 2022-08-19 9:06 | MySQL Server: Optimizer | Verified (787 days) | S2 | 8.0.23, 8.0.30 | Any | Any | Different results return when executing the same query with different plans |
109449 | 2022-12-21 9:48 | 2023-01-03 8:04 | MySQL Server: Optimizer | Verified (662 days) | S3 | 8.0.26, 8.0.31 | Any | Any | functional index could produce wrong result |
110015 | 2023-02-10 3:06 | 2023-11-20 11:24 | MySQL Server: Optimizer | Verified (608 days) | S5 | 8.0.32 | Windows (11) | x86 | Multi-valued index on JSON array is not used when used in a join |
110406 | 2023-03-17 4:58 | 2023-03-20 14:08 | MySQL Server: Optimizer | Verified (573 days) | S3 | 8.0 | Any | Any | Storing rows with null in join key in hash table for outer join is useless |
110998 | 2023-05-11 15:33 | 2023-12-01 6:49 | MySQL Server: Optimizer | Verified (515 days) | S5 | 8.0.20+, 8.0.33 | Linux | Any | Performance regression with SELECT query when sorting on limited fields |
111479 | 2023-06-19 4:24 | 2023-06-19 11:42 | MySQL Server: Optimizer | Verified (482 days) | S3 | 5.7.42 | Any | Any | Optimizer estimated rows is always equal to 1 when using spatial index. |
112377 | 2023-09-18 23:01 | 2023-09-19 12:24 | MySQL Server: Optimizer | Verified (390 days) | S3 | 8.0 | Any | Any | Assert in AccessPath::index_merge() |
112912 | 2023-11-01 8:45 | 2023-11-01 14:47 | MySQL Server: Optimizer | Verified (347 days) | S3 | 8.0 | Any | Any | Parsing a string To BIT type got a wrong result |
114581 | 2024-04-08 11:24 | 2024-04-08 12:37 | MySQL Server: Optimizer | Verified (188 days) | S2 | 8.0.36 | Any | Any | Constant-Folding optimization negative constant truncate gives wrong operator |
115840 | 2024-08-15 2:30 | 2024-08-26 7:58 | MySQL Server: Optimizer | Verified (59 days) | S2 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Contribute by Tencent:Incorrect Cost Display for Join with Materialized Subquery |
116163 | 2024-09-19 14:08 | 2024-09-24 12:36 | MySQL Server: Optimizer | Verified (19 days) | S2 | 9.0 | Any | Any | COALESCE(BIT), IF(BIT) return a wrong result |
115843 | 2024-08-15 8:26 | 2024-08-21 8:04 | MySQL Server: Optimizer | Verified (53 days) | S2 | 8.0.32, 8.0.39 | Any | Any | The incorrect calculation of 'select_limit' led to an incorrect index selection |
11948 | 2005-07-14 18:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (7011 days) | S3 | 5.0 | Any | Any | MyISAM only, nested JOIN Views, dramatic performance loss |
30342 | 2007-08-09 18:52 | 2015-10-07 14:54 | MySQL Server: Optimizer | Verified (3294 days) | S5 | 5.0.37, 5.6.17 | Any | Any | Equality propagation can make optimization much slower |
72294 | 2014-04-09 17:28 | 2014-04-10 6:24 | MySQL Server: Optimizer | Verified (3839 days) | S3 | 5.5-debug, 5.6-debug | Any | Any | Assertion `0' fails on killing INSERT .. SELECT into a FEDERATED table |
72814 | 2014-05-30 9:31 | 2014-07-18 18:56 | MySQL Server: Optimizer | Verified (3786 days) | S3 | 5.6.17 | Any | Any | Assertion `!(ordered_index_usage == ordered_index_void && ... fails |
74490 | 2014-10-22 2:08 | 2014-10-22 6:57 | MySQL Server: Optimizer | Verified (3644 days) | S3 | 5.6.20-debug, 5.6.22 | Linux (CentOS 7) | Any | Assertion `table->key_read == 0' failed | sig 6 in close_open_tables |
76604 | 2015-04-07 4:29 | 2015-04-07 6:15 | MySQL Server: Optimizer | Verified (3477 days) | S3 | 5.6.23, 5.6.24, 5.6.25, 5.7.8 | Linux (CentOS 7) | Any | Assertion `length > 0 && keyparts != 0' failed in create_ref_for_key |
82363 | 2016-07-27 19:28 | 2016-07-28 8:11 | MySQL Server: Optimizer | Verified (2999 days) | S3 | 5.7 and every other | Any | Any | impossible const condition still followed in a JOIN |
84858 | 2017-02-07 13:09 | 2017-02-09 6:34 | MySQL Server: Optimizer | Verified (2803 days) | S3 | 5.6, 5.7, 5.6.35 | Any | Any | Time is spent at "statistics" stage for primary key lookups |
105586 | 2021-11-16 8:51 | 2021-11-16 9:19 | MySQL Server: Optimizer | Verified (1062 days) | S2 | 8.0 | Any | Any | Uninitialized value in storage/innobase/btr/btr0bulk.cc |
111067 | 2023-05-18 8:05 | 2023-05-19 12:55 | MySQL Server: Optimizer | Verified (514 days) | S2 | 8.0.25, 8.0.33 | Any | Any | Query result error |
8036 | 2005-01-20 10:12 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (7197 days) | S3 | 4.0.18, 4.1.10, 5.1.52 | FreeBSD (Free BSD 4.5, Linux) | Any | Bad optimization of ORDER BY ... LIMIT 1 if one table is MyISAM, another InnoDB |
8749 | 2005-02-23 21:08 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5492 days) | S3 | 4.1.10, 5.0.67 | Any (*) | Any | EXPLAIN report different "type" w and w/o USE INDEX(...) for the same used key |
25764 | 2007-01-22 20:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5740 days) | S3 | 5.0.36-BK, 6.0.8-bzr | Linux (Linux, Mac OS X) | Any | Query Cost Estimate seems to only cover a part of subqueries, not full query. |
28554 | 2007-05-21 9:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5623 days) | S3 | 4.1.22, 5.0.42-BK | Any | Any | Optimizer wrongly prefers index for (col = value) over (PK <= value) |
29421 | 2007-06-28 13:43 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6317 days) | S2 | 5.1.14-beta/5.0 | Any | Any | MySQL allows mixing of GROUP columns with no GROUP columns in complex terms |
36300 | 2008-04-23 17:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5388 days) | S3 | 4.1.26, 5.0.32, 5.0+, 5.1.43-bzr, 6.0.14-bzr | Linux | Any | min() and max() functions returns NULL when using NOT + BETWEEN in where |
43720 | 2009-03-18 6:00 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5688 days) | S3 | 6.0.11, 5.0, 5.1 bzr | Any | Any | MyISAM & Maria gives wrong results with range access on bit type |
78407 | 2015-09-11 12:45 | 2022-04-29 5:41 | MySQL Server: Optimizer | Verified (898 days) | S5 | 7.4.6/5.6.24, 5.7, 8.0 | Linux | Any | wrong index being used in subqueries? |
83323 | 2016-10-10 18:02 | 2018-04-13 12:41 | MySQL Server: Optimizer | Verified (2729 days) | S3 | 5.7, 5.6, 8.0.1 | Any | Any | Optimizer chooses wrong plan when joining 2 tables |
96958 | 2019-09-20 21:42 | 2024-04-30 9:09 | MySQL Server: Optimizer | Verified (1848 days) | S3 | 8.0 | Any | Any | MySQL optimizer wrongly chooses to use a bigger and inefficient index for query |
107629 | 2022-06-22 8:41 | 2022-06-22 10:06 | MySQL Server: Optimizer | Verified (844 days) | S3 | 8.0.29 | Any | Any | Incorrect result when using index and materialization-lookup |
101794 | 2020-11-30 3:46 | 2020-12-02 4:15 | MySQL Server: Optimizer | Verified (1412 days) | S3 | 5.7, 5.7.32, 8.0.22 | Linux | Any | Query failing with "ERROR 1030 (HY000): Got error 1 from storage engine" |
109173 | 2022-11-23 7:51 | 2022-11-24 12:16 | MySQL Server: Optimizer | Verified (689 days) | S5 | .31, 8.0.31 | Any | Any | Contribution: Offset pushdown to InnoDB and removal of redundant conditions |
19195 | 2006-04-19 12:09 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5497 days) | S3 | 5.0.27-BK, 5.0.21-BK, 5.0.19 | Linux (Linux) | Any | Optimizer does not use proper index for join |
43342 | 2009-03-03 21:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5703 days) | S2 | 5.1, 6.0 | Any | Any | FORCE INDEX hint does not differentiate between ORDER BY and GROUP BY |
44549 | 2009-04-29 17:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S3 | 5.0.80, 5.1.34 | Any | Any | optimizer incorrectly chooses table scan and filesort over index |
49276 | 2009-12-01 17:03 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5430 days) | S5 | 5.0.85-community-log, 5.0.89, 5.1.42 | Linux | Any | Optimization for IN (on InnoDB tables) depends on number of set elements |
52170 | 2010-03-18 9:57 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5319 days) | S5 | 5.1.44, mysql-next-mt | Linux (fc12) | Any | innodb query optimizer fails (null possible_keys) with multicolumn key |
58928 | 2010-12-14 20:58 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5052 days) | S3 | 5.1-bugteam | Any | Any | "not exists" optimization not applied if relevant table is not single inner one |
61551 | 2011-06-17 12:26 | 2011-06-18 8:34 | MySQL Server: Optimizer | Verified (4867 days) | S3 | 5.1.56 | Any | Any | Loose index scan is not used for select COUNT(distinct a) |
64036 | 2012-01-15 15:51 | 2012-01-15 19:07 | MySQL Server: Optimizer | Verified (4655 days) | S3 | Any | Any | Use non-materializing loose-scan-merge for certain subqueries in FROM with LIMIT | |
71191 | 2013-12-20 15:30 | 2013-12-20 20:20 | MySQL Server: Optimizer | Verified (3950 days) | S3 | 5.5.33 | Any | Any | Loose index scan is used even though full table scan/tight index scan is faster |
82725 | 2016-08-25 15:55 | 2016-09-14 6:28 | MySQL Server: Optimizer | Verified (2951 days) | S5 | 5.7.14, 5.7.15 | CentOS (Linux rda-db-rep.ucar.edu 3.10.0-327.28.2.el7.x86_64 #1 SMP Wed Aug 3 11:11:39 UTC 2016 x86_64 x86_6) | Any | Extremely slow query when optimizer_switch='derived_merge=ON' |
83248 | 2016-10-03 15:57 | 2023-02-22 1:40 | MySQL Server: Optimizer | Verified (2932 days) | S3 | 8.0.0, 5.7.15 | Any | Any | Partition pruning is not working with LEFT JOIN |
83856 | 2016-11-17 4:19 | 2019-11-15 17:31 | MySQL Server: Optimizer | Verified (2856 days) | S3 | 5.7.13,5.7.16 | CentOS | Any | Index ref not used for multi-column IN - type or collation conversion warning |
93845 | 2019-01-07 21:55 | 2021-08-23 12:23 | MySQL Server: Optimizer | Verified (2104 days) | S2 | 5.7,8.0.11,8.0.13 | Any | Any | Optimizer choose wrong index, sorting index instead of filtering index |
100852 | 2020-09-15 9:40 | 2022-11-26 0:29 | MySQL Server: Optimizer | Verified (1489 days) | S3 | 8.0.20, 8.0.21 | Windows | Any | ANY_VALUE gives unexpected type with GROUP BY |
108863 | 2022-10-24 16:40 | 2024-03-15 8:49 | MySQL Server: Optimizer | Verified | S5 | 8.0.31 | Any | Any | different index picked when row is not found, marginally slower |
112802 | 2023-10-23 8:23 | 2023-10-27 9:46 | MySQL Server: Optimizer | Verified (356 days) | S3 | 8.1.0, 8.0.34 | Any | Any | Inconsistent results when using INDEX |
112911 | 2023-11-01 8:21 | 2023-11-01 8:56 | MySQL Server: Optimizer | Verified (347 days) | S2 | 8.1.0, 8.0.35 | Any | Any | Inconsistent results when using PRIMARY and DUPSWEEDOUT |
60023 | 2011-02-08 21:45 | 2014-05-22 12:13 | MySQL Server: Optimizer | Verified | S5 | 5.5.8 , 5.1.51 | Any | Any | No Loose Index Scan for GROUP BY / DISTINCT on InnoDB partitioned table |
72996 | 2014-06-13 6:08 | 2015-04-10 7:07 | MySQL Server: Optimizer | Verified (3474 days) | S3 | 5.6.16, 5.6.19, 5.6.18,5.6.23 | Any | Any | desc error on convert |
80390 | 2016-02-16 10:14 | 2022-10-04 15:10 | MySQL Server: Optimizer | Verified (3162 days) | S5 | 5.6.30 | Any | Any | Clustered primary key included in index merge may cause higher execution times |
98771 | 2020-02-28 6:29 | 2020-03-02 18:39 | MySQL Server: Optimizer | Verified (1689 days) | S2 | 5.7, 5.7.29 | Any | Any | Performance impact while selecting data from a JSON type column |
58737 | 2010-12-05 7:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5060 days) | S3 | 5.1.53, 5.1.54 | Windows (7) | Any | nested query fails to execute |
38550 | 2008-08-04 21:47 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5841 days) | S5 | 5.0.60, 5.1 | Any | Any | multiple optimizer bugs for queries with references from preceding table |
26284 | 2007-02-12 12:32 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6181 days) | S3 | 5.0.bk | Linux (Linux) | Any | bug #26273 / optimize, not executed for index, if datafile is gap-free |
50388 | 2010-01-16 4:13 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified | S5 | 5.1.41,5.1.42, 5.1.43-bzr | Any | Any | partition pruning not working with some right joins |
59187 | 2010-12-27 15:31 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5039 days) | S2 | 5.1.55, 5.6.2-m5 | Any | Any | Wrong result with NULL NOT IN subquery |
67980 | 2012-12-27 14:54 | 2013-01-19 10:52 | MySQL Server: Optimizer | Verified (4285 days) | S3 | 5.5.28 | Any | Any | MySQL not utilising full index because of possible bad cardinality stats |
71171 | 2013-12-18 10:40 | 2014-02-04 14:40 | MySQL Server: Optimizer | Verified (3904 days) | S2 | 5.6.14 | Linux (Debian 7.1) | Any | Optimizer executes inperformant subquery first |
61936 | 2011-07-21 6:27 | 2011-07-31 15:28 | MySQL Server: Optimizer | Verified (4832 days) | S2 | 5.1.48, 5.5.13, 5.5.16 | Linux (x86_64) | Any | STRAIGHT_JOIN has no effect on query with subquery in FROM clause |
71199 | 2013-12-21 18:16 | 2014-01-28 17:45 | MySQL Server: Optimizer | Verified (3947 days) | S3 | 5.6.14, 5.6.15, 5.5.35 | Any | Any | Optimizer's estimated number of rows is 2 times wrong for (loose?) index scans |
71330 | 2014-01-09 15:30 | 2018-01-26 5:20 | MySQL Server: Optimizer | Verified (3930 days) | S3 | 5.7.3, 5.6.15 | Any | Any | Item_insert_value type should be ITEM_INSERT_VALUE |
89182 | 2018-01-11 9:51 | 2018-01-11 13:10 | MySQL Server: Optimizer | Verified (2467 days) | S3 | 5.6.38, 5.7.20, 8.0.3 | Any | Any | Optimizer unable to ignore index part entering less optimal query plan |
18688 | 2006-03-31 14:07 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (6246 days) | S3 | 4.0, 4.1, 5.0 | Linux (linux) | Any | non-optimal plan for SELECT |
34078 | 2008-01-26 14:19 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (6078 days) | S3 | 4.1,5.0,5.1,6.0-BK | Any (Linux) | Any | ref access is not used for varchar column |
37902 | 2008-07-06 15:14 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5922 days) | S3 | 5.0.45, 5.0.68 | MacOS | Any | Bug (2) in the query optimizer (explain) |
15907 | 2005-12-21 15:23 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5416 days) | S5 | 5.0.19-BK, 5.0.13, 6.0.14-bzr | Linux (Linux) | Any | Binary comparison ignores indexes |
37053 | 2008-05-29 4:11 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5871 days) | S3 | 4.1, 5.0, 5.1,6.0.5 | Any (Linux, Solaris) | Any | Optimizer unnecessarily uses temporary and filesort with ORDER BY |
41220 | 2008-12-04 9:59 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5535 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 |
43052 | 2009-02-20 9:49 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5714 days) | S3 | 5.1.30-community, 4.1, 5.0, 5.1, 6.0 bzr | Any (MS Windows XP, Linux) | Any | not optimalised (sub)query, = versus IN |
46011 | 2009-07-07 14:05 | 2020-05-03 20:45 | MySQL Server: Optimizer | Verified (5115 days) | S3 | 5.1-bugteam | Any | Any | Regression after applying fix for bug #45828 |
46475 | 2009-07-30 11:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5553 days) | S3 | 5.1,5.4 | Any | Any | Different optimizations chosen for exactly equivalent queries |
47330 | 2009-09-15 15:39 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5499 days) | S5 | 5.0.77, 5.1.34, 5.1.37 | Linux (Debian x64) | Any | Slow query with left join and having. |
47884 | 2009-10-07 3:24 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5371 days) | S2 | 5.1.39, 5.1.44, 5.5.99 | Linux (Linux web2 2.6.18-92.1.18.el5.028stab060.8 #1 SMP Mon Feb 9 21:44:50 MSK 2009 x86_64) | Any | MySQL 5.1.39 failed to use index |
49504 | 2009-12-07 12:54 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5424 days) | S3 | 5.1+ | Any | Any | Inconsistency in handling range predicates with NULL constants |
52030 | 2010-03-13 12:35 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5325 days) | S2 | 5.1.44 | Any | Any | WHERE clause with != primary key check slows a query from 0.06 sec to 4 min |
56165 | 2010-08-21 8:12 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (5165 days) | S3 | 5.0.not_sure, 5.0, 5.1, 5.6.99 bzr | Any | Any | Bad Optimization |
70684 | 2013-10-22 8:13 | 2013-10-22 11:35 | MySQL Server: Optimizer | Verified (4009 days) | S3 | 5.5.33, 5.6.14 | Any | Any | HAVING referring to subquery results in WARNING 1292 |
70886 | 2013-11-12 10:42 | 2013-11-12 11:02 | MySQL Server: Optimizer | Verified (3988 days) | S3 | 5.5.32, 5.6 | Any | Any | MIN/MAX optimizer doesn't take into account type conversions |
71140 | 2013-12-13 9:16 | 2015-07-31 8:59 | MySQL Server: Optimizer | Verified (3362 days) | S2 | 5.1, 5.5, 5.6.15, 5.7.7 | Any | Any | Optimizer does NOT use range checks in typical self-join for InnoDB tables |
72646 | 2014-05-14 9:40 | 2014-05-14 12:17 | MySQL Server: Optimizer | Verified (3805 days) | S3 | 5.5 5.6, 5.6.19 | Any | Any | A strange result from explain query |
72745 | 2014-05-26 4:28 | 2014-05-26 5:48 | MySQL Server: Optimizer | Verified (3793 days) | S2 | 5.5.37, 5.5.38 | Any | Any | Wrong Results When Using Intersect |
74049 | 2014-09-24 8:01 | 2014-09-24 10:01 | MySQL Server: Optimizer | Verified (3672 days) | S3 | 5.6.19-67.0, 5.6.22 | Any | Any | Update query use filesort instead of index |
74256 | 2014-10-07 22:43 | 2015-11-02 6:19 | MySQL Server: Optimizer | Verified (3560 days) | S2 | 5.6.19, 5.6.22 | Any | Any | index_extensions used incorrectly in select cause performance regression |
75967 | 2015-02-19 12:45 | 2015-02-20 8:06 | MySQL Server: Optimizer | Verified (3523 days) | S3 | 5.6, 5.7, 5.6.24 | Any | Any | Wrong result (extra rows) with SQ and comparison to NULL, materialization=off |
76679 | 2015-04-13 15:48 | 2017-02-01 14:28 | MySQL Server: Optimizer | Verified (3470 days) | S3 | 5.6, 5.6.24, 5.6.25, 5.7.8 | Any | Any | EXPLAIN incorrectly shows Distinct for tables using join buffer |
76755 | 2015-04-20 12:35 | 2015-04-25 13:23 | MySQL Server: Optimizer | Verified (3459 days) | S2 | 5.6.24 | Any | Any | Query execution plan / indexes problem |
80067 | 2016-01-20 10:50 | 2020-06-17 23:13 | MySQL Server: Optimizer | Verified (3189 days) | S3 | 5.6.28, 5.7.10 | Any | Any | Index on BIT column is NOT used when column name only is used in WHERE clause |
87670 | 2017-09-05 9:32 | 2017-09-06 7:54 | MySQL Server: Optimizer | Verified (2594 days) | S3 | 5.7.18, 5.6.37, 5.7.19 | Any | Any | Force index for group by is not always honored |
88181 | 2017-10-23 5:30 | 2018-06-11 19:55 | MySQL Server: Optimizer | Verified (2547 days) | S3 | 5.7.20 | Any | Any | Another example of optimizer choosing ref over range when range is faster |
89367 | 2018-01-24 2:52 | 2018-01-24 9:04 | MySQL Server: Optimizer | Verified (2454 days) | S3 | 5.7.20, 5.7.21 | Any | Any | Storing result in a variable(UDV) causes query on a view to use derived tables |
93360 | 2018-11-27 9:41 | 2018-12-12 14:48 | MySQL Server: Optimizer | Verified (2132 days) | S5 | 5.6.16,5.7.23 | Linux | x86 | mysterious optimizer behavior |
93491 | 2018-12-05 17:40 | 2018-12-06 5:39 | MySQL Server: Optimizer | Verified (2138 days) | S3 | 8.0.13, 5.7.24, 5.6.42 | Any | Any | Optimizer does not correctly consider attached conditions in planning |
96379 | 2019-07-31 5:55 | 2019-08-02 7:03 | MySQL Server: Optimizer | Verified (1900 days) | S3 | 8.0.16, 8.0.17, 5.7.27 | Windows | x86 | First query successfull, second - ERROR 1270 (HY000): Illegal mix of collations |
98055 | 2019-12-23 11:37 | 2020-01-24 13:03 | MySQL Server: Optimizer | Verified (1725 days) | S3 | 5.7 | Red Hat (amezon RDS) | Any | MySQL Optimizer Bug not picking right index |
98770 | 2020-02-28 4:02 | 2020-03-03 15:05 | MySQL Server: Optimizer | Verified (1685 days) | S5 | 8.0.19 | Any | Any | Non-covering full index scan is always preferred over table scan for GROUP BY |
99995 | 2020-06-26 7:57 | 2020-06-26 13:13 | MySQL Server: Optimizer | Verified (1570 days) | S3 | 8.0 | Any | Any | Histogram is not used for filtering estimate when index is disabled |
101059 | 2020-10-06 2:47 | 2020-10-06 5:26 | MySQL Server: Optimizer | Verified (1468 days) | S3 | 8.0.19, 8.0.21, 5.7.31, 5.6.49 | Any | x86 | Query result inconsistent for the year type in NOT IN expression |
101665 | 2020-11-18 17:58 | 2020-11-19 14:02 | MySQL Server: Optimizer | Verified (1424 days) | S3 | 8.0.22 | Linux | x86 | mysql use incorrect index during executing "select" query |
102686 | 2021-02-22 12:50 | 2021-02-24 16:01 | MySQL Server: Optimizer | Verified (1327 days) | S5 | 8.0 | Any | Any | The query plan changed cause query too long |
103922 | 2021-06-07 7:12 | 2021-06-07 7:37 | MySQL Server: Optimizer | Verified (1224 days) | S3 | 5.7.32, 8.0.22, 5.7.34, 8.0.25 | Any | Any | Wrong `between` result for datetime/date/timestamp type |
104756 | 2021-08-28 7:52 | 2021-10-09 7:02 | MySQL Server: Optimizer | Verified (1100 days) | S3 | 5.7.35 | Any | Any | Incorrect query results after index creation |
105068 | 2021-09-28 22:06 | 2021-10-04 12:07 | MySQL Server: Optimizer | Verified (1109 days) | S3 | 5.7 | Any | Any | Type ref instead of range after reconsidering_access_paths_for_index_ordering. |
105289 | 2021-10-21 14:54 | 2021-10-25 12:20 | MySQL Server: Optimizer | Verified (1087 days) | S3 | 5.7 | Any | Any | Optimizer choose index scan but not index range for query with range condition |
105857 | 2021-12-10 7:39 | 2022-11-16 12:55 | MySQL Server: Optimizer | Verified (1006 days) | S3 | 8.0.23, 8.0.27 | Linux | Any | ResultSetMetaData return different column type in two calls |
106003 | 2021-12-29 20:06 | 2022-11-29 7:53 | MySQL Server: Optimizer | Verified (1018 days) | S3 | 8.0.27/5.7 | Any | Any | MySQL does not use indexes correctly for backwards ORDER BY conditions |
106580 | 2022-02-26 9:41 | 2022-03-02 14:56 | MySQL Server: Optimizer | Verified (956 days) | S3 | 8.0 | Any | Any | Multi-Valued Indexes only takes into account a portion of a whole data. |
106754 | 2022-03-17 7:06 | 2022-03-21 13:52 | MySQL Server: Optimizer | Verified (941 days) | S5 | 5.7, 8.0, 5.7.37, 8.0.28 | Any | Any | Index-loose scan doesn't work for signle table partition Query |
107576 | 2022-06-16 7:34 | 2022-06-16 9:24 | MySQL Server: Optimizer | Verified (850 days) | S3 | 8.0.29 | Ubuntu (ubuntu 20.04) | x86 | Incorrect result when comparing 0 and -0 when using materialization-lookup |
108116 | 2022-08-11 8:21 | 2024-09-05 3:40 | MySQL Server: Optimizer | Verified (794 days) | S3 | 8.0.29, 8.0.30, 5.7.39 | Any (rhel-7.4) | Any (x86-64) | SQL queries with range of Item_row are not optimized |
111367 | 2023-06-12 15:36 | 2023-08-04 15:11 | MySQL Server: Optimizer | Verified (436 days) | S5 | 8.0 | Any | Any | OFFSET 99 LIMIT 1 on a compound PK takes ages to execute. |
111409 | 2023-06-14 3:40 | 2023-06-14 13:31 | MySQL Server: Optimizer | Verified (487 days) | S3 | 8.0 | Any | Any | Incorrect result when select time col use "WHERE IN (NULL,'xx:xx:xx.xxxxxx')" |
111991 | 2023-08-08 3:25 | 2023-08-10 5:53 | MySQL Server: Optimizer | Verified (430 days) | S2 | 8.0.32,8.1.0 | Any | Any | index merge sometimes return incorrect result |
112212 | 2023-08-29 16:01 | 2023-08-30 7:42 | MySQL Server: Optimizer | Verified (410 days) | S3 | 8.0.34 | Any | Any | Subquery to derived result mismatch(HASH JOIN/BNL JOIN result mismatch) |
112816 | 2023-10-24 16:15 | 2023-12-13 12:00 | MySQL Server: Optimizer | Verified (345 days) | S2 | 8.0, 8.1 | Any | Any | Inconsistent results when JOINed in different order |
112985 | 2023-11-07 8:33 | 2023-11-08 10:54 | MySQL Server: Optimizer | Verified (341 days) | S3 | 8.0, 8.1, 8.2 | Any | Any | Inconsistent results when switching hash join optimization |
113059 | 2023-11-13 8:29 | 2023-11-13 9:51 | MySQL Server: Optimizer | Verified (335 days) | S2 | 8.2.0 | Any | Any | Inconsistent results when using DUPSWEEDOUT |
113316 | 2023-12-04 3:32 | 2023-12-04 7:21 | MySQL Server: Optimizer | Verified (314 days) | S3 | 8.0.35, 8.1.0, 8.2.0 | Any | Any | When the bit type has an index, the query result is incorrect. |
114719 | 2024-04-21 14:31 | 2024-04-22 7:46 | MySQL Server: Optimizer | Verified (174 days) | S1 | 8.0.36 | Any | Any | Incorrect results caused by different access types for an index |
114795 | 2024-04-26 10:05 | 2024-04-29 9:56 | MySQL Server: Optimizer | Verified (170 days) | S3 | 8.0 | Any | Any | Arithmetic overflow when calculating the length of used fields involving blob |
115597 | 2024-07-15 16:46 | 2024-07-16 13:44 | MySQL Server: Optimizer | Verified (90 days) | S2 | 9.0 | Any | Any | Window function applied to BIT column produces non-BIT type |
115679 | 2024-07-24 9:04 | 2024-07-24 9:46 | MySQL Server: Optimizer | Verified (81 days) | S5 | 8.0.37 | Any | Any | Block Nested-Loops Join can sometimes slow down the query |
41406 | 2008-12-11 17:28 | 2021-05-02 20:45 | MySQL Cluster: NDB API | Verified | S2 | mysql-5.1-telco-6.3 | Any | Any | Events segfault with NDBAPI when watching a primary key |
58247 | 2010-11-17 8:30 | 2021-05-02 20:45 | MySQL Cluster: NDB API | Verified | S3 | mysql-5.1-telco-7.0 | Any | Any | ndb_mgm_bindaddress produces errors on stdout; errno/errmsg incorrect |
42818 | 2009-02-13 9:15 | 2021-05-02 20:45 | MySQL Cluster: NDB API | Verified (5721 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | Batching to much kills data nodes with temporary error |
42047 | 2009-01-12 11:29 | 2021-05-02 20:45 | MySQL Cluster: NDB API | Verified (5747 days) | S3 | mysql-5.1-telco-6.2 | Any | Any | NDBAPI : Too large BIT column causes node failure on insert |
25891 | 2007-01-27 14:17 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (6122 days) | S3 | 5.0.36-BK, 5.0.27 | Linux (Linux) | Any | Creation of temporary table with key causing error 124 |
46714 | 2009-08-14 10:51 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (5539 days) | S3 | azalea (5.4) | Any | Any | MyISAM storage engine pollutes the diagnostics area with duplicate warnings |
65598 | 2012-06-13 9:58 | 2012-06-18 6:31 | MySQL Server: MyISAM storage engine | Verified (4505 days) | S3 | 5.5.19, 5.5.26 | Any | Any | Concurrent SET requests return non-existant error |
67123 | 2012-10-07 13:02 | 2012-10-12 12:56 | MySQL Server: MyISAM storage engine | Verified (4384 days) | S1 | 5.5.27, 5.5.29, 5.1.67, 5.7.0 | Any (MS Windows 2008 64bit, Linux) | Any | error in mi_update.c:226 |
68113 | 2013-01-17 22:27 | 2013-01-18 6:46 | MySQL Server: MyISAM storage engine | Verified (4286 days) | S3 | 5.5.28 | Any | Any | Avoid division by zero in MyISAM's chk_data_link |
69926 | 2013-08-05 10:40 | 2022-06-27 18:23 | MySQL Server: MyISAM storage engine | Verified (1774 days) | S1 | 5.1 , 5.5, 5.6, 5.6.46 | Linux | Any | MySQL crash on disk full with mysqld got signal 11 |
96001 | 2019-06-26 12:07 | 2019-09-02 12:14 | MySQL Server: MyISAM storage engine | Verified (1936 days) | S3 | 8.0.16, 5.7.26 | Any | Any | No warning when creating foreign key in MyISAM tables |
36392 | 2008-04-29 9:26 | 2022-12-04 20:45 | MySQL Server: MyISAM storage engine | Verified (6005 days) | S3 | 5.1.24-win32 | Windows | Any | no warning when key_buffer_size set too high? |
43514 | 2009-03-09 21:16 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Verified (5696 days) | S3 | 6.0.11 | Windows | Any | Drop MyISAM fails on Windows with lower_case_table_names = 2 |
82957 | 2016-09-12 19:14 | 2021-02-16 12:22 | MySQL Server: MyISAM storage engine | Verified (1335 days) | S3 | 8.0.0 | Any | Any | Remove MRG_MYISAM (MERGE) storage engine |
77538 | 2015-06-29 11:06 | 2015-06-29 11:35 | MySQL Server: MyISAM storage engine | Verified (3394 days) | S2 | 5.1/5.5/5.6/5.7 | Linux | Any | MyISAM accepts table definition that is no longer considered as correct |
63901 | 2012-01-02 19:08 | 2012-05-07 7:30 | MySQL Server: MyISAM storage engine | Verified (4668 days) | S3 | 5.1, 5.5+ | Any | Any | Potentially invalid write to a MYISAM_SHARE share object |
69585 | 2013-06-26 11:23 | 2014-07-22 18:41 | MySQL Server: MyISAM storage engine | Verified (3736 days) | S1 | 5.5.30 x64, 5.5.39, 5.6.21, 5.7.5 | Any (MS Windows W2K8 64bit, Linux) | Any | low-priority-updates not working on replication slave |
32714 | 2007-11-26 13:14 | 2012-05-18 20:19 | MySQL Server: MyISAM storage engine | Verified (6164 days) | S2 | 5.0.42 - 5.0.46 | Linux | Any | Wrong value for function in JOINs ON-clause if functions reads from joined table |
67629 | 2012-11-19 0:27 | 2012-11-19 11:52 | MySQL Server: MyISAM storage engine | Verified (4346 days) | S3 | 5.1/5.5.28 | FreeBSD | Any | Changing the type of the column destroys the table. Data loss. |
56902 | 2010-09-21 16:43 | 2013-03-03 20:45 | MySQL Server: MyISAM storage engine | Verified (5136 days) | S1 | mysql-5.1.50.tar | Linux (Linux 2.6.18-164.el5xen Red Hat) | Any | Reproducible/systematic core by myisampack (latest 5.1.50 version) |
72053 | 2014-03-17 7:09 | 2014-03-17 18:53 | MySQL Server: MyISAM storage engine | Verified (3863 days) | S1 | 5.5,5.6,5.7 | Any | Any | mysql client command coredump when disk space is full! |
79392 | 2015-11-24 6:16 | 2015-11-24 8:31 | MySQL Server: MyISAM storage engine | Verified (3246 days) | S2 | 5.7.9 GA | Any | Any | handle_fatal_signal (sig=11) in ha_myisammrg::detach_children |
32364 | 2007-11-14 9:56 | 2013-03-03 20:45 | MySQL Server: Merge storage engine | Verified (6178 days) | S2 | 5.1.22-rc, 5.1 BK, 5.0 BK, 4.1 BK | Any | Any | MERGE doen't work with compressed and uncompressed tables |
41217 | 2008-12-04 8:39 | 2013-03-03 20:45 | MySQL Server: Merge storage engine | Verified (5792 days) | S3 | 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | SELECT from MERGE table which unions many tables gives wrong error |
62548 | 2011-09-27 10:22 | 2015-05-16 14:26 | MySQL Server: Memory storage engine | Verified (4765 days) | S2 | 5.1.49, 5.1.58 | Linux (Ubuntu) | Any | Different result from memory and myisam table |
67978 | 2012-12-27 6:13 | 2012-12-29 16:21 | MySQL Server: Memory storage engine | Verified (4306 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Signed zero is handled incorrectly by HASH indexes and GROUP BY |
85291 | 2017-03-03 11:41 | 2017-03-03 11:42 | MySQL Server: Memory storage engine | Verified | S3 | 5.1+ | Any | Any | missing break for case HA_EXTRA_RESET_STATE in function heap_extra |
74198 | 2014-10-03 0:07 | 2014-10-12 17:45 | MySQL Server: Memory storage engine | Verified (3654 days) | S3 | 5.7.5 | Any | Any | Get full table scan after FORCE INDEX for HEAP |
75887 | 2015-02-13 9:04 | 2015-03-06 7:30 | MySQL Server: Memcached | Verified | S3 | 5.6.24 | Any | Any | memcached - configuration script fails if the test database doesn't exists |
72911 | 2014-06-08 9:20 | 2014-06-09 11:37 | MySQL Server: Memcached | Verified (3779 days) | S3 | 5.6.17, 5.6.20, 5.7.5 | Linux (CentOS 6.5 x64) | Any | Memcached plugins init sql should change to support storge large value size |
97456 | 2019-11-01 14:44 | 2019-11-26 11:27 | MySQL Server: Memcached | Verified (1794 days) | S3 | 8.0 | Any | Any | Memory leak at corner cases in authentication_win and storage ndb engine |
72464 | 2014-04-26 10:12 | 2014-04-29 8:12 | MySQL Server: Logging | Verified | S3 | 5.6.17 | Any | Any | the unsafe statement spam throttling is not good enough |
115959 | 2024-08-29 9:53 | 2024-08-29 10:42 | MySQL Server: Logging | Verified (45 days) | S3 | 8.0.39 | Any | Any | Unable to locate recent stack traces in a large error log. |
57690 | 2010-10-24 10:47 | 2022-12-04 20:45 | MySQL Server: Logging | Verified (5077 days) | S3 | 5.1.50 | Linux | Any | impossible to redirect log-error to STDOUT in 5.1 |
90679 | 2018-04-29 7:54 | 2018-04-30 8:33 | MySQL Server: Logging | Verified (2358 days) | S3 | 8.0 | Any | Any | dragnet logging: make uninstall messages clearer and document dependency issues |
103684 | 2021-05-13 12:43 | 2024-07-25 20:23 | MySQL Server: Logging | Verified (1249 days) | S3 | 8.0.24 | Any | Any | Warning issued when querying ps. keyring_component_status |
90111 | 2018-03-16 14:50 | 2018-06-14 5:00 | MySQL Server: Logging | Verified (2402 days) | S3 | 5.7 | Any | Any | Incorrect enum comparisons |
80489 | 2016-02-24 7:26 | 2016-02-24 7:39 | MySQL Server: Logging | Verified (3154 days) | S2 | 5.7.11 | Any | Any | Very misleading log messages upon failures of file operations |
59999 | 2011-02-07 21:11 | 2022-12-04 20:45 | MySQL Server: Locking | Verified | S3 | 5.5, 5.6.2 | Any | Any | mysqlhotcopy returns error and crashes debug server |
71055 | 2013-12-03 5:18 | 2013-12-09 3:00 | MySQL Server: Locking | Verified (3961 days) | S2 | 5.5.12, 5.5.35, 5.6.16 | Windows | Any | Using IF EXISTS(SELECT * ...) acquires a lock when using read uncommitted |
106610 | 2022-03-01 10:32 | 2022-04-04 11:34 | MySQL Server: Locking | Verified (923 days) | S2 | 5.7.33 | Linux | x86 | Concurrent INSERT IGNORE in InnoDB table may trigger the database to stall |
108881 | 2022-10-26 8:46 | 2022-10-28 11:04 | MySQL Server: Locking | Verified (716 days) | S3 | 8.0.31 | Ubuntu (22.04) | x86 (x86_64) | FLUSH TABLES deadlock |
64814 | 2012-03-30 12:26 | 2012-03-31 9:30 | MySQL Server: Locking | Verified (4579 days) | S3 | 5.5.19 | Any | Any | Inconsistent error when concurrently dropping table and trigger |
80436 | 2016-02-19 2:34 | 2020-02-17 0:31 | MySQL Server: Locking | Verified (2620 days) | S2 | 5.6 | Linux | Any | Failed !lock->recursive assert in sync0rw.cc |
110795 | 2023-04-25 5:45 | 2023-04-25 8:41 | MySQL Server: Locking | Verified (537 days) | S3 | 8.0.27, 8.0.33, 5.7.42 | Any | Any | mysql insert is deadlocked |
102595 | 2021-02-14 23:00 | 2021-02-15 8:40 | MySQL Server: JSON | Verified (1336 days) | S3 | 5.7.31, 5.7.33 | CentOS (CentOS Linux release 7.6.1810 (Core)) | Any | Internal error: JSON wrapper: unexpected type from json_unquote json_extract |
88689 | 2017-11-29 6:57 | 2021-11-30 9:55 | MySQL Server: JSON | Verified (1048 days) | S3 | 5.7, 5.7.36 | Linux | Any | LOAD DATA is failed if JSON file include blank line at end of file |
91245 | 2018-06-14 2:08 | 2024-06-25 13:20 | MySQL Server: JSON | Verified (2313 days) | S2 | 5.7.19, 5.7.22, 8.0.11 | MacOS | Any | json column wtih integer value got incorrect result |
113049 | 2023-11-10 15:28 | 2024-01-17 16:27 | MySQL Server: JSON | Verified (270 days) | S2 | 8.0.35, 8.2.0 | Any | Any | MTR test json.array_index fails with a result difference |
116160 | 2024-09-19 10:28 | 2024-09-20 8:58 | MySQL Server: JSON | Verified (23 days) | S3 | 8.0 | Any | Any | Precision loss of double value in JSON |
116300 | 2024-10-04 13:44 | 2024-10-04 14:34 | MySQL Server: JSON | Verified (9 days) | S2 | 9.0 | Any | Any | TINYBLOB and BLOB with same value, stored as JSON, become different |
100567 | 2020-08-19 3:37 | 2020-08-27 11:24 | MySQL Server: JSON | Verified (1516 days) | S3 | 8.0, 8.0.21, 8.0.11 | Any | Any | Unexpected cast to float from attribute of a JSON datum |
95698 | 2019-06-07 22:40 | 2019-06-10 7:10 | MySQL Server: JSON | Verified (1952 days) | S3 | 8.0, 8.0.16, 5.7.26 | Any | Any | JSON columns are returned with binary charset |
100885 | 2020-09-18 3:43 | 2020-11-09 11:38 | MySQL Server: JSON | Verified (1486 days) | S5 | 5.7.31 | Any | Any | generated column index against json column is not used with different encoding |
102233 | 2021-01-12 11:34 | 2021-01-12 11:45 | MySQL Server: JSON | Verified (1370 days) | S3 | 8.0, 8.0.22 | Any | Any | JSON Path evaluation is not standard-compliant |
41313 | 2008-12-08 23:31 | 2011-02-16 23:43 | MySQL Server: Installing | Verified (5786 days) | S2 | 5.1.30 | Any (Windows) | Any | network administrator does not have TRIGGER and EVENT privileges |
91476 | 2018-06-28 15:58 | 2018-10-21 20:45 | MySQL Server: Installing | Analyzing (2266 days) | S1 | Installer 1.4.25 MySQL 8.0.1.1 | Windows (Cannot Initialize DB) | Any | Still getting error in Installer 1.4.25 |
90796 | 2018-05-09 3:48 | 2018-05-14 6:25 | MySQL Server: Installing | Verified (2346 days) | S2 | 5.7.22 | Ubuntu (18.04 Gnome shell) | x86 | Trying to install Mysql and set root password, not working on Ubuntu 18.04 |
95246 | 2019-05-04 10:08 | 2020-04-02 7:34 | MySQL Server: Installing | Verified (1907 days) | S2 | 8.0.16, 8.0.17 | Windows (Microsoft Windows 10 Home Single Language) | Any | Serious bug!!! Related to PATH environment variable on Windows 10 |
55283 | 2010-07-15 13:36 | 2016-12-04 20:45 | MySQL Server: InnoDB Plugin storage engine | Verified (5171 days) | S3 | 5.1,5.5 | Any | Any | assert trx0roll.c undo_no + 1 == trx->undo_no in trx_rollback_or_clean_all_recov |
64181 | 2012-01-31 14:41 | 2012-02-09 12:20 | MySQL Server: InnoDB Plugin storage engine | Verified (4635 days) | S5 | 5.1.52, 5.1.61 | Any | Any | unzip_LRU length management might need to be updated for SSD |
72351 | 2014-04-15 12:10 | 2015-07-23 5:49 | MySQL Server: InnoDB Plugin storage engine | Verified (3833 days) | S2 | 5.6.16+ | Any | Any | mysqld failed recovery for in-place upgrading from 5.5 to 5.6 |
116209 | 2024-09-24 7:44 | 2024-09-27 8:59 | MySQL Server: InnoDB storage engine | Verified (19 days) | S5 | 8.0 | Any | Any | Crash recovery is slow because of repeated scans of double-wrtie |
45812 | 2009-06-28 18:39 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Verified (2742 days) | S3 | 5.4.2-beta | Solaris | Any | DTrace: no InnoDB read row probes |
58234 | 2010-11-16 16:26 | 2014-02-26 12:47 | MySQL Server: InnoDB storage engine | Verified (4683 days) | S5 | 5.1.49-r1, 5.5.20 | Any | Any | LENGTH() / OCTET_LENGTH() on BLOB field very slow |
60613 | 2011-03-24 3:29 | 2013-01-16 19:54 | MySQL Server: InnoDB storage engine | Verified (4288 days) | S3 | 5.0, 5.1.56, 5.1.67 | Any | Any | SYS_TABLES is accessed before recv_recovery_from_checkpoint_finish() may crash |
62535 | 2011-09-25 14:46 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | Verified (4701 days) | S3 | 5.5, 5.1, etc | Linux | Any | os_event_create() has inefficient memory allocation |
70047 | 2013-08-15 11:57 | 2015-02-24 1:46 | MySQL Server: InnoDB storage engine | Verified (4028 days) | S3 | 5.6.12 | Any | Any | srv_buf_size not declared |
71164 | 2013-12-17 16:38 | 2014-09-05 2:44 | MySQL Server: InnoDB storage engine | Verified (3944 days) | S3 | 5.6.15 | Any | Any | an autocommit SELECT was not treated as autocommit non-lock trx |
71521 | 2014-01-30 8:43 | 2017-04-05 11:45 | MySQL Server: InnoDB storage engine | Verified (3909 days) | S2 | 5.6 | Any | Any | Manual does not list all valid values for innodb_flush_method |
72123 | 2014-03-25 14:12 | 2017-10-04 3:52 | MySQL Server: InnoDB storage engine | Verified (3853 days) | S3 | 5.6, 5.6.18 | Any | Any | Spurious lock_wait_timeout_thread wakeup in lock_wait_suspend_thread() |
73583 | 2014-08-14 13:31 | 2018-04-01 6:04 | MySQL Server: InnoDB storage engine | Verified (3702 days) | S3 | 5.6.12 | Any | Any | buf_read_page_async calls buf_read_page_low with sync=true |
76670 | 2015-04-13 4:16 | 2015-04-14 13:40 | MySQL Server: InnoDB storage engine | Verified (3470 days) | S3 | 5.6.23 | Windows | Any | GetLastError() should be called just after FindNextFile() at os0file.cc |
76932 | 2015-05-04 14:56 | 2015-05-04 15:44 | MySQL Server: InnoDB storage engine | Verified (3450 days) | S3 | 5.7.7 | Any | Any | comment of innodb_buffer_pool_chunk_size is incorrect |
83047 | 2016-09-20 7:40 | 2023-08-15 10:35 | MySQL Server: InnoDB storage engine | Verified (2573 days) | S2 | 5.7 | Ubuntu | Any | Memory usage gradually increases and brings server to halt |
84241 | 2016-12-16 23:53 | 2017-01-16 12:14 | MySQL Server: InnoDB storage engine | Verified (2827 days) | S3 | 5.7.15 | Ubuntu (16.04) | Any | Potential Race Condition |
85307 | 2017-03-04 13:53 | 2018-11-07 13:01 | MySQL Server: InnoDB storage engine | Verified (2770 days) | S3 | 5.7 | Any | Any | The server refuses to restart if turn off innodb_log_checksums |
85585 | 2017-03-22 21:36 | 2023-06-01 12:05 | MySQL Server: InnoDB storage engine | In progress (1418 days) | S1 | 5.6.35-80.0-debug-log | Any | Any | InnoDB: Failing assertion: UT_LIST_GET_LEN(buf_pool->flush_list) == 0 |
88399 | 2017-11-08 8:39 | 2018-02-18 18:29 | MySQL Server: InnoDB storage engine | Verified (2489 days) | S5 | 5.7,8.0 | Linux | ARM | Using CAS for trylock in place of TAS for EventMutex (arm64) |
88827 | 2017-12-08 1:30 | 2018-05-31 13:08 | MySQL Server: InnoDB storage engine | Verified (2386 days) | S3 | 5.6.35, 5.6.38, 5.7.20, 8.0.4 | Any | Any | innodb uses too much space in the PK for concurrent inserts into the same table |
91977 | 2018-08-11 3:57 | 2023-12-09 19:04 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.7.17 | Any | Any | Dropping Large Table Causes Semaphore Waits; No Other Work Possible |
94441 | 2019-02-22 9:42 | 2019-02-22 11:25 | MySQL Server: InnoDB storage engine | Verified (2060 days) | S3 | 5.7.25, 8.0.15 | Any | Any | empty ibuf aio reads in innodb status |
100182 | 2020-07-10 13:35 | 2020-07-13 12:40 | MySQL Server: InnoDB storage engine | Verified (1556 days) | S5 | 8.0.20 | Any | ARM | Improving performance of 'row_mysql_store_col_in_innobase_format' |
101200 | 2020-10-16 3:25 | 2020-10-17 1:19 | MySQL Server: InnoDB storage engine | Verified (1458 days) | S5 | 8.0 | Any | Any | All commits are unnecessarily blocked for more than 1ms at binlog rotate |
101532 | 2020-11-10 6:10 | 2020-11-10 12:53 | MySQL Server: InnoDB storage engine | Verified (1433 days) | S5 | 8.0 | Any | Any | LRU list should still be maintained before the very first eviction |
106630 | 2022-03-03 12:48 | 2022-09-01 19:46 | MySQL Server: InnoDB storage engine | Verified (955 days) | S3 | 8.0.28 | CentOS | Any | Contribution by Tencent: Missing declaration of srv_log_writer_timeout |
108503 | 2022-09-15 23:49 | 2022-09-16 4:57 | MySQL Server: InnoDB storage engine | Verified (758 days) | S3 | 8.0.21 | Any | Any | Check return error from os_file_create_subdirs_if_needed() |
108505 | 2022-09-15 23:54 | 2022-09-16 5:01 | MySQL Server: InnoDB storage engine | Verified (758 days) | S2 | 8.0.21 | Any | Any | Check return pointer from dict_sdi_get_index() |
108506 | 2022-09-15 23:58 | 2022-09-16 5:04 | MySQL Server: InnoDB storage engine | Verified (758 days) | S2 | 8.0.21 | Any | Any | Check return error from fil_space_acquire() |
108507 | 2022-09-16 0:07 | 2022-09-16 5:22 | MySQL Server: InnoDB storage engine | Verified (758 days) | S2 | 8.0.21 | Any | Any | Return value of my_rand_buffer() not get checked |
108714 | 2022-10-08 14:51 | 2022-10-10 4:50 | MySQL Server: InnoDB storage engine | Verified (734 days) | S3 | 8.0.27, 8.0.30 | Any | Any | ha_innodb.cc Possible error log output should have errors |
109784 | 2023-01-26 3:19 | 2023-02-03 9:36 | MySQL Server: InnoDB storage engine | Verified (622 days) | S3 | 8.0 | Any | Any | Remove innodb table lock and use MDL lock to protect table |
111276 | 2023-06-05 10:42 | 2023-09-05 1:39 | MySQL Server: InnoDB storage engine | Verified (496 days) | S3 | 8.0, 5.7 | Any | Any | There are some punctuation errors here, when buf_flush_do_batch |
113312 | 2023-12-01 22:48 | 2024-05-02 6:18 | MySQL Server: InnoDB storage engine | Verified (248 days) | S2 | 8.0.35, 8.1.0 | Any | Any | Server stall during Alter/Drop table while clearing AHIs from the buffer pool |
113733 | 2024-01-24 6:36 | 2024-02-01 6:39 | MySQL Server: InnoDB storage engine | Verified (255 days) | S2 | 8.0, 8.0.36 | Any | Any | Innodb page has a large proportion of garbage space in certain conditions |
82798 | 2016-08-30 9:54 | 2016-08-30 12:04 | MySQL Server: InnoDB storage engine | Verified (2966 days) | S2 | 5.6, 5.6.32 | Any | Any | Small buffer pools might be too small for rseg init during crash recovery |
89760 | 2018-02-22 6:49 | 2018-02-22 7:23 | MySQL Server: InnoDB storage engine | Verified (2425 days) | S3 | 5.7, 5.7.21 | Any | Any | mysql server crash at dict0dict.cc:2328 |
101900 | 2020-12-08 3:21 | 2024-01-30 6:39 | MySQL Server: InnoDB storage engine | Verified (1405 days) | S2 | 8.0.21 | Linux (7.6) | Any | Add partition is slow |
76472 | 2015-03-24 10:21 | 2015-03-24 12:17 | MySQL Server: InnoDB storage engine | Verified (3491 days) | S3 | 5.6.23, 5.6.25 | Linux (CentOS 7) | Any | Failing assertion: index_id == index->id in btr0sea.cc line 1161 |
91956 | 2018-08-10 6:56 | 2019-01-28 10:59 | MySQL Server: InnoDB storage engine | Verified (2256 days) | S3 | 5.6.41, 5.7.23 | Any | Any | Sig 6 : Assertion failure in ha_innodb.cc line 17420 |
115780 | 2024-08-06 7:25 | 2024-08-20 3:42 | MySQL Server: InnoDB storage engine | Verified (67 days) | S2 | 8,9, 8.0.39 | Any | Any | InnoDB aborts when a DB_OUT_OF_RESOURCES error occurs in Parallel_reader |
68064 | 2013-01-10 4:17 | 2018-05-04 7:43 | MySQL Server: InnoDB storage engine | Verified (4282 days) | S3 | 5.5.16, 5.5.31 | Solaris | Any | mysql crashes when Solaris resource controls prevent memory from allocation |
80530 | 2016-02-26 13:13 | 2016-04-04 10:27 | MySQL Server: InnoDB storage engine | Verified (3114 days) | S3 | 5.7.11 | Any | Any | innodb monitor_set_tlb variable used before initialized, data race |
86234 | 2017-05-09 5:27 | 2017-05-09 6:15 | MySQL Server: InnoDB storage engine | Verified (2714 days) | S2 | 5.5.54, 5.6.35, 5.7.17, 5.6.36, 5.7.18 | Any | Any | InnoDB: Failing assertion: heap->magic_n == MEM_BLOCK_MAGIC_N |
79637 | 2015-12-14 16:55 | 2015-12-15 5:07 | MySQL Server: InnoDB storage engine | Verified (3225 days) | S5 | 5.6, 5.7 | Any | Any | Hard-coded cache line size |
96504 | 2019-08-12 4:42 | 2019-08-12 18:21 | MySQL Server: InnoDB storage engine | Verified (1889 days) | S5 | 8.0 | Any | ARM | Refine atomics and barriers for weak memory order platform |
116305 | 2024-10-06 11:05 | 2024-10-09 13:54 | MySQL Server: InnoDB storage engine | Verified (4 days) | S2 | 9.0 | Any | Any | row_search_mvcc process wrong page of small buffer pool |
104787 | 2021-09-01 8:57 | 2024-04-16 13:48 | MySQL Server: InnoDB storage engine | Verified (418 days) | S2 | 8.0 | Any | Any | need wait buf_fix_count =0 in buf_read_page_handle_error |
80695 | 2016-03-10 17:12 | 2016-03-11 11:06 | MySQL Server: InnoDB storage engine | Verified (3138 days) | S3 | 5.7.11 | CentOS | Any | handle_fatal_signal (sig=6) in ib::fatal::~fatal | innobase/ut/ut0ut.cc:920 |
91630 | 2018-07-13 14:47 | 2018-07-15 6:02 | MySQL Server: InnoDB storage engine | Verified (2282 days) | S2 | 5.6.40 | Any | Any | stack-use-after-scope in innobase_convert_identifier() detected by ASan |
72995 | 2014-06-13 3:23 | 2014-07-15 17:54 | MySQL Server: InnoDB storage engine | Verified (3743 days) | S3 | 5.6.21 | Any | Any | mysql server crash slient when out of memory using srv_use_sys_malloc |
74663 | 2014-11-03 6:31 | 2018-03-02 4:19 | MySQL Server: InnoDB storage engine | Verified (2417 days) | S3 | 5.6.20-debug, 5.6.22 | Linux (CentOS 7) | Any | DROP TABLE corrupts table | inode fsp0fsp.cc line 1887 fseg_inode_get |
82013 | 2016-06-27 9:30 | 2016-11-13 8:32 | MySQL Server: InnoDB storage engine | Verified | S3 | 5.7 | Any | Any | assertion: state == TRX_STATE_NOT_STARTED || state == TRX_STATE_FORCED_ROLLBACK |
93165 | 2018-11-12 15:11 | 2018-11-26 21:02 | MySQL Server: InnoDB storage engine | Verified (2148 days) | S3 | 5.7.23, 5.7.24 | Any | Any | Memory leak in sync_latch_meta_init() after mysqld shutdown detected by ASan |
66683 | 2012-09-04 13:57 | 2012-09-04 18:47 | MySQL Server: InnoDB storage engine | Verified (4422 days) | S3 | 5.5.27 | Any | Any | InnoDB doesn't report DB_OUT_OF_FILE_SPACE during recovery |
83361 | 2016-10-13 6:26 | 2016-10-13 7:32 | MySQL Server: InnoDB storage engine | Verified (2922 days) | S3 | 5.7.13, 5.7.15 | Any | Any | InnoDB: Failing assertion: logger->debug() |
87203 | 2017-07-26 10:03 | 2017-07-27 14:43 | MySQL Server: InnoDB storage engine | Verified (2635 days) | S3 | 5.7 | Any | Any | Suspicious UAF at storage/innobase/row/row0merge.cc |
90154 | 2018-03-21 7:23 | 2018-03-21 7:56 | MySQL Server: InnoDB storage engine | Verified (2398 days) | S3 | 5.7.21 | CentOS | Any | Sig 6 assert: fil_space_get(table->space) != __null in row0quiesce.cc line 724 |
110060 | 2023-02-14 9:32 | 2023-03-07 5:40 | MySQL Server: InnoDB storage engine | Verified | S2 | 5.7.41 | Any | Any | shutdown: Failing assertion: UT_LIST_GET_LEN(rseg->update_undo_list) == 0 |
108508 | 2022-09-16 0:11 | 2023-09-06 7:55 | MySQL Server: InnoDB storage engine | Verified (758 days) | S2 | 8.0.21 | Any | Any | Return value of field_store_string() not get checked |
76793 | 2015-04-22 17:18 | 2016-04-20 17:15 | MySQL Server: InnoDB storage engine | Verified (3147 days) | S3 | 5.6.20, 5.6.24 | Any | Any | Different row size limitations in Anaconda and Barracuda file formats |
102831 | 2021-03-05 16:32 | 2021-04-19 6:39 | MySQL Server: InnoDB storage engine | Verified (1317 days) | S2 | 5.7.31, 5.7.33 | Any (CentOS, Ubuntu) | Any | transaction-isolation level is not honored when changed at session level |
111079 | 2023-05-18 18:01 | 2023-05-19 13:10 | MySQL Server: InnoDB storage engine | Verified (513 days) | S3 | 8.0 | Any | Any | InnoDB SDI index description has fields out-of-order |
98072 | 2019-12-25 13:27 | 2020-01-02 13:05 | MySQL Server: InnoDB storage engine | Verified (1746 days) | S3 | 8.0.18, 8.0.11 | Any | Any | innochecksum summary shows blob pages as other type of page for 8.0 tables |
101465 | 2020-11-05 1:03 | 2020-11-06 13:28 | MySQL Server: InnoDB storage engine | Verified (1437 days) | S5 | 8.0 | Any | Any | mysql doesn't release index sx latch properly in page split operation |
73512 | 2014-08-08 21:35 | 2014-08-11 8:16 | MySQL Server: InnoDB storage engine | Verified (3716 days) | S3 | mysql-5.6.20, 5.6.21 | Any | Any | No useful errormsg. when trying to set innodb table datadir to non-writable path |
73881 | 2014-09-10 23:39 | 2014-09-12 18:04 | MySQL Server: InnoDB storage engine | Verified (3684 days) | S3 | 5.6 | Any | Any | InnoDB: Failing assertion: state == TRX_STATE_NOT_STARTED on concurrent DDL/DML |
83794 | 2016-11-13 23:53 | 2016-11-14 0:12 | MySQL Server: InnoDB storage engine | Verified (2890 days) | S3 | 5.6.34 | Any | Any | InnoDB: Failing assertion: zip_size == fil_space_get_zip_size(space) |
89759 | 2018-02-22 6:38 | 2018-02-22 7:23 | MySQL Server: InnoDB storage engine | Verified (2425 days) | S3 | 5.7, 5.7.21 | Any | Any | mysql server crash at dict0stats_bg.cc:383 |
109200 | 2022-11-24 22:02 | 2023-06-28 14:54 | MySQL Server: InnoDB storage engine | Verified (501 days) | S3 | 5.7, 8.0 | Any | Any | Metrics not incremented for 1st iteration in buf_LRU_free_from_common_LRU_list. |
71232 | 2013-12-26 11:34 | 2014-07-04 9:51 | MySQL Server: InnoDB storage engine | Verified (3754 days) | S3 | 5.6.15 | Any | Any | Wrong behaviour for auto_increment unsigned bigint column approaching max value |
70164 | 2013-08-27 13:57 | 2013-08-28 11:19 | MySQL Server: InnoDB storage engine | Verified (4064 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Misleading comment for the recv_parse_or_apply_log_rec_body() function |
80444 | 2016-02-19 12:12 | 2016-02-19 12:36 | MySQL Server: InnoDB storage engine | Verified (3159 days) | S3 | 5.6.29, 5.6.30, 5.7.11 | CentOS | Any | Sig6: `!!new_clustered==(innobase_need_rebuild(ha_alter_info) || add_fts_doc_id) |
98546 | 2020-02-11 6:38 | 2020-02-12 15:20 | MySQL Server: InnoDB storage engine | Verified (1705 days) | S5 | 8, 5.7 | Any | Any | Transient indexes statistics are updated in foreground causing performance issue |
102668 | 2021-02-20 6:53 | 2021-02-22 14:23 | MySQL Server: InnoDB storage engine | Verified (1329 days) | S3 | 8.0.23 | Any | Any | Unused parameter documented in the comment as used |
28913 | 2007-06-06 4:54 | 2019-08-24 6:02 | MySQL Server: InnoDB storage engine | Verified (5028 days) | S2 | 5.0.45, 5.1 | Windows | Any | Running MySQL data on a GPT drive? |
10132 | 2005-04-25 3:00 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | Verified (3916 days) | S1 | 5.1, 6.0 | Linux (Linux) | Any | Crashing the server on corrupt InnoDB page is unhelpful |
59710 | 2011-01-25 10:11 | 2022-04-10 20:45 | MySQL Server: InnoDB storage engine | Verified | S3 | 5.6+ | Any | Any | InnoDB mutex_t size should be trimmed |
64304 | 2012-02-12 17:04 | 2012-02-16 9:49 | MySQL Server: InnoDB storage engine | Verified (4627 days) | S5 | 5.5 | Any | Any | assemble to implement procedure of transforming between big-end and little-end |
70950 | 2013-11-19 7:03 | 2015-06-28 20:45 | MySQL Server: InnoDB storage engine | Verified (3980 days) | S5 | 5.7+ | Any | Any | log_sys->mutex is so hot in pure write cases |
80496 | 2016-02-24 14:00 | 2018-06-13 12:30 | MySQL Server: InnoDB storage engine | Verified (2445 days) | S3 | 5.7, 5.7.11, 8.0.4 | Any | Any | buf_dblwr_init_or_load_pages now returns an error code, but caller not updated |
85208 | 2017-02-27 13:35 | 2017-03-01 15:26 | MySQL Server: InnoDB storage engine | Verified (2783 days) | S3 | 8.0.0 | Any | Any | A follow-up fix for buffer pool mutex split patch might be suboptimal, commit 2 |
90903 | 2018-05-17 6:13 | 2018-05-23 14:51 | MySQL Server: InnoDB storage engine | Verified (2335 days) | S2 | 5.6/5.7/8.0 | Any | Any | ALTER TABLE doesn't prevent AUTO_INCREMENT out of range in strict mode |
91513 | 2018-07-02 6:39 | 2018-07-02 11:19 | MySQL Server: InnoDB storage engine | Verified (2295 days) | S3 | 8.0,5.7 | Any | Any | log_end isn't correctly calculated in mlog_open_and_write_index |
99295 | 2020-04-18 7:56 | 2020-04-20 10:04 | MySQL Server: InnoDB storage engine | Verified (1637 days) | S2 | 8.0.19 | Any | Any | InnoDB in-memory estimate is wrong after an index is created |
105652 | 2021-11-22 4:41 | 2021-11-23 14:20 | MySQL Server: InnoDB storage engine | Verified (1056 days) | S2 | 5.7, 8.0 | Any | Any | buffer pool flush_rbt could be disorded with innodb tablespace > 32TB |
107473 | 2022-06-03 3:34 | 2022-08-24 7:29 | MySQL Server: InnoDB storage engine | Verified (781 days) | S3 | 8.0.23, 8.0.29 | CentOS | Any | Updating BLOB column slows down purge and causes high trx_rseg_history_len |
110606 | 2023-04-04 10:16 | 2023-04-17 8:24 | MySQL Server: InnoDB storage engine | Verified (545 days) | S5 | 8.0 | Linux | ARM (aarch64) | Improve crc32c code for arm64 |
115256 | 2024-06-08 0:10 | 2024-06-08 7:47 | MySQL Server: InnoDB storage engine | Verified (127 days) | S3 | 8.4, 8.0.37 | Any | Any | Import tablespace does not work properly for decimal data type |
116291 | 2024-10-03 12:11 | 2024-10-07 13:13 | MySQL Server: InnoDB storage engine | Verified (9 days) | S5 | 8.0 | Any | Any | innodb crash recovery optimize for MLOG_REC_INSERT |
73659 | 2014-08-20 16:01 | 2017-05-14 20:45 | MySQL Server: InnoDB storage engine | Verified (3519 days) | S3 | 5.6 | Any | Any | [RDS 5616] bugfix: when crash on create table , the server may fail to restart |
80625 | 2016-03-06 9:26 | 2016-03-08 13:10 | MySQL Server: InnoDB storage engine | Verified (3141 days) | S1 | 5.6.29 | Any | Any | InnoDB: Failing assertion: table->data_dir_path while dropping table |
61735 | 2011-07-04 11:30 | 2011-07-08 6:02 | MySQL Server: InnoDB storage engine | Verified (4846 days) | S3 | 5.1, etc | Any | Any | index->lock held while preads are done |
67196 | 2012-10-11 21:00 | 2012-10-12 12:22 | MySQL Server: InnoDB storage engine | Verified (4384 days) | S3 | 5.5, 5.6 | Any | Any | ENUM type not treated correctly in HAVING w/ MAX() |
73168 | 2014-07-02 4:14 | 2015-02-25 10:51 | MySQL Server: InnoDB storage engine | Verified (3756 days) | S5 | 5.6/5.7 | Any | Any | locking/unlocking overhead for THD::LOCK_thd_data |
75512 | 2015-01-15 7:59 | 2015-03-10 3:20 | MySQL Server: InnoDB storage engine | Verified (3505 days) | S3 | 5.7.5, 5.7.6 | Any | Any | buf_flush_do_batch can be optimized if the lsn_limit is already satisfied. |
81099 | 2016-04-15 15:02 | 2019-06-03 5:37 | MySQL Server: InnoDB storage engine | Verified (3100 days) | S3 | 5.7, 5.6.30, 5.7.12 | Any | Any | INNODB_METRICS need better testing |
95491 | 2019-05-23 11:23 | 2019-06-05 11:48 | MySQL Server: InnoDB storage engine | Verified (1960 days) | S5 | ALL | Any | Any | The unused wake up in simulator AIO of function reserve_slot |
96391 | 2019-08-01 1:00 | 2019-08-05 13:49 | MySQL Server: InnoDB storage engine | Verified (1899 days) | S3 | 5.6 5.7 | Any | Any | a mrec_buf_t[] index bug in row_merge_blocks(). |
103059 | 2021-03-22 12:35 | 2021-03-23 5:35 | MySQL Server: InnoDB storage engine | Verified (1301 days) | S3 | 8.0.23 | Any | Any | system_variable_source does not report DYNAMIC when queried from sys_var update |
106220 | 2022-01-19 20:27 | 2022-01-20 13:57 | MySQL Server: InnoDB storage engine | Verified (997 days) | S3 | 8.0 | Any | Any | LatchCounter::m_counters not pfs instrumented |
112540 | 2023-09-27 13:10 | 2023-10-11 23:16 | MySQL Server: InnoDB storage engine | Verified (382 days) | S3 | 5.7 and less MariaDB 10.4 and less | Any | Any | Timestamp data type key column is changing implicitly |
68814 | 2013-03-29 15:33 | 2015-04-23 6:14 | MySQL Server: InnoDB storage engine | Verified (3461 days) | S3 | 5.6.10 | Any (Centos 6.3) | Any | MySQL optimizer consider few rows to examine but it is not really obvious why |
101154 | 2020-10-13 13:42 | 2022-08-30 12:19 | MySQL Server: InnoDB storage engine | Verified (1460 days) | S3 | 5.7 | Any | Any | err == DB_SUCCESS in in file btr0btr.cc line 2167 for internal temporary table |
60087 | 2011-02-10 13:14 | 2016-12-04 20:45 | MySQL Server: InnoDB storage engine | Verified (4994 days) | S3 | 5.5 | Any | Any | Patch: Minimize InnoDB I/O load by adding a prefetch stage |
65889 | 2012-07-13 0:21 | 2012-07-16 10:18 | MySQL Server: InnoDB storage engine | Verified (4475 days) | S3 | <=5.5 | Any | Any | Appended primary key stored inefficiently in unique surrogate keys |
68552 | 2013-03-02 13:00 | 2013-03-04 8:50 | MySQL Server: InnoDB storage engine | Verified (4241 days) | S3 | 5.1 builtin, plugin, 5.5, 5.6 | Any | Any | Leftover prototype for dict_load_space_id_list() |
68659 | 2013-03-13 7:47 | 2013-03-13 9:01 | MySQL Server: InnoDB storage engine | Analyzing (4232 days) | S5 | 5.6.10 | Any | Any | InnoDB Linux native aio should submit more i/o requests at once |
69276 | 2013-05-18 19:23 | 2014-11-05 15:15 | MySQL Server: InnoDB storage engine | Verified (4165 days) | S5 | 5.6.11 | Any | Any | fil_system->mutex contention limits block read rate with fast storage |
75962 | 2015-02-19 3:14 | 2015-03-03 20:46 | MySQL Server: InnoDB storage engine | Verified (3512 days) | S3 | 5.6.24, 5.7.6 | Any | Any | Innodb calls fsync when freeing a LRU page to fulfill page request |
76922 | 2015-05-04 8:08 | 2015-05-05 13:24 | MySQL Server: InnoDB storage engine | Verified (3449 days) | S2 | 5.5.43 | Linux (ubuntu 12.04.) | Any | #1030 - Got error -1 from storage engine |
79932 | 2016-01-12 9:27 | 2016-07-21 7:37 | MySQL Server: InnoDB storage engine | Verified (3006 days) | S2 | 5.7.10 | CentOS (7) | Any | Unclear error message while altering compressed table with page compression |
83799 | 2016-11-14 5:50 | 2020-08-23 14:39 | MySQL Server: InnoDB storage engine | Verified (2890 days) | S3 | 5.6.34, 5.7.16 | Any | Any | InnoDB: Assertion failure in thread x in file handler0alter.cc line 5817 |
87402 | 2017-08-11 15:59 | 2017-08-14 10:00 | MySQL Server: InnoDB storage engine | Verified (2617 days) | S5 | 8.0.2 | Any | Any | Redundant check in ut_rnd_gen_ulint() |
88422 | 2017-11-09 12:20 | 2017-11-14 14:42 | MySQL Server: InnoDB storage engine | Verified (2525 days) | S2 | 5.7.19 | Any | Any | MySQL 5.7 innodb purge thread get oldest readview could block other transaction |
94912 | 2019-04-05 2:14 | 2019-04-23 13:39 | MySQL Server: InnoDB storage engine | Verified (2017 days) | S3 | 8.0.14 and above | Any | Any | O_DIRECT_NO_FSYNC possible write hole |
112425 | 2023-09-22 5:39 | 2023-09-22 11:54 | MySQL Server: InnoDB storage engine | Verified (387 days) | S3 | 8.0 | Any | Any | trx_t might be Use-After-Free in innobase_commit_by_xid |
115157 | 2024-05-29 7:34 | 2024-05-29 7:53 | MySQL Server: InnoDB storage engine | Verified (137 days) | S3 | mysql-trunk, 8.0 | Any | Any | Potential Nullptr Derefence in file `storage\innobase\lob\zlob0update.cc` |
62602 | 2011-10-03 3:16 | 2013-01-27 16:20 | MySQL Server: InnoDB storage engine | Verified (4277 days) | S3 | any | Any | Any | An option to ignore foreign key checks |
84439 | 2017-01-07 10:40 | 2017-01-09 5:21 | MySQL Server: InnoDB storage engine | Verified (2834 days) | S3 | 5.7.17-log | Any | Any | Table of row size of ~800 bytes does not compress with KEY_BLOCK_SIZE=1. |
105435 | 2021-11-03 3:23 | 2021-11-16 8:19 | MySQL Server: InnoDB storage engine | Verified (1075 days) | S3 | 8.0 | Any | Any | InnoDB: mem_heap_alloc(heap, 0) returns non-null pointer |
62018 | 2011-07-28 15:15 | 2018-02-11 20:45 | MySQL Server: InnoDB storage engine | Verified (4288 days) | S5 | 5.6.3 | Any | Any | innodb adaptive hash index mutex contention |
70811 | 2013-11-04 17:28 | 2013-11-06 12:16 | MySQL Server: InnoDB storage engine | Verified (3994 days) | S3 | 5.7 | Any | Any | buf_flush_event initialized too late |
72851 | 2014-06-03 14:01 | 2015-08-30 12:07 | MySQL Server: InnoDB storage engine | Verified (3784 days) | S3 | 5.6 | Any | Any | Fix for bug 16345265 in 5.6.11 breaks backward compatibility for InnoDB recovery |
74919 | 2014-11-18 18:15 | 2015-11-25 16:01 | MySQL Server: InnoDB storage engine | Verified (3398 days) | S3 | all | Any | Any | purge should remove intermediate rows between far snapshots |
100801 | 2020-09-10 13:48 | 2020-09-10 14:53 | MySQL Server: Information schema | Verified (1494 days) | S3 | 8.0.21 | Any | Any | Wrong datatype for column DATA_TYPE in INFORMATION_SCHEMA |
47697 | 2009-09-29 6:19 | 2015-11-05 10:35 | MySQL Server: Information schema | Verified (5493 days) | S2 | 5.1.39 | Any | Any | Inconsistencies in the query outputs on INFORMATION_SCHEMA.TABLES. |
91801 | 2018-07-26 13:20 | 2018-07-27 12:21 | MySQL Server: Information schema | Verified (2270 days) | S3 | 5.6.40 | Any | Any | Read of free memory in mysqld_list_processes |
112556 | 2023-09-28 7:03 | 2024-07-02 3:40 | MySQL Server: Information schema | Verified (103 days) | S2 | 8.0.30,8.4.0 | Any | Any | Created_tmp_disk_tables doesn't count on-disk temptable with fallback |
112151 | 2023-08-23 5:50 | 2023-08-31 10:50 | MySQL Server: Information schema | Verified (409 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | Wrong query output type |
112297 | 2023-09-08 8:48 | 2023-09-08 9:42 | MySQL Server: Information schema | Verified (401 days) | S3 | 8.1.0, 8.0.34 | Ubuntu (22.04) | x86 (x86_64) | Wrong query output type 2 |
71172 | 2013-12-18 11:38 | 2013-12-26 18:07 | MySQL Server: Information schema | Verified (3944 days) | S2 | 5.6.14, 5.6.16, 5.5.35, 5.1.74. 5.0.97 | Windows (7 x64) | Any | There's no way to get default value as binary from a (var)binary column |
71280 | 2014-01-02 18:21 | 2014-01-03 8:37 | MySQL Server: Information schema | Verified (3936 days) | S3 | 5.6.14, 5.6.15, 5.6.16 | Any | Any | Misleading error message for ANALYZE against INFORMATION_SCHEMA tables |
85440 | 2017-03-14 10:58 | 2017-03-14 11:47 | MySQL Server: Information schema | Verified (2770 days) | S2 | 5.7.17 , 5.6.35 | Linux | Any | unusual values in enums subvert SHOW CREATE TABLE and DESCRIBE |
88385 | 2017-11-07 10:23 | 2018-10-18 12:37 | MySQL Server: Information schema | Verified (2524 days) | S3 | 5.7.20 | Ubuntu (17.10) | Any | Incorrect CHARACTER_MAXIMUM_LENGTH for LONGTEXT data type in information_schema |
92558 | 2018-09-25 12:02 | 2018-09-26 5:47 | MySQL Server: Information schema | Verified (2209 days) | S3 | 5.7.23, 8.0.12 | Any | Any | information_schema.innodb_trx trx_is_read_only not set for all RO transactions |
103872 | 2021-06-01 7:40 | 2021-06-02 8:17 | MySQL Server: Information schema | Verified (1229 days) | S2 | 8.0.25 | Any | Any | Window function result type not consistent with schema |
108715 | 2022-10-08 20:11 | 2022-10-17 4:19 | MySQL Server: Information schema | Verified (734 days) | S3 | 5.7, 8.0 | Any | Any | Mysql_field returns NUM_FLAG (32768) for grouped by columns |
116149 | 2024-09-18 16:25 | 2024-09-19 6:04 | MySQL Server: Information schema | Verified (24 days) | S3 | 8.0.39 | Any | Any | Inconsistent auto_increment values |
47420 | 2009-09-17 18:34 | 2013-03-03 20:45 | MySQL Server: Information schema | Verified (5444 days) | S3 | 5.1.38 | Any | Any | information_schema.plugins.PLUGIN_VERSION doesn't specify the full version |
92287 | 2018-09-04 17:50 | 2018-09-06 7:45 | MySQL Server: Information schema | Verified (2230 days) | S3 | 5.7.23, 5.6.41 | Linux (ubuntu 17.10) | x86 | Inconsistent value querying information_schema.statistics collation column |
41771 | 2008-12-27 23:28 | 2011-02-16 23:43 | MySQL Server: Information schema | Verified (5761 days) | S2 | 6.0.8-alpha | Windows (XPSP2) | Any | Can't retrieve data type attributes of routine parameters. |
71355 | 2014-01-12 17:22 | 2014-01-13 5:06 | MySQL Server: Information schema | Verified (3926 days) | S3 | 5.6 | Any | Any | Strange data type is used for name-related columns in some I_S.INNODB_* tables |
71312 | 2014-01-07 13:21 | 2014-01-08 12:27 | MySQL Server: Information schema | Verified (3931 days) | S3 | 5.6.15 | Any | Any | Weird warning for MERGE table while accessing I_S.REFERENTIAL_CONSTRAINTS |
113789 | 2024-01-29 9:35 | 2024-01-30 13:38 | MySQL Server: Information schema | Verified (258 days) | S3 | 8.0 | Any | Any | information_schema tables not accessible via Table Access Service |
98976 | 2020-03-17 15:35 | 2020-03-18 7:08 | MySQL Server: Information schema | Verified (1670 days) | S3 | 8.0.19, 5.7.29 | Debian (mysql:8.0.19 from Docker) | x86 | Case of referenced column of foreign key not corrected on import |
86930 | 2017-07-04 13:31 | 2017-07-11 19:14 | MySQL Server: Information schema | Verified (2658 days) | S3 | 5.6.29, 5.7.18 | Any | Any | Wrong results for queries with row constructors and information_schema |
99361 | 2020-04-26 16:48 | 2021-05-31 8:20 | MySQL Server: Information schema | Verified (1626 days) | S1 | MySQL 8.0, 8.0.19 | Debian (Debian 4.19.98-1 ) | Any ( Intel(R) Xeon(R) CPU @ 2.30GHz) | MySQL 8.0: select count(*) quey on information_schema.innodb_tables taking very |
76384 | 2015-03-19 8:41 | 2015-03-20 13:44 | MySQL Server: GIS | Verified (3495 days) | S2 | 5.6.19, 5.6.25, 5.7.8 | Any | Any | Spatial index not used when checking return values explicitly |
94560 | 2019-03-05 11:43 | 2019-03-07 4:30 | MySQL Server: GIS | Verified (2047 days) | S2 | 5.7, 8.0 | Any | Any | record comparison in spatial index non-leaf rtree node seems incorrect |
96963 | 2019-09-22 14:51 | 2019-09-23 16:43 | MySQL Server: GIS | Verified (1847 days) | S3 | 8.0, 5.7.27, 8.0.17 | Any | Any | gis function incompatible between 5.6 vs 8.0 |
107435 | 2022-05-31 13:06 | 2022-06-01 14:26 | MySQL Server: GIS | Verified (865 days) | S3 | Any | Any | It will return success from expr ST_GeomFromWKB with invalid wkb | |
92349 | 2018-09-10 9:22 | 2020-04-17 20:57 | MySQL Server: GIS | Verified (2210 days) | S2 | 8.0.12 | Any | Any | Storage Format is wrong regarding POINT data with SRID=2443-2461,6669-6687,30161 |
49826 | 2009-12-19 14:02 | 2011-02-16 23:44 | MySQL Server: General | Verified (5410 days) | S3 | any | Windows (any) | Any | MySQL installs a 'local system' not 'network service' |
47937 | 2009-10-09 9:11 | 2011-02-16 23:44 | MySQL Server: General | Verified (5483 days) | S5 | Any | Any | Appending to fields using CONCAT gets very slow | |
54121 | 2010-06-01 3:17 | 2011-02-16 23:44 | MySQL Server: General | Verified (5248 days) | S2 | M3 (Celosia), M4 (Dahlia), 6.0 | Any | Any | events_scheduling.test times out sporadically |
37292 | 2008-06-09 18:29 | 2013-03-03 20:45 | MySQL Server: General | Verified (5969 days) | S3 | 5.1.23-rc | Any | Any | KEY array passed into handler::add_index has incomplete information |
62077 | 2011-08-03 19:50 | 2014-05-28 9:24 | MySQL Server: General | Verified (4818 days) | S3 | 5.5.11, 5.5.16 | Any | Any | Assign date/time type to user-defined variable changes type/charset/collation |
27872 | 2007-04-17 6:26 | 2020-04-24 13:10 | MySQL Server: General | Verified (6226 days) | S3 | 5.0.37-community-log | Linux | Any | Incorrect error message when disk fills up running a large query against a view |
42705 | 2009-02-09 16:37 | 2011-02-16 23:43 | MySQL Server: General | Verified (5683 days) | S3 | 5.1.30 | Any | Any | Reduce malloc/free during query lifecycle. |
43427 | 2009-03-05 17:17 | 2012-03-18 18:41 | MySQL Server: General | Verified (5698 days) | S5 | 5.0 | Any | Any | Don't limit table_cache_size as a function of max_connections |
44636 | 2009-05-04 9:29 | 2011-02-16 23:43 | MySQL Server: General | Verified (5640 days) | S3 | all | Any | Any | sql_mode ORACLE should be more restrictive and contain more options |
55608 | 2010-07-28 16:06 | 2014-11-09 1:53 | MySQL Server: General | Verified | S3 | 5.5 | Any | Any | mysqld fails to start with --skip-innodb |
39066 | 2008-08-27 10:06 | 2011-02-16 23:43 | MySQL Server: General | Verified (5891 days) | S3 | 5.x, 6.0.x | MacOS | Any | Problems with setting variables with expression/functions |
40910 | 2008-11-20 22:34 | 2011-02-16 23:43 | MySQL Server: General | Verified (5753 days) | S2 | 4.1.22, 5.0.70, 5.1.22-rc, 5.1.30, 6.0.7 | Any (7.0) | Any | SELECT MAX(DATETIME) INTO @var yields LONGBLOB |
45801 | 2009-06-27 16:11 | 2022-12-04 20:45 | MySQL Server: General | Verified (5587 days) | S3 | 5.1.34 | Any | Any | str_to_date formats non-dates as dates instead of returning a null value |
43039 | 2009-02-20 1:14 | 2013-03-03 20:45 | MySQL Server: General | Verified (5708 days) | S1 | mysql-6.0.11, 5.1 | Any | Any | mysql_truncate() uses ha_resolve_by_legacy_type() |
53818 | 2010-05-19 17:31 | 2022-12-04 20:45 | MySQL Server: General | Verified (5254 days) | S3 | mysql-5.1 | Any | Any | Default values in .frm file not byte-order-independent |
31354 | 2007-10-02 20:30 | 2011-02-16 23:43 | MySQL Server: General | Verified | S3 | 5.0.46 | Any | Any | MySQL binds to port while executing init_file |
61979 | 2011-07-26 5:41 | 2016-10-04 7:10 | MySQL Server: General | Verified (4828 days) | S3 | 5.5.16 | Any | Any | MySQL 5.5 and PVS-Studio |
37805 | 2008-07-02 12:08 | 2011-02-16 23:43 | MySQL Server: General | Verified (5914 days) | S3 | 5.0+ | Any | Any | sql_load.cc: incorrect file type detection |
58224 | 2010-11-16 10:12 | 2012-05-18 20:19 | MySQL Server: General | Verified | S3 | 5.5 | Windows | Any | Assorted bugs in the VIO layer |
104690 | 2021-08-23 10:47 | 2021-08-25 0:30 | MySQL Server: Group Replication | Verified (1145 days) | S3 | 8.0.25, 8.0.26 | Any | Any | transaction cannot commit in AFTER consistencty mode when have unreachable node |
106032 | 2022-01-04 14:17 | 2022-01-21 6:47 | MySQL Server: Group Replication | Verified (997 days) | S3 | 8.0.27 Community Server | Debian (11.2) | x86 (HyperV) | MySQL uses up ram/swap after short member disconnect within innodb cluster |
116245 | 2024-09-26 15:23 | 2024-09-30 15:17 | MySQL Server: Group Replication | Need Feedback (13 days) | S2 | 8.0.36 | Red Hat ( 4.18.0-553.8.1.el8_10.x86_64) | x86 | innodb cluster / GR error after import w/ has_generated_invisible_primary_key=0 |
86956 | 2017-07-05 12:04 | 2017-08-25 10:48 | MySQL Server: Group Replication | Verified (2656 days) | S3 | 5.7.18 | Any | Any | Joining group timeout on permissions error |
110773 | 2023-04-23 7:56 | 2023-11-28 21:08 | MySQL Server: Group Replication | Verified (325 days) | S3 | mysql 8.0.32 | Any | Any | group_replication start faild use different ips and same port on same server |
91722 | 2018-07-20 3:08 | 2018-11-01 8:40 | MySQL Server: Group Replication | Verified (2252 days) | S1 | 5.7.22 | Any | Any | MGR may becomes a one-member-online system but still provide service |
82581 | 2016-08-15 10:21 | 2021-11-03 0:08 | MySQL Server: Group Replication | Verified (2834 days) | S1 | 5.7.14 | CentOS (7) | Any | altering table engine from innodb to memory will break group replication |
102249 | 2021-01-14 15:56 | 2021-01-27 17:40 | MySQL Server: Group Replication | Verified (1364 days) | S3 | 8.0.22 | Any | Any | Slow query log filling up with performance_schema queries |
75538 | 2015-01-17 19:54 | 2015-01-21 7:27 | MySQL Server: FULLTEXT search | Verified (3553 days) | S2 | 5.7, 5.7.6 | Windows (Windows 8) | Any | Multiple / Single phrase serach using Full Text In InnoDB is not working |
80579 | 2016-03-02 5:58 | 2016-03-02 6:33 | MySQL Server: FULLTEXT search | Verified (3147 days) | S3 | 5.6.29, 5.7.11 | CentOS | Any | Failing assertion: result != FTS_INVALID in file fts0fts.cc line 2209 |
78643 | 2015-09-30 10:44 | 2015-09-30 11:05 | MySQL Server: FULLTEXT search | Verified (3301 days) | S3 | 5.6.26, 5.6.28, 5.7.10 | CentOS (CentOS 7) | Any | InnoDB: Failing assertion: val <= 4294967295u in fts0vlc.ic line 96 |
87182 | 2017-07-25 8:27 | 2017-07-31 12:44 | MySQL Server: FULLTEXT search | Verified (2631 days) | S3 | 5.6.35 | Any | Any | Sporadic MATCH AGAINST results with unique index |
39640 | 2008-09-25 4:01 | 2013-03-03 20:45 | MySQL Server: FULLTEXT search | Verified (5489 days) | S3 | 5.1.26, 5.1.28, 6.0.6 | Any | Any | ftb_query_add_word does not recognice MYSQL_FTFLAGS_NEED_COPY |
60904 | 2011-04-18 8:10 | 2011-07-17 13:14 | MySQL Server: FULLTEXT search | Verified (4837 days) | S1 | 5.1.49, 5.1.59 | Any | Any | plugin of full text index has a string address error |
75763 | 2015-02-04 13:29 | 2015-02-05 8:19 | MySQL Server: FULLTEXT search | Verified (3538 days) | S2 | 5.6.21, 5.6.24 | Any | Any | InnoDB FULLTEXT index reduces insert performance by up to 6x on JSON docs |
80347 | 2016-02-12 5:02 | 2016-11-08 13:39 | MySQL Server: FULLTEXT search | Verified (2896 days) | S2 | 5.7.9, 5.7.11 | Any | Any | mysqldump backup restore fails due to invalid FTS_DOC_ID (Error 182 and 1030) |
82330 | 2016-07-25 5:55 | 2024-04-06 9:15 | MySQL Server: FULLTEXT search | Verified (190 days) | S1 | 5.7.13, 5.7.22, 8.0.16, 8.3.0 | CentOS (6.6) | Any | Don't recursively-evaluate stopword after tokenize |
108509 | 2022-09-16 0:17 | 2022-09-16 5:25 | MySQL Server: FULLTEXT search | Verified (758 days) | S2 | 8.0.21 | Any | Any | Return value of rbt_search() not get checked |
25508 | 2007-01-09 23:54 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified (6485 days) | S3 | 5.2.0 | Linux (SUSE 10.0 / 64-bit) | Any | Federated: Failure to Remove Partitioning |
30051 | 2007-07-25 18:40 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified (6283 days) | S3 | 5.0, 5.1 | Any | Any | CREATE TABLE does not connect and check existence of remote table |
65431 | 2012-05-27 2:59 | 2012-05-30 7:34 | MySQL Server: Federated storage engine | Verified (4522 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Error 1430 while selecting from a federated table with index on a bit column |
27180 | 2007-03-15 15:49 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified (6122 days) | S1 | mysql Ver 14.12 Distrib 5.0.24a | Linux (Linux Ubuntu) | Any | #1030 - Got error 1 from storage engine with big tables |
25571 | 2007-01-12 7:27 | 2013-03-03 20:45 | MySQL Server: Federated storage engine | Verified | S3 | 5.0.34-BK, 5.0.27 | Linux (Linux) | Any | EXPLAIN returns incorrect estimation of rows for federated table |
68572 | 2013-03-05 10:57 | 2014-02-19 16:19 | MySQL Server: Federated storage engine | Verified (4239 days) | S3 | 5.5.25a, 5.5.31 | Any | Any | FEDERATED using SHOW TABLE STATUS causes performance problems for InnoDB tables |
82959 | 2016-09-12 19:26 | 2016-09-13 0:03 | MySQL Server: Federated storage engine | Verified (2952 days) | S3 | 8.0.0 | Any | Any | Remove FEDERATED storage engine |
73219 | 2014-07-07 7:34 | 2014-07-07 7:34 | MySQL Server: Federated storage engine | Verified | S3 | 5.6.19 | Any | Any | cannot connect to federated table if table charset is utf16 |
78551 | 2015-09-25 6:33 | 2015-09-25 6:34 | MySQL Server: Federated storage engine | Verified | S3 | 5.6.26 | Any | Any | ER_CONNECT_TO_FOREIGN_DATA_SOURCE truncates the error message to 64 chars |
102659 | 2021-02-19 9:07 | 2021-02-19 17:29 | MySQL Server: Errors | Verified (1332 days) | S3 | 8.0 | Any | Any | Unhandled return value in MySQL-8.0.23 |
60583 | 2011-03-22 10:49 | 2011-03-22 13:51 | MySQL Server: Errors | Verified (4954 days) | S3 | 5.5.9 | Windows | Any | Unable to call user created functions from another schema |
97399 | 2019-10-28 14:27 | 2019-10-29 5:53 | MySQL Server: Errors | Verified (1811 days) | S3 | 8.0.16, 8.0.18, 5.7.28 | Any | Any | Bogus warning when using grant on localhost + skip-name-resolve |
72259 | 2014-04-07 6:42 | 2016-11-21 6:38 | MySQL Server: Errors | Verified (3841 days) | S1 | 5.6.16 | Linux (Red Hat 4 Tikanga) | Any | MySQL doesn't show informative error message for read-only filesystem in Linux |
105870 | 2021-12-11 19:40 | 2021-12-12 13:13 | MySQL Server: Errors | Verified (1036 days) | S3 | 8.0.27 | Linux | Any | Return error not get checked |
41749 | 2008-12-25 19:45 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (5770 days) | S3 | 5.1.30 | Windows (XP) | Any | No errors in server logfile when started with wrong errmsg.sys |
69547 | 2013-06-21 23:24 | 2013-06-24 22:09 | MySQL Server: Errors | Verified (4129 days) | S2 | 5.5 plus | Windows | Any | Documentation describes a parameter for mysqld that does not exist |
72217 | 2014-04-03 9:33 | 2023-09-05 16:16 | MySQL Server: Errors | Verified (3846 days) | S3 | 5.5, 5.6 | Any | Any | When uninstall a audit plugin, there is a warning info which is not correct |
80226 | 2016-02-01 22:28 | 2018-01-24 16:05 | MySQL Server: Errors | Verified (2454 days) | S3 | 5.5, 5.6, 5.7, 5.7.10, 8.0.4-rc | Any | Any | Result type check for SET GLOBAL fails unexpectedly |
47250 | 2009-09-10 13:16 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (5512 days) | S3 | 5.0.88,5.1.38,5.5.99-m3 | Any | Any | blackhole+fulltext search cause uneeded 'Got error 131 when reading table' |
84101 | 2016-12-08 6:46 | 2016-12-08 10:35 | MySQL Server: Errors | Verified (2866 days) | S3 | 5.5/5.6/5.7/8.0 | Linux | Any | inconsistent behavior for auto increment column when reaching max limit |
5931 | 2004-10-06 18:05 | 2017-11-11 18:37 | MySQL Server: Errors | Verified (7135 days) | S3 | 5.0.2-alpha-debug | Linux (SuSE 9.1) | Any | Traditional: FLOAT and DOUBLE out-of-range values are accepted |
34831 | 2008-02-26 12:25 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (6073 days) | S3 | 5.1.22, 4.1, 5.0, 5.1, 6.0 BK | Any | Any | Enumeration and some of the boolean variables can be assigned decimal values |
77029 | 2015-05-13 14:15 | 2015-05-14 12:43 | MySQL Server: Errors | Verified (3440 days) | S2 | 5.5.43-0+deb7u1-log, 5.6.24 | Linux | Any | Drop database fails with 'Database doesn't exists' whereas it exists |
77751 | 2015-07-16 20:14 | 2015-07-21 14:18 | MySQL Server: Errors | Verified (3372 days) | S3 | 5.5/5.6/5.7 | Any | Any | errmsg #1690: wrong field type |
81351 | 2016-05-09 9:26 | 2016-06-02 4:39 | MySQL Server: Document Store: MySQL Shell | Verified (3056 days) | S1 | 1.0.3 | Any | Any | switching session type from classic to JS fails |
81061 | 2016-04-13 8:27 | 2017-07-07 1:21 | MySQL Server: Document Store: X Plugin | Verified (3105 days) | S2 | 5.7.12 | Any | Any | Unable to use for loop with add() for adding documents inside mysqlsh-py |
85977 | 2017-04-18 2:02 | 2018-11-02 15:03 | MySQL Server: Documentation | Verified (2735 days) | S3 | 5.7 and 8.0 | Any | Any | The doc. of slave-parallel-type=LOGICAL_CLOCK wrongly reference Group Commit. |
88360 | 2017-11-04 11:40 | 2017-11-06 8:58 | MySQL Server: Documentation | Verified (2535 days) | S3 | 5.7.20 | Any | Any | Documentation about systemd and mysqld-debug is incomplete and wrong |
71146 | 2013-12-14 11:34 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (3954 days) | S3 | any | Any | Any | Manual does not explain when REPAIR or OPTIMIZE TABLE uses repair by sorting |
71189 | 2013-12-20 14:56 | 2021-08-08 20:45 | MySQL Server: Documentation | Verified (3950 days) | S3 | 5.5, any | Any | Any | Manual does not provide enough details on how loose index scan really works |
101654 | 2020-11-18 3:50 | 2020-11-18 5:46 | MySQL Server: Documentation | Verified (1425 days) | S3 | Any | Any | Update documentation to include missing binlog event types | |
110891 | 2023-05-03 10:50 | 2023-05-05 12:00 | MySQL Server: Documentation | Verified (527 days) | S3 | 8.0 | Any | Any | Documentation bug: CHAR vs VARCHAR |
92331 | 2018-09-07 6:29 | 2022-08-06 2:51 | MySQL Server: Documentation | In progress (799 days) | S3 | 8.0.12 | Any | Any | Document JSON numeric types and conversion rules |
110928 | 2023-05-05 10:59 | 2023-05-16 12:26 | MySQL Server: Documentation | Verified (516 days) | S3 | Any | Any | Documentation about NULL saving storage looks false | |
111984 | 2023-08-07 7:53 | 2024-08-16 16:31 | MySQL Server: Documentation | Verified (417 days) | S3 | 8.0, 8.1 | Any | Any | Typos and inconsistencies in the doxygen doc for the protocol |
97734 | 2019-11-21 14:19 | 2020-03-05 7:08 | MySQL Server: Documentation | Verified (1683 days) | S3 | 5.7.27 | Linux | x86 (x86_64) | Document the correct method to stop slaving with MTS without a warning or error |
102287 | 2021-01-19 3:07 | 2021-01-20 15:15 | MySQL Server: Documentation | Verified (1362 days) | S3 | 5.7, 8.0 | Any | Any | Miss some corner cases on Locking of DELETE FROM ... WHERE... |
108063 | 2022-08-03 14:58 | 2022-08-04 12:55 | MySQL Server: Documentation | Verified (801 days) | S3 | 8.0 | Any (CentOS7.9) | Any (Intel) | data volumes from previous mysql versions doesn't work with 8.0.30 |
108210 | 2022-08-22 2:24 | 2022-08-22 7:56 | MySQL Server: Documentation | Verified (783 days) | S2 | Any | Any | Description about LOCK_MODE is not accurate | |
108707 | 2022-10-07 11:47 | 2022-10-31 12:42 | MySQL Server: Documentation | Verified (737 days) | S3 | 8.0 | Any | Any | Clarify manual on Estimating Query Performance |
114221 | 2024-03-05 9:00 | 2024-03-05 10:56 | MySQL Server: Documentation | Verified (222 days) | S3 | 8.0 | Any | Any | The description of "Specifying a character set" is incorrect in Online DDL |
115778 | 2024-08-06 6:24 | 2024-08-07 7:17 | MySQL Server: DML | Verified (67 days) | S3 | 8.4.0, 8.0 | Any | Any | Cast DATE_ADD/SUB result as double get wrong result. |
30402 | 2007-08-14 8:35 | 2014-03-10 14:31 | MySQL Server: DML | Verified (4330 days) | S2 | 5.0.37 Community | Linux (RedHat 9.0) | Any | SELECT count(distinct) from mytable return 0 |
74448 | 2014-10-20 9:18 | 2014-10-24 8:10 | MySQL Server: DML | Verified (3646 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `table_share->tmp_table != NO_TMP_TABLE || m_lock_type != 2' failed |
74504 | 2014-10-22 12:09 | 2014-10-22 12:34 | MySQL Server: DML | Verified (3644 days) | S3 | 5.6.20-debug | Linux (CentOS 7) | Any | Assertion `map->bitmap && map2->bitmap && map->n_bits==map2->n_bits' failed |
74537 | 2014-10-24 6:53 | 2014-10-24 11:19 | MySQL Server: DML | Verified (3642 days) | S3 | 5.6.20-debug, 5.6.22 | Linux (CentOS 7) | Any | Assertion `lex.sphead == __null' failed in Table_triggers_list::check_n_load |
74779 | 2014-11-11 7:42 | 2016-07-29 10:37 | MySQL Server: DML | Verified (3624 days) | S3 | 5.6.20-debug, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion :bitmap_is_s et(&m_part_info->read_partitions, m_part_spec.start_part) |
74780 | 2014-11-11 9:15 | 2016-11-18 6:33 | MySQL Server: DML | Verified (3624 days) | S3 | 5.6.20-debug, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion `tab->ref.use_count' failed in join_read_key_unlock_row |
74946 | 2014-11-21 4:47 | 2014-11-23 9:19 | MySQL Server: DML | Verified (3614 days) | S3 | 5.6.20, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Assertion `nr >= 0.0' failed in virtual double Item_sum_std::val_real() |
75232 | 2014-12-16 9:11 | 2014-12-16 9:49 | MySQL Server: DML | Verified (3589 days) | S3 | 5.6.21, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Sig 6 abort in get_partition_id_range_for_endpoint | sql/sql_partition.cc:3600 |
75648 | 2015-01-27 10:04 | 2015-01-27 11:12 | MySQL Server: DML | Verified (3547 days) | S3 | 5.6.21-debug, 5.6.24, 5.7.6 | Linux (CentOS 7) | Any | Assertion `length <= max_data_length()' failed in Field_blob::store_to_mem |
76040 | 2015-02-25 7:31 | 2018-04-20 23:33 | MySQL Server: DML | Verified (3516 days) | S3 | 5.6.23, 5.6.25 | Linux (CentOS 7) | Any | Assertion `!flags.finalized' failed in sql/binlog.cc:1172 |
81191 | 2016-04-25 11:10 | 2016-09-02 16:26 | MySQL Server: DML | Verified (3092 days) | S3 | 5.7.11 | Windows | Any | CREATE TABLE ... SELECT caused ERROR 1114 while destination reached over 4 Gb |
83021 | 2016-09-16 10:02 | 2016-09-16 10:16 | MySQL Server: DML | Verified (2949 days) | S3 | 5.6.33, 5.5.52 | Any | Any | Assertion "buf != end" failed |
86471 | 2017-05-26 9:27 | 2017-05-26 12:31 | MySQL Server: DML | Verified (2697 days) | S3 | 5.7.18 | Ubuntu (Xenial) | Any | Assertion `! no_data(nbytes)' failed in void Geometry::wkb_parser::skip_unsafe |
87588 | 2017-08-29 17:17 | 2017-08-29 17:57 | MySQL Server: DML | Verified (2602 days) | S3 | 5.7/8.0 | Ubuntu | Any | Assertion `thd->lex->sql_com mand == SQLCOM_XA_COMMIT' failed |
88805 | 2017-12-07 8:40 | 2017-12-07 9:37 | MySQL Server: DML | Verified (2502 days) | S1 | 5.6.38 | Any | Any | Assertion `item_in->left_expr->cols() == 1' failed. |
90190 | 2018-03-23 8:26 | 2018-03-23 17:05 | MySQL Server: DML | Verified (2396 days) | S3 | 5.7.21/8.0 | CentOS | Any | Sig=6 assertion in MYSQL_BIN_LOG::new_file_impl | binlog.cc:6862 |
114218 | 2024-03-05 4:50 | 2024-03-05 7:01 | MySQL Server: DML | Verified (222 days) | S2 | 8.2.0, 8.3.0, 8.0.36 | Any | Any | Unexpected Results by MEMORY ENGINE |
66794 | 2012-09-13 2:39 | 2012-09-13 14:53 | MySQL Server: DML | Verified (4413 days) | S3 | 5.1.63/5.5.29 | Linux (Ubuntu 32bit) | Any | Column metadata inconsistent when used against a View |
71981 | 2014-03-08 20:24 | 2014-03-13 11:15 | MySQL Server: DML | Verified (3867 days) | S3 | 5.6.16 | Any | Any | Strange result on explain |
73552 | 2014-08-12 18:56 | 2014-08-18 19:47 | MySQL Server: DML | Verified (3709 days) | S2 | 5.5.8, 5.5.31, 5.5.34,5.6.20 | Any | Any | ('string' = CAST(0 as TIME)) produces bogus error "Illegal mix of collations" |
79505 | 2015-12-03 10:57 | 2015-12-03 12:09 | MySQL Server: DML | Verified (3237 days) | S3 | 5.7.8, 5.5.48, 5.6.29, 5.7.9 | Any | Any | "if(1,1,1.234)" return 1 while the "Decimals" is 3 |
79565 | 2015-12-09 7:11 | 2015-12-09 8:34 | MySQL Server: DML | Verified (3231 days) | S3 | 5.7.8,5.5.48, 5.6.29, 5.7.9 | Any | Any | Function insert work incorrectly with multiple-type utf8 character |
80775 | 2016-03-17 9:37 | 2016-03-23 8:51 | MySQL Server: DML | Verified (3126 days) | S3 | 5.6.24-72.2-log, 5.6.29, 5.7.11 | Ubuntu (14.04.4) | Any | "Out of range value for column XXX" in DML is missleading |
81876 | 2016-06-16 7:30 | 2016-06-20 11:09 | MySQL Server: DML | Verified (3037 days) | S3 | 5.5.50, 5.6.31, 5.7.13 | Linux | Any | neg op returns diff results |
82559 | 2016-08-12 3:08 | 2016-08-16 20:12 | MySQL Server: DML | Verified (2984 days) | S2 | 5.6, 5.7.14, 5.6.32 | Linux | Any | a bug about union with subquery |
83146 | 2016-09-26 7:39 | 2016-09-26 10:34 | MySQL Server: DML | Verified (2939 days) | S3 | 5.6, 5.7 | Linux | Any | time to bit produces inconsistent results |
83454 | 2016-10-20 8:09 | 2016-10-20 8:38 | MySQL Server: DML | Verified (2915 days) | S3 | 5.7 | Linux | Any | inconsistent results returned when compare enum with integer |
84055 | 2016-12-05 9:25 | 2016-12-05 14:17 | MySQL Server: DML | Verified (2869 days) | S3 | 5.6/5.7/8.0 | Linux | Any | inconsistent behavior for inserting default value to a column of enum type |
84342 | 2016-12-27 7:28 | 2016-12-27 11:58 | MySQL Server: DML | Verified (2847 days) | S3 | 5.7.17,5.6.33 | Any | Any | ORDER BY on BIT column results changes output display format |
84933 | 2017-02-10 3:22 | 2017-02-10 9:30 | MySQL Server: DML | Verified (2802 days) | S3 | 5.6 5.7, 5.6.35, 5.5.54 | Any | Any | same sql mode in 5.6 and 5.7 results in difference results |
91232 | 2018-06-13 11:11 | 2018-06-13 15:12 | MySQL Server: DML | Verified (2314 days) | S3 | 5.7/8.0 | MacOS | Any | json column wtih string value got incorrect result |
101718 | 2020-11-23 12:35 | 2020-11-24 5:16 | MySQL Server: DML | Verified (1420 days) | S5 | 8.0, 8.0.22 | Linux | Any | all new.x in before trigger marked in write_set may cause update use temp table |
108828 | 2022-10-19 13:39 | 2023-06-07 15:17 | MySQL Server: DML | Verified (724 days) | S2 | 8.0.28, 8.0.31 | Any | Any | error DB_UNDO_RECORD_TOO_BIG when update json column |
109149 | 2022-11-20 5:01 | 2023-12-05 4:04 | MySQL Server: DML | Verified (313 days) | S3 | 8.0.31, 5.7 | Ubuntu | x86 | The representation of 0 in MOD function in computing string |
109837 | 2023-01-30 12:24 | 2023-01-30 13:24 | MySQL Server: DML | Verified (622 days) | S3 | 8.0.31, 8.0.32, 5.7.41 | MacOS | x86 | The representation of 0 in division function in computing string |
113060 | 2023-11-13 10:23 | 2023-11-20 11:40 | MySQL Server: DML | Verified (335 days) | S3 | 8.0 | Any | Any | The result of avg(distinct xx)is different between from primary and secondary |
113366 | 2023-12-08 1:39 | 2023-12-08 8:06 | MySQL Server: DML | Verified (310 days) | S3 | 8.0.35 | Any | Any | Incorrect query results involving the date type. |
114312 | 2024-03-12 6:30 | 2024-03-19 2:26 | MySQL Server: DML | Verified (208 days) | S3 | 8.0 | Any | Any | Item_ref::used_tables wrong when ref to a rollup constant |
114333 | 2024-03-13 10:50 | 2024-03-13 16:33 | MySQL Server: DML | Verified (214 days) | S3 | 8.0 | Any | Any | Lead/lag window functions returning BLOB instead of VARCHAR |
116182 | 2024-09-20 13:39 | 2024-09-20 14:14 | MySQL Server: DML | Verified (23 days) | S3 | 9.0.1, 8.4.2, 8.0.39 | Any | Any | recursive CTE handling of decimal is unexpected |
116211 | 2024-09-24 8:14 | 2024-09-26 11:19 | MySQL Server: DML | Verified (19 days) | S3 | 9.0.1, 8.4.2, 8.0.39 | Any | Any | zero value of year does not display as 4 characters in union clause |
76355 | 2015-03-17 15:34 | 2015-03-17 16:33 | MySQL Server: DML | Verified (3498 days) | S3 | 5.6/5.7 | Linux | Any | Function "addtime" returns wrong column type (regression). |
81035 | 2016-04-12 1:57 | 2016-04-12 7:43 | MySQL Server: DML | Verified (3106 days) | S3 | 5.7.8, 5.5.49, 5.6.30, 5.7.12 | Any | Any | `NEWDECIMAL` result for ROUND() function is out of range of 65 digits |
83178 | 2016-09-28 2:28 | 2016-09-28 6:47 | MySQL Server: DML | Verified (2937 days) | S3 | 5.6, 5.6.33, 5.7.15 | Linux | Any | substring(binary, 3) return inconsistent results |
106597 | 2022-02-28 13:25 | 2022-03-01 7:21 | MySQL Server: DML | Verified (957 days) | S3 | 8.0.25, 8.0.28 | Any | Any | TIME type truncate error in 'in' function |
79849 | 2016-01-05 13:08 | 2016-02-08 10:09 | MySQL Server: DML | Verified (3170 days) | S2 | 5.6.23, 5.6.28, 5.7.10 | CentOS | Any | STR_TO_DATE function not working for numeric month (0...12) |
74646 | 2014-10-31 9:51 | 2014-10-31 10:27 | MySQL Server: DML | Verified (3635 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `((Item_result_field*)item)->result_field' failed in create_tmp_field |
76307 | 2015-03-13 3:46 | 2015-03-13 6:23 | MySQL Server: DML | Verified (3502 days) | S3 | 5.6.23, 5.6.25, 5.7.7, 5.5.44 | Linux (CentOS 7) | Any | Assertion `share->rows_recorded' failed in ha_tina::delete_row(const uchar*) |
60724 | 2011-04-01 16:19 | 2011-04-05 14:50 | MySQL Server: DML | Verified (4944 days) | S2 | 5.5.11, 5.5.10-log, 5.1.57, 5.0.93 | Any | Any | Unquoted date literal in comparison yields incorrect implicit conversion |
78415 | 2015-09-12 6:17 | 2015-09-12 9:50 | MySQL Server: DML | Verified (3319 days) | S3 | 5.6.22, 5.6.26, 5.7.9 | Any | Any | Equivalent SQL like "select cast( varchar as decimal)" returns different results |
90089 | 2018-03-15 12:57 | 2018-03-15 17:36 | MySQL Server: DML | Verified (2404 days) | S2 | 5.5/5.6/5.7/8.0 | Linux | Any | Year type column have index , between operate sql , the result is wrong . |
90265 | 2018-03-30 19:05 | 2018-04-10 17:27 | MySQL Server: DML | Verified (2382 days) | S3 | 5.7.21, 5.6.39 | Any | Any | Inconsistency in size truncating when converting to a smaller string data_type |
11472 | 2005-06-21 0:08 | 2024-04-09 10:03 | MySQL Server: DML | Verified (5841 days) | S2 | 5.0.8/5.5/5.6/5.7 | Any | Any | Triggers not executed following foreign key updates/deletes |
25620 | 2007-01-15 6:54 | 2020-05-03 20:45 | MySQL Server: DML | Verified (6157 days) | S3 | 5.0.33 | Windows (Windows Server 2003 Web Edition) | Any | Error in ADDTIME function when update more 35 days |
79409 | 2015-11-25 10:45 | 2015-11-30 8:11 | MySQL Server: DML | Verified (3240 days) | S3 | 5.7.8, 5.7.9, 5.5.48, 5.6.29 | Any | Any | compare type for datetime column and varchar column is inconsistent with doc |
81508 | 2016-05-19 13:22 | 2016-05-20 8:52 | MySQL Server: DML | Verified (3068 days) | S3 | 5.7.8, 5.7.12, 5.6.30 | Any | Any | Type in meta data for "cast('a' as char(100))" is VAR_STRING |
99005 | 2020-03-20 11:31 | 2020-03-20 12:17 | MySQL Server: DML | Verified (1668 days) | S2 | 5.6/5.7/8.0 | Any | Any | Flags of column-type-info is different |
105983 | 2021-12-27 9:42 | 2023-03-14 14:02 | MySQL Server: DML | Verified (1021 days) | S2 | 8.0.26, 8.0.27, 5.7.36 | MacOS | Any | `SELECT GREATEST(time '20:00:00', 120000) + 0.00` should return 20 |
106533 | 2022-02-22 2:05 | 2022-02-25 13:52 | MySQL Server: DML | Verified (964 days) | S3 | 8.0.25, 5.7,8.0 | Any (rhel 7.4) | Any | The time type cannot be handled in the `in` statement |
107287 | 2022-05-13 10:16 | 2022-05-15 9:08 | MySQL Server: DML | Verified (884 days) | S3 | 8.0.28, 8.0.29, 5.7.38 | Any | Any | CASE operator does not follow standard equality |
113368 | 2023-12-08 3:10 | 2023-12-08 8:01 | MySQL Server: DML | Verified (310 days) | S3 | 5.7.44-log, 8.0 | Any | Any | IN() has a problem handling when the expression on the left is of type time |
113446 | 2023-12-18 2:32 | 2023-12-18 7:59 | MySQL Server: DML | Verified (300 days) | S3 | 8.0.33 | Any | Any | Query with DISTINCT and ORDER BY on BIT data type returns wrong result |
90140 | 2018-03-20 13:28 | 2018-03-20 15:39 | MySQL Server: DML | Verified (2399 days) | S3 | 5.7.21-debug | Any | Any | mysql-5.7.21 coredump on ut0ut.cc ine942 |
77164 | 2015-05-27 5:10 | 2015-05-27 13:29 | MySQL Server: DML | Verified (3427 days) | S3 | 5.6.21, 5.6.26, 5.6.24 | Linux (CentOS 7) | Any | Assertion : mtr_memo_contains(mtr, block, 2) == rw_lock_own(&block->lock, 351) |
75640 | 2015-01-27 4:50 | 2015-01-27 7:58 | MySQL Server: DML | Verified (3547 days) | S3 | 5.6.21-debug, 5.6.24 | Linux (CentOS 7) | Any | Failing assertion: array->n_elems < array->max_elems in sync_thread_add_level |
74759 | 2014-11-10 7:29 | 2014-11-10 8:55 | MySQL Server: DML | Verified (3625 days) | S3 | 5.6.20-debug | Linux (CentOS 7) | Any | Failing assertion: lock_rec_get_first(receiver, receiver_heap_no) == __null |
74664 | 2014-11-03 7:03 | 2016-09-09 2:34 | MySQL Server: DML | Verified (3632 days) | S3 | 5.6.20-debug, 5.5.41, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion: len <= col->len || col->mtype==5 || (col->len == 0 && col->mtype ==1) |
77289 | 2015-06-10 2:49 | 2015-06-10 7:11 | MySQL Server: DML | Verified (3413 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 |
80681 | 2016-03-10 7:24 | 2016-03-11 8:07 | MySQL Server: DML | Verified (3138 days) | S3 | 5.7.11 | CentOS | Any | Failing assertion: len <= fixed_len in in file rem0rec.cc line 886 |
77108 | 2015-05-21 4:52 | 2015-05-21 6:38 | MySQL Server: DML | Verified (3433 days) | S3 | 5.6.23, 5.6.26 | Linux (CentOS 7) | Any | InnoDB: Failing assertion: index == cursor->index in btr0sea.cc line 1782 |
74747 | 2014-11-08 7:20 | 2015-02-05 7:55 | MySQL Server: DML | Verified (3538 days) | S1 | 5.6.20, 5.6.22, 5.7.5 | Any | Any | Failing assertion: index->id == btr_page_get_index_id(page) btr0cur.cc line 899 |
74678 | 2014-11-04 8:28 | 2014-11-04 9:07 | MySQL Server: DML | Verified (3631 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `host_length <= 60' failed in set_setup_actor_key |
76844 | 2015-04-27 5:50 | 2015-04-27 6:53 | MySQL Server: DML | Verified (3457 days) | S3 | 5.6.23, 5.6.25 | Linux (CentOS 7) | Any | handle_fatal_signal (sig=6) in trx_commit_low | trx/trx0trx.cc:1365 |
92036 | 2018-08-16 7:49 | 2018-08-17 11:52 | MySQL Server: DML | Verified (2249 days) | S3 | 8.0.12 | Any | Any | InnoDB: Assertion failure: api0api.cc:3163:!sdi_delete_failed |
74641 | 2014-10-31 1:31 | 2014-10-31 14:42 | MySQL Server: DML | Verified (3635 days) | S1 | 5.6.20, 5.6.21 | Any | Any | my_seek.c:57: my_seek: Assertion `fd != -1' failed. Table corruption on opt |
104628 | 2021-08-15 23:37 | 2021-08-20 12:26 | MySQL Server: DML | Verified (1150 days) | S3 | 8.0 | Any | Any | Unused assignment in MySQL-8.0.23 |
97038 | 2019-09-26 13:58 | 2021-04-19 9:52 | MySQL Server: DML | Verified | S3 | 5.7, 8.0 | Any | Any | Column metadata of a table and a view created from similar SELECT is not same |
76925 | 2015-05-04 10:37 | 2015-05-04 11:20 | MySQL Server: DML | Verified (3450 days) | S3 | 5.6.23, 5.6.25 | Linux (CentOS 7) | Any | handle_fatal_signal (sig=11) in ha_innobase::store_key_val_for_row |
74480 | 2014-10-21 11:44 | 2018-01-01 3:30 | MySQL Server: DDL | Verified (3324 days) | S1 | 5.6.20-debug,5.6.26, 5.6.27, 5.6.28, 5.7.8 and 5.7.9 | Linux (CentOS 7) | Any | Failing assertion: os_file_status(newpath, &exists, &type), os0file.cc line 1950 |
73326 | 2014-07-18 11:31 | 2014-07-18 11:59 | MySQL Server: DDL | Verified (3740 days) | S2 | all, 5.6.20 | Any | Any | Behavior when using a non-permitted index type. |
74762 | 2014-11-10 11:49 | 2014-11-10 12:40 | MySQL Server: DDL | Verified (3625 days) | S3 | 5.6.20-debug, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Failing assertion: thr_get_trx(thr)->error_state == DB_SUCCESS. |
109033 | 2022-11-09 3:43 | 2022-11-17 9:37 | MySQL Server: DDL | Verified (699 days) | S2 | 5.7.39 | Any | Any | Contribution by Tencent: crash after ha_commit_inplace_alter_table is unsafe |
75083 | 2014-12-03 8:49 | 2014-12-03 11:56 | MySQL Server: DDL | Verified (3602 days) | S3 | 5.6.20, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | handle_fatal_signal (sig=6) in retrieve_auto_increment | myisam/mi_key.c:588 |
95227 | 2019-05-02 19:56 | 2019-05-15 20:32 | MySQL Server: DDL | Verified (1990 days) | S3 | 5.7.24 | CentOS | x86 | JSON columns in a UNION get changed into longtext |
74887 | 2014-11-17 4:29 | 2014-11-17 6:36 | MySQL Server: DDL | Verified (3618 days) | S3 | 5.6.21, 5.6.23, 5.7.6 | Linux (CentOS 7) | Any | Failing assertion: trx_get_dict_operation(trx) == TRX_DICT_OP_INDEX |
110872 | 2023-04-30 2:06 | 2023-05-04 11:32 | MySQL Server: DDL | Verified (529 days) | S3 | 8.0 | Any | Any | Unable to create indexes concurrently on the same table |
72427 | 2014-04-22 22:06 | 2014-09-09 8:05 | MySQL Server: DDL | Verified (3688 days) | S1 | 5.5.16 | Any | Any | Crash during ALTER TABLE may lead to non-usable table |
22632 | 2006-09-23 20:45 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (6577 days) | S3 | 5.1.11-beta | Linux (linux) | Any | SHOW CREATE TABLE is inconsistent in showing unsupported options |
79151 | 2015-11-06 9:10 | 2016-07-05 8:59 | MySQL Server: DDL | Verified (3022 days) | S2 | 5.6.27, 5.7.11 | Any | Any | error -1 from storage engine while creating table with non-existing datadir |
83898 | 2016-11-21 6:44 | 2016-11-21 7:16 | MySQL Server: DDL | Verified (2883 days) | S3 | 5.6.34 | Any | Any | ERROR 1030 (HY000): Got error -1 from storage engine |
112660 | 2023-10-09 2:21 | 2023-10-09 8:52 | MySQL Server: DDL | Verified (370 days) | S3 | 8.1.0, 8.0.34 | Linux | Any | Got error -1 - 'Unknown error -1' from storage engine |
116175 | 2024-09-20 8:35 | 2024-09-23 14:24 | MySQL Server: DDL | Verified (20 days) | S3 | all | Any | Any | The declaration of dd_set_autoinc is repeated. |
76467 | 2015-03-23 23:26 | 2015-03-24 8:04 | MySQL Server: DDL | Verified (3491 days) | S1 | 5.6.22, 5.6.23, 5.6.25 | Any | Any | Assertion `strlen(db) <= (64*3) && strlen(name) <= (64*3)' failed. DROP FUNCTION |
38434 | 2008-07-29 19:15 | 2012-05-18 20:19 | MySQL Server: DDL | Verified (5912 days) | S1 | 5.0.51b-community-nt MySQL Community Ed, 5.0, 5.1 BZR | Any (Linux, MS Windows xp) | Any | unique key index length |
10992 | 2005-05-31 16:17 | 2017-11-13 0:44 | MySQL Server: DDL | Verified (6437 days) | S3 | 4.1.13, 5.1.52 | Any | Any | MyISAM foreign key definitions create indexes |
63962 | 2012-01-08 20:10 | 2012-01-09 14:05 | MySQL Server: DDL | Verified (4662 days) | S3 | 5.1.61 | Any | Any | CREATE SERVER still not converting hostnames to lower case |
74603 | 2014-10-28 11:33 | 2014-10-28 11:50 | MySQL Server: DDL | Verified (3638 days) | S3 | 5.6.20-debug/5.7 | Linux (CentOS 7) | Any | Assertion `comma_length > 0' failed in mysql_prepare_create_table |
74606 | 2014-10-28 15:56 | 2014-10-29 9:58 | MySQL Server: DDL | Verified (3637 days) | S3 | 5.6.20-debug, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `thd->transaction.stmt.is_empty()' failed in close_mysql_tables |
75003 | 2014-11-26 2:45 | 2014-11-26 9:53 | MySQL Server: DDL | Verified (3609 days) | S3 | 5.6.21, 5.6.23 | Linux (CentOS 7) | Any | Assertion `bitmap_is_set_all(&table->s->all_set)' failed int handler::ha_reset() |
75079 | 2014-12-03 5:50 | 2014-12-08 11:54 | MySQL Server: DDL | Verified (3597 days) | S3 | 5.6.21, 5.6.23, 5.6.22, 5.7.6 | Linux (CentOS 7) | Any | Assertion `!do_checksum || remains == 0' failed in MYSQL_BIN_LOG::do_write_cache |
81367 | 2016-05-10 13:42 | 2016-05-10 14:18 | MySQL Server: DDL | Verified (3078 days) | S2 | 5.7.12 | Any | Any | Irrelevant error message altering table engine -> The table '#sql-9ae_5' is full |
85065 | 2017-02-20 2:56 | 2017-03-02 8:00 | MySQL Server: DDL | Verified (2782 days) | S2 | 5.7.17 | Any | Any | CREATE EVENT not OOM safe |
92760 | 2018-10-12 7:09 | 2018-10-12 7:39 | MySQL Server: DDL | Verified (2193 days) | S3 | 8.0, 5.7.23 | Any | Any | Cannot alter InnoDB table to MyISAM if table definition has encryption='N' text |
93409 | 2018-11-29 16:43 | 2018-11-30 5:30 | MySQL Server: DDL | Verified (2144 days) | S3 | 5.7.24 | Any | Any | disabled_storage_engines does not catch partition engines |
102306 | 2021-01-20 6:36 | 2021-01-20 6:54 | MySQL Server: DDL | Verified (1362 days) | S1 | 8.0 | Any | Any | Improper locking in alter_part_normal::try_commit |
109194 | 2022-11-24 15:08 | 2022-11-25 7:01 | MySQL Server: DDL | Verified (688 days) | S3 | 8.0.31 | Ubuntu (22.04) | x86 (x86_64) | Inexistent secondary_engine ignored |
112661 | 2023-10-09 6:29 | 2023-10-09 8:52 | MySQL Server: DDL | Verified (370 days) | S3 | 8.1.0, 8.0.34 | Linux | Any | Got 'Unknown error -1' when create index on table |
27175 | 2007-03-15 14:48 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (6045 days) | S3 | 5.0.38 4.1.23 | Linux (Linux) | Any | invalid colum attributes in create/alter table |
37130 | 2008-06-01 20:11 | 2018-09-09 20:45 | MySQL Server: DDL | Verified | S3 | 5.0.44 | Any | Any | Extra index is added to column when making SERIAL column PK. |
73299 | 2014-07-16 14:59 | 2014-07-18 9:26 | MySQL Server: DDL | Verified (3740 days) | S2 | 5.6.19, 5.6.20 | Any | Any | DEFAULT value for PRIMARY KEY column depends on the way to declare it PRIMARY |
79645 | 2015-12-15 9:02 | 2015-12-15 11:16 | MySQL Server: DDL | Verified (3225 days) | S3 | 5.7.8, 5.5.48, 5.6.28,5.7.10 | Any | Any | On column property, when both 'NOT NULL' and 'NULL' specified, no error throws |
81010 | 2016-04-08 10:34 | 2020-01-24 10:45 | MySQL Server: DDL | Verified (3107 days) | S3 | 5.7.11, 5.6.29, 8.0.17 | Windows | Any | ALTER TABLE DROP DEFAULT - default value of NULL not forced |
82419 | 2016-08-03 9:21 | 2016-08-03 9:54 | MySQL Server: DDL | Verified (2993 days) | S3 | 5.6, 5.7, 5.7.14 | Any | Any | Supplementary unicode characters accepted for schema object names |
95233 | 2019-05-03 1:46 | 2020-03-23 4:54 | MySQL Server: DDL | Verified (1665 days) | S3 | 8.0.16 | Any | Any | check constraint doesn't consider IF function that returns boolean a boolean fun |
105090 | 2021-09-30 17:23 | 2021-09-30 18:26 | MySQL Server: DDL | Verified (1109 days) | S3 | 5.7.35 | Any | x86 | FK cannot be created when the table has a UNIQUE KEY in a virtual generated col |
113416 | 2023-12-14 7:34 | 2023-12-14 8:38 | MySQL Server: DDL | Verified (304 days) | S2 | 8.2.0 | Any | Any | Contribution by Tencent: replaying rename space ddl log fails |
113507 | 2023-12-25 4:04 | 2023-12-25 10:34 | MySQL Server: DDL | Verified (293 days) | S3 | 8.0.35 | Any | Any | gipk add column failed |
111178 | 2023-05-29 3:33 | 2024-04-10 7:28 | MySQL Server: DDL | Verified (503 days) | S2 | 8.0.25, 8.0.33, 8.3.0 | Any | Any | Unable to set the secondary engine |
39413 | 2008-09-11 23:26 | 2022-12-04 20:45 | MySQL Server: DDL | Verified (5875 days) | S3 | 5.0, 5.1, 6.0 bzr | Any | Any | Incorrect AUTO_INCREMENT value allowed |
48228 | 2009-10-22 13:17 | 2013-04-16 15:15 | MySQL Server: DDL | Verified | S2 | 5.0.88, 5.1.31, 5.1.41 | Any | Any | UNIQUE_KEY_FLAG not respected for multiple columns in unique key |
105295 | 2021-10-22 12:24 | 2021-10-22 15:46 | MySQL Server: DDL | Verified (1087 days) | S3 | 8.0.27 | Any | x86 | Type of COALESCE(1, FALSE) was INT, but MySQL8.0.27 is decimal(1,0). |
45196 | 2009-05-29 14:26 | 2012-05-18 20:19 | MySQL Server: DB2SE for IBM i | Patch pending (5585 days) | S3 | 5.1.33 | Any | Any | Some collations do not sort correctly with IBMDB2I |
110194 | 2023-02-23 14:06 | 2023-04-03 16:54 | MySQL Server: Data Dictionary | Verified (559 days) | S3 | 8.0.23, 8.0.30, 8.0.32 | Any | Any | DD upgrade leaves dictonary tables in temporary schema dd_upgrade_targets_80030 |
111286 | 2023-06-05 22:05 | 2023-06-06 12:35 | MySQL Server: Data Dictionary | Verified (495 days) | S3 | 8.0.33 | Any | Any | SDI has incorrect types for DB_TRX_ID and DB_ROLL_PTR fields |
111616 | 2023-06-29 6:19 | 2023-06-30 7:40 | MySQL Server: Data Dictionary | Verified (471 days) | S2 | 8.0.32 | Any | Any | Failed to upgrade from 5.7 to 8.0 because of spatial column with BTREE index |
89544 | 2018-02-06 4:16 | 2018-03-09 5:42 | MySQL Server: Data Dictionary | Verified (2438 days) | S3 | 8.0.4 | Any | Any | LeakSanitizer errors on failed server startup due to DD engine init fail |
71091 | 2013-12-05 12:52 | 2013-12-06 11:15 | MySQL Server: CSV | Verified (3964 days) | S3 | 5.5.33, any, 5.6.15, 5.5.35 | Any | Any | CSV engine does not properly process "", in quotes |
34612 | 2008-02-15 19:49 | 2013-03-03 20:45 | MySQL Server: CSV | Verified (5497 days) | S2 | 5.0,5.1.22 | Other (i5/OS v5r4 PASE) | Any | CSV storage engine does not honor time_zone |
55907 | 2010-08-11 8:39 | 2013-03-03 20:45 | MySQL Server: CSV | Verified (5177 days) | S3 | 5.1, 5.6.99 | Any | Any | CSV Engine seems to have changed format of numeric handling |
106852 | 2022-03-28 12:38 | 2022-04-11 2:00 | MySQL Server: Connection Handling | Verified (916 days) | S2 | 8.0.28 | Windows (Windows 11 Pro (build 22000.556)) | x86 (x64) | Cannot connect using named pipe on windows if the connection was the first |
115783 | 2024-08-06 12:38 | 2024-08-07 9:34 | MySQL Server: Connection Handling | Verified (68 days) | S3 | 8.4 | Any | Any | Valgrind error on test_services suite tests |
83151 | 2016-09-26 14:27 | 2021-09-14 10:08 | MySQL Server: Connection Handling | Verified (2090 days) | S2 | 5.6.33 | CentOS | Any | high number of SHOW WARNINGS can stall server if compressed protocol in use |
76688 | 2015-04-14 13:47 | 2015-07-06 11:54 | MySQL Server: Compiling | Analyzing (3387 days) | S1 | 5.6.24, 5.7.7-rc | Linux (CentOS 7) | Any | -DMYSQL_DATADIR impact on compiling MySQL with cmake |
97777 | 2019-11-26 0:44 | 2019-11-29 13:51 | MySQL Server: Compiling | Verified (1780 days) | S5 | 5.7.28 | Linux (or any ELF platform) | Any | separate global variables (from hot variables) using linker script (ELF) |
60872 | 2011-04-14 15:22 | 2011-04-20 9:11 | MySQL Server: Compiling | Verified (4925 days) | S1 | 5.1, 5.5 | Any | Any | cmake-based build system declares DBUG_OFF/DBUG_ON in CFLAGS instead of headers |
64477 | 2012-02-27 21:20 | 2012-03-06 9:10 | MySQL Server: Compiling | Verified (4611 days) | S3 | 5.5.23 | Linux (Ubuntu 11.10) | Any | Can't build 5.5 on Ubuntu with systemtap-sdt-dev installed |
100868 | 2020-09-16 13:22 | 2020-09-16 21:09 | MySQL Server: Compiling | Verified (1488 days) | S3 | 8.0.21 | Windows (Windows 10 2004) | x86 | Can't build mysqlx plugin on Visual Studio 2019 |
71680 | 2014-02-12 11:00 | 2014-02-12 11:24 | MySQL Server: Compiling | Verified (3896 days) | S3 | 5.6.16 | Any | Any | Incomplete fix of "Bug #11765975 __FILE__ macros expanded to full path ..." |
83196 | 2016-09-29 3:35 | 2018-02-23 0:44 | MySQL Server: Compiling | Verified (2936 days) | S3 | 8.0.0 | Linux (ubuntu-16.04) | ARM | buf0buf.ic:1171:51: compile error=logical-op - with -DCMAKE_BUILD_TYPE=Debug |
115471 | 2024-07-01 5:04 | 2024-07-04 8:23 | MySQL Server: Compiling | Verified (101 days) | S3 | 8.0.37, 8.4.0 | MacOS (14.5) | ARM | Linker errors with enabled LTO |
93105 | 2018-11-07 12:34 | 2018-11-13 11:17 | MySQL Server: Compiling | Verified (2161 days) | S3 | 8.0.13, 5.7.24 | Linux | Any | writing to ‘struct buf_buddy_free_t’ with no trivial copy-assignment |
112022 | 2023-08-10 1:56 | 2023-08-10 7:38 | MySQL Server: Compiling | Verified (430 days) | S3 | 8.0.34 | CentOS (CentOS Linux 7) | x86 | Compiling with -DWITH_DEBUG=1 and using C++17 resulted in a failure. |
98241 | 2020-01-15 21:40 | 2020-01-20 11:56 | MySQL Server: Compiling | Verified (1728 days) | S3 | 8.0.19 | Ubuntu | Any | unused variable p in storage/innobase/include/univ.i |
81285 | 2016-05-02 17:07 | 2016-05-04 12:52 | MySQL Server: Compiling | Verified (3084 days) | S2 | 5.5.49 | CentOS (5.11 32-bit) | Any | Cannot build 5.5.49 on CentOS 32-bit with arch=i686 |
108389 | 2022-09-05 16:16 | 2022-09-06 13:01 | MySQL Server: Compiling | Verified (768 days) | S2 | 8.0.30 | SUSE (OpenSUSE 15.4) | ARM | Cannot compile with Performance schema disabled |
113426 | 2023-12-14 17:21 | 2023-12-15 7:35 | MySQL Server: Compiling | Verified (303 days) | S3 | mysql-trunk | Oracle Linux | x86 | using -DWITH_INNODB_EXTRA_DEBUG results in compilation error |
113270 | 2023-11-29 0:18 | 2023-11-29 10:34 | MySQL Server: Compiling | Verified (319 days) | S3 | 8.0.35 | Any | Any | Unable to compile 8.0.35 with DISABLE_PSI_THREAD |
87348 | 2017-08-08 17:00 | 2017-08-09 6:46 | MySQL Server: Compiling | Verified (2622 days) | S2 | 5.7.19 | Any | Any | Client build fails since CMakeLists.txt references missing storage/ndb directory |
115279 | 2024-06-11 7:10 | 2024-06-11 11:52 | MySQL Server: Compiling | Verified (124 days) | S3 | 8.0.37 | Any | Any | Warning about YYSTYPE in mysql-8.0.37 |
58402 | 2010-11-22 19:55 | 2011-07-17 13:11 | MySQL Server: Compiling | Verified (4837 days) | S3 | 5.1.53, 5.1.59 | Linux | Any | ut/ut0ut.c compilation errors |
56522 | 2010-09-02 22:47 | 2012-05-18 20:19 | MySQL Server: Compiling | Verified (5122 days) | S1 | 5.5-bugfixing | Any | Any | Compiler warnings in mysys/lf_hash.c |
80466 | 2016-02-22 5:04 | 2016-02-22 13:02 | MySQL Server: Compiling | Verified (3156 days) | S3 | 5.7.10 | Solaris (Sparc, 11.3) | Any | Accessing uninitialized memory os0file.h Encryption(const Encryption&) ~357 |
111432 | 2023-06-15 8:56 | 2023-06-16 13:42 | MySQL Server: Compiling | Verified (485 days) | S3 | mysql-8.0.33 | Ubuntu (22.04.2) | x86 | c++ Undefined Behavior with clang-16 |
55729 | 2010-08-04 6:46 | 2011-02-16 23:44 | MySQL Server: Compiling | Verified (5184 days) | S3 | Any | Any | Enable -Wconversion in maintainer mode on gcc > 4.3 | |
80463 | 2016-02-22 4:13 | 2016-02-22 13:01 | MySQL Server: Compiling | Verified (3156 days) | S3 | 5.7.10 | Solaris (Sparc, 11.3) | Any | Accessing uninitialized memory include/mach0data.ic mach_read_from_1() ~75 |
83033 | 2016-09-18 15:41 | 2020-03-24 1:00 | MySQL Server: Compiling | Verified (2946 days) | S3 | 8.0.0 | Any | Any | CMake docs say -DMUTEX_TYPE, sources -DMUTEXTYPE |
53622 | 2010-05-13 17:02 | 2011-02-16 23:44 | MySQL Cluster: Replication | Verified (5256 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | null bitmask read incorrectly in mysqlbinlog |
52473 | 2010-03-30 12:51 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (5286 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | NDB inserts row when updating slave's empty table (with PK) |
39500 | 2008-09-17 15:35 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified | S2 | mysql-5.1-telco-6.3 | Linux | Any | mysqld core in ha_ndbcluster::add_row_check_if_batch_full_size() |
33160 | 2007-12-12 8:19 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (6037 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Didn't check data type of conflict_fn column when creating mysql.ndb_replication |
33440 | 2007-12-21 5:51 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (6037 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Conflict info not correct with wrong column type in exception table |
48934 | 2009-11-20 9:17 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (5200 days) | S2 | mysql-5.1-telco-7.0, 7.1.4b | Linux | Any | Delete from table; 3600 rows not replicated from MASTER to SLAVE |
55888 | 2010-08-10 15:41 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (5176 days) | S2 | mysql-5.1 | Any | Any | ndb table binlogged as transactional table when ndb_use_transactions=0 |
33412 | 2007-12-20 16:29 | 2021-05-02 20:45 | MySQL Cluster: Replication | Verified (6037 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Didn't limit the storage engine for exception table |
66386 | 2012-08-14 17:51 | 2012-08-14 22:44 | MySQL Cluster: Packaging | Verified (4443 days) | S2 | 7.2.7 | Windows (Windows 7 64-bit) | Any | MySQL Cluster Installs the Windows Service incorrectly |
80565 | 2016-02-29 20:26 | 2017-08-23 11:34 | MySQL Cluster: Packaging | Verified (3148 days) | S3 | 5.7.11 | Any | Any | Minified javascript files in source tarball |
88010 | 2017-10-06 13:56 | 2017-10-30 1:04 | MySQL Cluster: plugin | Verified (2542 days) | S1 | Windows | Any | Unable to add new node under existing cluster from different machine | |
69935 | 2013-08-06 8:09 | 2014-09-26 21:54 | MySQL Cluster: Memcached | Verified (3670 days) | S3 | MySQL Cluster 7.3.0, 7.3.1, 7.3.2, 7.4.1 | Linux (Ubuntu 13.04) | Any | ndbmemcached built with bundled memcached but not with bundled libevent fails |
75293 | 2014-12-22 18:31 | 2017-02-24 19:18 | MySQL Cluster: Memcached | Verified (3561 days) | S2 | 7.3.2+, 7.3.7, 7.5.5 | Linux (CentOS 6/7) | Any | Memcached Process at 100% CPU |
69920 | 2013-08-03 23:17 | 2014-09-26 21:44 | MySQL Cluster: Memcached | Verified (3670 days) | S3 | MySQL Cluster 7.3.1, 7.3.2, 7.4.1 | Linux | Any | Can't build ndb memcached engine against unbundled default memcached installatio |
69936 | 2013-08-06 9:00 | 2014-09-26 21:07 | MySQL Cluster: Memcached | Verified (3670 days) | S2 | MySQL Cluster 7.3.1, 7.3.2, 7.4.1 | Linux | Any | MySQL Cluster 7.3.x bundles memcached source twice -> please merge |
38193 | 2008-07-17 11:13 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified (5932 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | Weird error message when trying to alter cluster table to STORAGE MEMORY |
43241 | 2009-02-26 17:54 | 2021-05-02 20:45 | MySQL Cluster: Disk Data | Verified | S3 | mysql-5.1-telco-6.3 | Any | Any | Inconsistancy in warnings on create table / create tablespace with unknown engin |
60579 | 2011-03-22 7:50 | 2013-01-14 9:28 | MySQL Cluster: Disk Data | Verified (4290 days) | S2 | ndb-7.1.8 | Linux | Any | Storage node fails to restart after watchdog issue |
14243 | 2005-10-23 19:45 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6501 days) | S3 | mysql-5.0 | Linux (Linux) | Any | Statistics on MySQL cluster |
31390 | 2007-10-04 8:50 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5976 days) | S3 | mysql-5.1-telco-7.0 | Solaris | Any | ERROR 1296 (HY000) at line 24: Got error 744 'Character string is invalid |
31723 | 2007-10-19 20:29 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6144 days) | S3 | mysql-5.1 | Linux | Any | ndb_restore giving wrong backup file version information |
38161 | 2008-07-16 8:01 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5910 days) | S3 | mysql-5.1 | Linux (Debian 2.6.18) | Any | Triggers can't handle ERROR 1296 (HY000) when cluster is down |
41594 | 2008-12-18 16:29 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5778 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | Not connectng to the Cluster should not keep MySQL demon from starting |
43857 | 2009-03-25 13:05 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5617 days) | S1 | mysql-5.1-telco-7.0 | Solaris (SunOS 5.10 Generic_138888-01 sun4v sparc SUNW,Sun-Fire-T200) | Any | Cluster crash during heavy load |
46061 | 2009-07-08 21:09 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | In progress (5507 days) | S1 | mysql-5.1-telco-7.0 | Windows (XP) | Any | Cluster with more than 8 MySql/API nodes |
51222 | 2010-02-16 22:09 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S2 | mysql-5.1-telco-7.0 | Any | Any | Assert in DBDICT after restore |
53440 | 2010-05-05 15:41 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5040 days) | S1 | mysql-5.1-telco-7.0 | Linux (x86_64 2.6.18-53.1.21.el5 #1 SMP) | Any | erratic index when bringing data node online into a working cluster |
55964 | 2010-08-13 6:50 | 2011-02-16 23:44 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5175 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Small race condition in output log writing |
77349 | 2015-06-14 20:06 | 2016-09-02 16:22 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3408 days) | S2 | 5.6.2x | Any | Any | Missing Sanity Check for malloc() in mgmapi.cpp |
84197 | 2016-12-13 23:55 | 2017-07-17 4:55 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S3 | 7.5.4 | Any | Any | UndoIndexBuffer and UndoDataBuffer should be removed from mgmsrv |
41514 | 2008-12-16 15:28 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5749 days) | S3 | mysql-5.1-telco-6.3 | Linux (2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux) | Any | ndb_print_schema_file segfaults and documentation is lacking |
42833 | 2009-02-13 14:38 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5721 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | ndb_restore segfault when there is an error |
44330 | 2009-04-16 21:22 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5652 days) | S2 | mysql-5.1-telco-7.0 | Any | Any | ndb-connection-pool set higher then NDB API slots makes db appear corrupt |
84651 | 2017-01-24 20:07 | 2017-01-31 5:16 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2812 days) | S3 | 7.5.5 | Linux (x64) | Any | unable to start ndbmtd after upgrade |
18138 | 2006-03-10 15:56 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6501 days) | S1 | mysql-5.0 | Linux (RHE 3.0) | Any | FORCE INDEX is ignored when using NDB tables |
18865 | 2006-04-06 19:29 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6501 days) | S3 | mysql-4.1 | Linux (Linux) | Any | Table definitions "stay" even after a ndbd --initial |
35148 | 2008-03-07 16:15 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5578 days) | S2 | mysql-5.0 | Any | Any | Error '4009 Cluster Failure' in various tests on various platforms |
54178 | 2010-06-02 10:34 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5247 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | SHOW CREATE TABLE does not show column format FIXED/DYNAMIC if set implicitly |
72929 | 2014-06-10 6:58 | 2014-12-08 8:22 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3597 days) | S1 | 5.6.17-ndb-7.3.5-cluster-gpl-log, 7.3.7 | Linux (Red Hat Enterprise Linux Server release 6.2 (Santiago)) | Any | Ndb kernel thread is stuck in: Job Handling for about 18s caused data node crash |
114516 | 2024-03-30 20:23 | 2024-04-09 14:51 | MySQL Cluster: Cluster (NDB) storage engine | Verified (193 days) | S1 | 8.0.31 | Any | x86 | ndbmtd with useSHM failing with Signal 6 received; Aborted |
38315 | 2008-07-23 16:00 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5578 days) | S3 | mysql-5.0 | Any (Solaris 10 x86, linux) | Any | "Cluster Failure" in ps_7ndb |
26955 | 2007-03-08 10:10 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (6429 days) | S3 | mysql-5.1-telco-6.2 | Any | Any | <id> RESTART of management server fails |
44540 | 2009-04-29 13:34 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5638 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | NDBD restart |
49458 | 2009-12-04 13:58 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5424 days) | S2 | mysql-5.1-telco-7.0 | Any | Any | Restart types listed by ndb_config are not consistent with the documentation |
55645 | 2010-07-30 9:16 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S3 | mysql-5.1-telco-7.0 | Any | Any | LIKE search is slow using varbinary indexes on cluster |
65032 | 2012-04-19 8:40 | 2013-01-05 6:03 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4299 days) | S3 | 7.2.5 | Linux (2.6.32) | Any | Misleading error shown while trying to ALTER TABLE |
82474 | 2016-08-05 13:04 | 2018-08-06 8:52 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2260 days) | S3 | mysql-cluster-7.2.14, probably all | Linux | Any | Cluster log truncates long messages |
83596 | 2016-10-28 8:06 | 2016-11-21 13:51 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2883 days) | S2 | 5.6.27-ndb-7.4.8-cluster-gpl | CentOS (CentOS release 6.4) | Any | select with group_concat will resturn wrong result of bit fields |
80915 | 2016-03-31 0:38 | 2016-09-08 6:03 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2957 days) | S2 | 5.6.28-ndb-7.4.10-cluster-gpl | Oracle Linux | Any | Foreign key not created if unique constraint not defined when using SQLAlchemy |
108773 | 2022-10-14 8:30 | 2022-10-31 12:56 | MySQL Cluster: Cluster (NDB) storage engine | Verified (727 days) | S2 | 8.0.31 | Linux (Amazon Linux 2022) | x86 (AWS r6i) | Query causes mysql to hang at 'preparing' and query cannot be stopped. |
44760 | 2009-05-09 9:06 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S2 | mysql-5.1-telco-6.3 | Any | Any | Cardinality is wrong on key in ndbcluster table |
52653 | 2010-04-07 11:05 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | In progress (5086 days) | S3 | mysql-5.1-telco-6.3 | Any | Any | Record size have changed from 8052B to 8048B |
53223 | 2010-04-27 20:41 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5282 days) | S3 | mysql-5.1-telco-7.1 | Any | Any | Config parameter Nodegroup should have restart type system |
55090 | 2010-07-08 16:55 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified | S3 | Any | Any | ndb query faster with ORDER BY than without | |
45912 | 2009-07-02 13:02 | 2012-05-18 20:19 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5508 days) | S1 | mysql-5.1 | Linux (Ubuntu Jaunty) | Any | "stack smashing" in ndbd |
91028 | 2018-05-25 14:26 | 2019-02-14 7:31 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2068 days) | S1 | 7.4.13 | Any | Any | NDB data node fails and crashes with SIGFPE, floating point exception |
44817 | 2009-05-12 8:24 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4000 days) | S3 | mysql-5.1-telco-6.3 | Linux | Any | Error 157 still reported as "unknown error code" by server |
79179 | 2015-11-09 1:31 | 2020-11-08 13:13 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3261 days) | S2 | 7.4.7 | CentOS (6.5 x64) | Any | bit data type was not full supported by MySQL cluster |
60261 | 2011-02-26 0:59 | 2016-11-12 22:57 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2892 days) | S5 | mysql-cluster-gpl-7.1.9a | Any | Any | Are transaction hints needed in these situation? |
69063 | 2013-04-25 8:32 | 2013-04-25 13:59 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4189 days) | S2 | 7.3.1 m2 | Windows (Server 2008 R2 64-bit) | Any | ndbd does not propagate failure status when run as windows service |
70460 | 2013-09-28 15:17 | 2016-12-30 9:20 | MySQL Cluster: Cluster (NDB) storage engine | Verified (4033 days) | S2 | 5.6.11-ndb-7.3.2-cluster-gpl-log | Linux (CentOS release 6.4 (Final)) | Any | Mysql Cluster and constraints |
35901 | 2008-04-08 12:43 | 2014-10-22 16:09 | MySQL Cluster: Cluster (NDB) storage engine | Verified (3644 days) | S1 | mysql-5.1 | Linux (redhat enterprise 4 x86_64) | Any | ndbd gives malloc error when starting up with SharedGlobalMemory > 1012M |
47120 | 2009-09-04 5:37 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Need Merge (5338 days) | S3 | mysql-5.1-telco-7.0 | Any | Any | ErrorReporter::formatMessage overruns the buffer |
49574 | 2009-12-10 8:05 | 2021-05-02 20:45 | MySQL Cluster: Cluster (NDB) storage engine | Verified (5420 days) | S3 | mysql-5.1-telco-7.0 | Linux | Any | undefined reference to ... libwrap problem |
114777 | 2024-04-25 7:09 | 2024-05-08 10:47 | MySQL Cluster: Cluster (NDB) storage engine | Verified (158 days) | S2 | 8.0.35-cluster MySQL Cluster Community S | Any (20.04) | Any | lost connection in MySQL NDB cluster |
107446 | 2022-06-01 13:42 | 2022-06-01 14:28 | MySQL Server: Clone Plugin | Verified (865 days) | S3 | 8.0 | Any | Any | Incorrect clone COM_EXIT command error handling logic |
107715 | 2022-06-30 14:07 | 2024-07-09 12:58 | MySQL Server: Clone Plugin | Verified (96 days) | S2 | 8.0.29-8.0.32 | Any | Any | Multiple SE clone not calling clone_end after mixed clone_begin failure/success |
109934 | 2023-02-04 12:26 | 2023-02-07 9:45 | MySQL Server: Clone Plugin | Verified (615 days) | S3 | 8.0.32 | Linux (Ubuntu 22.04) | x86 | Configuring a MySQL innodb cluster with MySQL Shell failed in Docker container |
76215 | 2015-03-09 1:57 | 2015-03-11 12:48 | MySQL Server: Charsets | Verified (3504 days) | S3 | 5.5.44, 5.6.25 | Any | Any | Implicit casts to string by COLLATE don't use character_set_connection |
42307 | 2009-01-23 16:21 | 2011-02-16 23:43 | MySQL Server: Charsets | Verified (5737 days) | S3 | 6.0 | Linux | Any | ctype_ujis_ucs2.test fails for falcon, innodb, maria (wrong warnings or errors) |
77993 | 2015-08-08 9:27 | 2017-09-18 7:26 | MySQL Server: Charsets | Verified (3354 days) | S3 | 5.6.26, 5.7.8 | CentOS (CentOS 7) | Any | handle_fatal_signal (sig=6) in my_mbcharlen_utf16 | /strings/ctype-ucs2.c:1421 |
68531 | 2013-03-01 2:42 | 2013-03-04 14:16 | MySQL Server: Charsets | Verified (4241 days) | S3 | 5.5.31 | Any | Any | incorrect interpret single digits in time values |
72715 | 2014-05-21 22:39 | 2014-05-22 8:02 | MySQL Server: Charsets | Verified (3797 days) | S3 | 5.6.17 | Any | Any | character set code endianness dependent on CPU type rather than endianness of CP |
74449 | 2014-10-20 9:39 | 2014-10-20 10:44 | MySQL Server: Charsets | Verified (3646 days) | S3 | 5.5.40, 5.6.21, 5.7.5, 5.6.22 | Linux (CentOS 6.3) | Any | Incorrect datetime casting with charcter_set_connection=sjis |
86233 | 2017-05-09 3:22 | 2020-04-27 16:24 | MySQL Server: Charsets | Verified (1630 days) | S3 | 8.0 | Any | Any | NVARCHAR should default to utf8mb4 |
114086 | 2024-02-21 19:41 | 2024-02-26 11:05 | MySQL Server: Charsets | Verified (230 days) | S3 | 8.0 | Any | Any | Item_singlerow_subselect::store may lead to memory corruption |
114830 | 2024-05-01 0:51 | 2024-05-02 8:35 | MySQL Server: Charsets | Verified (164 days) | S3 | 8.0 | Any | Any | MySQL converts collection of date data type in ibd but data dictionary |
43707 | 2009-03-17 16:29 | 2011-02-16 23:43 | MySQL Server: Charsets | Verified | S3 | 6.0.10, 5.6 | Linux (2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:56:28 EST 2006 x86_64 x86_64 x86_64 GNU/Linux) | Any | Columns in general_log and slow_log changed to "longtext" during upgrade |
86251 | 2017-05-10 2:43 | 2017-05-10 6:11 | MySQL Utilities: Binlog Events | Verified (2713 days) | S1 | 5.7.17, 5.7.18 | Any | Any | Assertion `head->variables.gtid_next.type == ANONYMOUS_GROUP' failed. |
92070 | 2018-08-19 22:16 | 2018-08-25 6:13 | MySQL Utilities: Binlog Events | Verified (2241 days) | S1 | 8.0.12 | Any | Any | Assertion `thd->variables.gtid_next.type == AUTOMATIC_GTID' failed. |
72495 | 2014-04-30 19:55 | 2024-04-25 7:51 | MySQL Utilities: Binlog Events | Verified (3816 days) | S3 | 5.6.16, 8.0 | Linux | Any | mysqlbinlog doesn't properly read GIS columns |
37103 | 2008-05-30 13:55 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5323 days) | S3 | 6.0 | Any | Any | mysql.online_backup.username is ambiguous |
91996 | 2018-08-13 17:37 | 2018-08-13 18:27 | MySQL Server: Archive storage engine | Verified (2253 days) | S3 | Any | Any | Contribution: Configurable compression level for archive storage engine | |
48343 | 2009-10-27 9:09 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5465 days) | S3 | 5.1.41-bzr | Any | Any | Wrong locking for Archive tables leads to broken statement replication. |
82580 | 2016-08-15 8:56 | 2016-08-16 6:13 | MySQL Server: Archive storage engine | Verified (2980 days) | S3 | 5.7.12, 5.6.19, 5.7.14 | Linux | Any | MySQL Docu does not reflect that archive SE support partitioning |
113305 | 2023-12-01 8:13 | 2023-12-11 10:31 | MySQL Server: Archive storage engine | Verified (317 days) | S3 | 8.0 | Linux | Any | Ambiguous error messages 'Unknown error -1' from storage engine |
69086 | 2013-04-26 19:17 | 2013-04-26 20:29 | MySQL Server: Archive storage engine | Verified (4188 days) | S3 | 5.1-debug, 5.5-debug, 5.6-debug | Any | Any | Assertion `fd != -1' fails in my_seek on REPAIR of a corrupted ARCHIVE table |
37648 | 2008-06-26 0:48 | 2013-03-03 20:45 | MySQL Server: Archive storage engine | Verified (5927 days) | S2 | 5.1.25 | Linux (CentOS 5) | Any | Changing storage engine to ARCHIVE in 5.1 loses data if disk fills up |
60348 | 2011-03-04 20:14 | 2013-01-15 15:25 | MySQL Server | Verified (4289 days) | S5 | 5.1.55 | Any | Any | trim trailing spaces processes data only byte wise (continue of bug14637 (2)) |
60349 | 2011-03-04 21:20 | 2013-01-15 15:25 | MySQL Server | Verified (4289 days) | S5 | 5.1.55 | Any | Any | trim beginning spaces processes data only byte wise (continue of bug14637 (3)) |
48899 | 2009-11-19 10:55 | 2011-02-16 23:44 | MySQL Server | Verified (5442 days) | S3 | 5.0, all | Any | Any | storage requirement for non-MyISAM poorly documented and 'instrumentated' |
60351 | 2011-03-04 22:15 | 2013-01-15 15:27 | MySQL Server | Verified (4289 days) | S5 | 5.1.55 | Any | Any | trim same character processes data only byte wise (continue of bug14637 (4)) |
24762 | 2006-12-01 21:41 | 2011-02-16 23:43 | MySQL Server | Verified (5468 days) | S1 | 4.1.20,5.0.60,5.1.38,5.1.40 | Linux (CentOS,Mac OSX) | Any | Failure to import data (timestamp) |
44943 | 2009-05-19 4:35 | 2011-02-16 23:43 | MySQL Server | Verified (5626 days) | S3 | 5.1.34, 4.1, 5.0, 5.1, 6.0 bzr | Any (NT) | Any | ORDER BY on SHOW INDEXES |
44372 | 2009-04-20 20:17 | 2013-03-03 20:45 | MySQL Server | Verified (5553 days) | S3 | 5.1.30, 5.1 bzr | Any | Any | bug 22125 affects handler::index_next_same in 5.1 |
46089 | 2009-07-09 15:09 | 2011-02-16 23:44 | MySQL Server | Verified (5571 days) | S3 | 5.1.30, 5.0, 5.4 | Any | Any | .frm file uses 2 bytes to store key flags, KEY structure uses 4. |
49895 | 2009-12-23 16:27 | 2013-03-03 20:45 | MySQL Server | Verified (5408 days) | S2 | 5.1.36, 5.1 bzr | Any (add_index) | Any | use of KEY_PART_INFO->fieldnr inconsistent in handler::create and add_index |
53561 | 2010-05-11 12:20 | 2016-10-16 20:45 | MySQL Server | Verified (5266 days) | S3 | 5.1.46, 5.5 | Any | Any | HA_EXTRA_WRITE_CAN_REPLACE does not work with row based replication |
45689 | 2009-06-23 19:37 | 2011-02-16 23:44 | MySQL Server | Verified (5589 days) | S3 | 4.1, 5.0, 5.1 bzr | Any | Any | SESSION 'interactive_timeout' variable is useless |
46945 | 2009-08-26 20:10 | 2011-02-16 23:44 | MySQL Server | Verified (5515 days) | S2 | 4.1, 5.0, 5,1, next bzr | Any | Any | enable filesort index rebuild for SPATIAL index |
77050 | 2015-05-15 14:17 | 2015-05-22 15:01 | MySQL Server | Verified (3436 days) | S3 | 5.6.24, 5.6.26, 5.7.8 | Any | Any | Syntax error if index type specified |
47582 | 2009-09-24 7:11 | 2022-12-04 20:45 | MySQL Server | Verified (4128 days) | S3 | 5.1, 5.5 | Windows (XP Russian, Bulgarian) | Any | main.perror-win fails on non-English versions of Windows |
34907 | 2008-02-27 21:23 | 2011-02-16 23:43 | MySQL Server | Verified (5472 days) | S3 | 5.1.22 | Any | Any | Handlers cannot replace the plugin variable update func for thread vars |
72286 | 2014-04-09 8:49 | 2014-04-10 15:51 | MySQL Server | Verified (3840 days) | S3 | 5.6+ | Any | Any | server-system-variables.html and "Dynamic variable" setting is incomplete |
91241 | 2018-06-13 15:35 | 2020-09-22 5:41 | MySQL Router | Verified (2309 days) | S3 | 8.0.11 | CentOS (6) | x86 | mysqlrouter init script doesn't show syntax errors in config file |
108849 | 2022-10-21 17:09 | 2022-11-04 2:19 | MySQL Router | Verified (710 days) | S3 | 8.0.31 | Any | Any | mysqlrouter bootstrap without password not working / incorrectly prompting |
108917 | 2022-10-28 13:33 | 2022-11-03 14:44 | MySQL Router | Verified (713 days) | S3 | 8.0.31 | Any | Any | bootstrapping mysqlrouter with certificate authentication issues |
92647 | 2018-10-03 3:46 | 2018-10-04 5:06 | MySQL Router | Verified (2201 days) | S2 | 8.0.12-1 | CentOS (6) | x86 | Unable to natively increase default number of open file descriptors. |
30506 | 2007-08-20 10:11 | 2024-02-04 20:45 | MySQL Proxy: Scripts | Verified | S2 | 0.6.0 | Any | Any | Proxy handles multi-statements queries in its core, but not in scripts |
66556 | 2012-08-27 19:15 | 2012-12-18 19:05 | MySQL Proxy: Core | Verified (4317 days) | S2 | 0.8.2, 0.8.3 | Linux | Any | Connection attempts alternately fail |
48570 | 2009-11-05 14:27 | 2012-05-18 20:19 | MySQL Proxy | Patch queued (5116 days) | S2 | 0.8 | Solaris (10-intel x86) | Any | Hangs on Solaris 10 if backend is down. |
35942 | 2008-04-09 15:59 | 2024-02-04 20:45 | MySQL Proxy | Verified (5788 days) | S2 | 0.6.1 , rev 511 | Any (SunOS 5.11 NexentaOS_20080131 i86pc i386 i86pc Solaris - Linux) | Any | MySQL-Proxy with rw-splitting.lua writes to slave because of SQL_CALC_FOUND_ROWS |
65023 | 2012-04-18 14:14 | 2012-04-19 19:35 | MySQL Proxy | Verified (4560 days) | S1 | mysql-proxy-0.8.2 | Windows (Windows Server 2008 R2) | Any | MySQL Proxy Does not start |
65782 | 2012-07-01 18:08 | 2012-07-04 9:57 | MySQL Websites: MySQLForge | Verified (4486 days) | S2 | MacOS (Tried from Safari browser and Firefox browser) | Any | Unable to login | |
74547 | 2014-10-24 11:33 | 2015-06-22 13:14 | MySQL Utilities | Verified (3401 days) | S3 | 1.5.2, 1.6.0-1 | Any | Any | mysqlserverinfo tries to access error log on the client instead of on the serve |
78342 | 2015-09-05 20:53 | 2017-02-10 6:06 | MySQL Utilities | Verified (2802 days) | S2 | 1.5.4 | CentOS | Any | mysqlrpladmin fails with complaint about unrelated GRANT during switchover |
80210 | 2016-01-31 19:57 | 2016-02-01 8:00 | MySQL Utilities | Verified (3177 days) | S2 | 1.5.6 | CentOS | Any | Unable to use mysqldbexport: "Error: Missing gtid_executed system variable" |
81218 | 2016-04-28 9:02 | 2016-09-10 9:10 | MySQL Utilities | Verified (2955 days) | S3 | 1.6.3, 1.6.4 | Any | Any | MySQL Utilities should not depend on MySQL (login-paths) |
82877 | 2016-09-06 21:32 | 2017-01-20 7:27 | MySQL Utilities | Verified (2847 days) | S3 | 1.6.4 | CentOS | Any | mysqlfailover daemon stops when unable to get health/gtid/uuid data |
88376 | 2017-11-06 20:19 | 2019-06-15 7:11 | MySQL Utilities | Verified (2531 days) | S2 | 1.6.5-1 | CentOS (7) | Any | ImportError: No module named utilities.common.tools ; Unable to use mysqlfrm |
88772 | 2017-12-06 4:59 | 2017-12-06 6:34 | MySQL Utilities | Verified (2503 days) | S3 | 1.6.5 | Any | Any | mysqldbcopy copying constraint fails with hyphenated database name |
85178 | 2017-02-24 17:54 | 2017-04-05 14:18 | MySQL Workbench: SQL Editor | Verified (2748 days) | S3 | 6.3.6, 6.3.9 | MacOS (10.12.4 Beta (16E163f)) | Any | Unable to set table when exporting data from a JOIN |
84211 | 2016-12-15 8:19 | 2016-12-15 9:30 | MySQL Workbench: SQL Editor | Verified (2859 days) | S5 | 6.3.8 | Windows (Microsoft Windows 10 Home) | Any | Autocomplete Feature |
99940 | 2020-06-20 2:15 | 2021-06-01 3:58 | MySQL Workbench: SQL Editor | Verified (1557 days) | S3 | 8.0.16 | Any | Any | Stored Procedure Call parameter filling not working |
102827 | 2021-03-05 13:57 | 2021-03-09 13:32 | MySQL Workbench: SQL Editor | Verified (1314 days) | S1 | 8.0.23 | Windows (Microsoft Windows 10 Enterprise) | Any | beautifying SQL script |
54262 | 2010-06-06 2:26 | 2018-06-24 20:45 | MySQL Workbench: SQL Editor | Verified (4521 days) | S2 | 5.2.22, 5.2.40 | Windows (revision 6091) | Any | Unable to view the routine when clicking on alter routine |
73442 | 2014-07-31 0:21 | 2015-11-24 22:47 | MySQL Workbench: SQL Editor | Verified (3723 days) | S3 | 6.1.6, 6.1.7 | MacOS (10.9.4) | Any | Unable to close query tab while executing query |
75109 | 2014-12-04 22:56 | 2018-06-28 10:34 | MySQL Workbench: SQL Editor | Verified (3596 days) | S5 | 6.2.3 | Windows (Microsoft Windows 7 Enterprise Service Pack 1) | Any | Workbench Freezes while running longer queries |
59274 | 2011-01-04 10:41 | 2012-05-18 20:19 | MySQL Workbench: SQL Editor | Verified (4877 days) | S2 | 5.2.31 | Windows (7) | Any | Crash when edit value in Editor |
73085 | 2014-06-23 23:30 | 2015-07-26 7:48 | MySQL Workbench: SQL Editor | Verified (3763 days) | S3 | 6.1.6 | Any | Any | Result Grid's Data Import to include more types, like Data Export |
79712 | 2015-12-20 11:26 | 2022-07-13 11:55 | MySQL Workbench: SQL Editor | Verified (3220 days) | S3 | 6.3.5/6.3.6 | Windows (Microsoft Windows 7 Ultimate Service Pack 1) | Any | Image tab in the BLOB editor is missing, only Binary and Text present. |
80564 | 2016-02-29 20:10 | 2018-05-24 15:25 | MySQL Workbench: SQL Editor | QA review (2334 days) | S3 | 6.3.6 (Workbench) | MacOS (10.9.5 (mysql version 5.7.11-Community Edition)) | Any | Saved procedure entered parameters ignored, zeros incorrectly entered by script |
80933 | 2016-04-01 14:26 | 2021-08-18 12:43 | MySQL Workbench: SQL Editor | Verified (3114 days) | S3 | 6.3, 6.3.6, 8.0 | Windows | Any | Error updating BIT column value to 0 (false) |
84977 | 2017-02-14 7:30 | 2018-05-30 21:00 | MySQL Workbench: SQL Editor | Verified (2783 days) | S3 | 6.3.9 | MacOS | Any | Backticks are not visible when typing |
84999 | 2017-02-14 17:34 | 2019-03-06 11:18 | MySQL Workbench: SQL Editor | Verified (2796 days) | S2 | 6.3.9 | Windows (Microsoft Windows 10 Pro) | Any | Resultset Row Height don't adjust to 'ResultSetGrid Font' setting |
97111 | 2019-10-05 19:44 | 2019-10-15 8:16 | MySQL Workbench: SQL Editor | Verified (1825 days) | S3 | 6.3.8, 8.0.18 | Linux (Ubuntu 18.04.3 LTS) | Any | MySQL Workbench doesn't know the type of a UDF result |
99417 | 2020-05-02 11:13 | 2020-11-19 18:07 | MySQL Workbench: SQL Editor | Verified (1623 days) | S2 | 8.0.19-1ubuntu18.04, 8.0.20 | Debian (10 Buster) | x86 (64bit) | MySQL Workbench: Unresponsive several minutes after each "use DB" statement |
114501 | 2024-03-28 1:38 | 2024-03-28 3:36 | MySQL Workbench: SQL Editor | Verified (199 days) | S3 | 8.0.36 | Windows (Windows 11 Pro 23H2) | x86 (AMD Ryzen 9 5950X 16-Core Processor ) | MySQL Workbench fail to open a exiting table after adding a virtual column |
77418 | 2015-06-19 19:56 | 2017-03-18 3:08 | MySQL Workbench: Modeling | Verified (3404 days) | S5 | 6.3.4 | MacOS (OS X 10.10.x Yosemite) | Any | EER: Differences in data-type lengths between Forward Engineer and Sync Model |
78786 | 2015-10-09 13:13 | 2015-10-09 15:58 | MySQL Workbench: Modeling | Verified (3292 days) | S2 | 6.34.0 | MacOS | Any | BINARY column inserts can't be forward engineered |
111745 | 2023-07-13 10:53 | 2023-09-21 13:15 | MySQL Workbench: Modeling | Verified (388 days) | S3 | 8.0.33 | Windows (Microsoft Windows 10 Pro) | Any | POINT SRID 4326 not supported |
82081 | 2016-07-01 9:33 | 2018-03-13 7:14 | MySQL Workbench: Modeling | Verified (2522 days) | S3 | 6.3.10 | Any | Any | json type cannot be dealt well in synchronize |
84606 | 2017-01-23 9:55 | 2017-01-23 10:07 | MySQL Workbench: Modeling | Verified (2820 days) | S3 | 6.3.8 | Any | Any | can not reverse engineering a table which has JSON data type fileds |
84908 | 2017-02-09 13:42 | 2017-07-11 14:52 | MySQL Workbench: Modeling | Verified (2743 days) | S1 | 6.3.9 | Linux ( x86_64) | Any | Workbench crash with message: locale::facet::_S_create_c_locale name not valid |
95592 | 2019-06-01 20:34 | 2019-06-06 5:53 | MySQL Workbench: Modeling | Verified (1956 days) | S3 | 8.0.16 | Any | Any | Malformed Comment Syntax breaks Synchronize Model |
96496 | 2019-08-10 1:13 | 2019-08-12 12:22 | MySQL Workbench: Modeling | Verified (1889 days) | S3 | 8.0.17 | Windows (Microsoft Windows 7 Professional Service Pack 1) | Any | Changed user defined type name is not apdating on ERD diagram. |
98405 | 2020-01-26 18:05 | 2020-12-20 16:34 | MySQL Workbench: Modeling | Verified (1690 days) | S3 | 8.0.19 | Linux (LinuxMint 19.3 x86_64) | x86 | Unreadable tooltip colors on tables |
101273 | 2020-10-22 11:40 | 2020-10-22 11:52 | MySQL Workbench: Modeling | Verified (1452 days) | S3 | 8.0.22 | Windows | x86 | Geometry collection fields break MySQL Workbench |
101704 | 2020-11-21 5:02 | 2020-11-21 7:48 | MySQL Workbench: Modeling | Verified (1422 days) | S3 | 8.0.22 | Windows (Microsoft Windows 10 Pro) | x86 | JSON type in CAST() and CONVERT() is recognized as error in model editors |
96898 | 2019-09-17 7:38 | 2021-01-08 7:32 | MySQL Workbench: Modeling | Verified (1853 days) | S2 | 8.0.16/8.0.17,8.0.22 | Windows (Microsoft Windows 10 Enterprise) | Any | EER Diagram mouse hovering on table couldn't show detail |
85456 | 2017-03-15 7:53 | 2018-02-13 10:31 | MySQL Workbench: Modeling | Verified (2769 days) | S2 | 6.3.9 | Windows (10 pro, 64b) | Any | Workbench Error:Table Filter in Forward Engineer to Database |
108080 | 2022-08-05 12:28 | 2022-12-08 11:04 | MySQL Workbench: Modeling | Verified (675 days) | S3 | 8.0.29, 8.0.31 | Linux (Ubuntu 22.04 x86_64) | Any | Model-Synchronization -> changes of charset/collation not correct identified |
66904 | 2012-09-21 9:54 | 2012-09-21 12:36 | MySQL Workbench: Modeling | Verified (4405 days) | S3 | 5.2.43 | Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit) | Any | Model designer : Model Overview : Focus flicker when returning from "Edit Routin |
67816 | 2012-12-05 9:49 | 2012-12-05 11:45 | MySQL Workbench: Modeling | Verified (4330 days) | S3 | 5.2.44 | Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit) | Any | Cant delete multiple tables from Tables list in Model Overview |
Showing 1-1000 of 1226 (Edit, Save, CSV, Feed) | Show Next 1000 Entries » |