Showing all 503 (Edit, Save, CSV, Feed) |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
653 | 2003-06-13 13:27 | 2003-06-14 4:25 | MySQL Server | Can't repeat (7762 days) | S2 | 3.23.51 | Linux (Linux) | Any | mysqld got signal 11 |
710 | 2003-06-24 6:55 | 2003-06-24 6:59 | MySQL Server | Can't repeat (7752 days) | S2 | 4.0.13 | Solaris (Solaris 2.8) | Any | SmartHeap and MySQL libraries cause core dumps on Solaris |
768 | 2003-06-30 16:51 | 2003-07-19 8:16 | MySQL Server | Can't repeat (7727 days) | S2 | 4.1.0-alpha-max | SunOS 5.8 | Any | Db privilege table not being used with multi-table updates |
987 | 2003-08-03 20:24 | 2003-08-04 4:23 | MySQL Server: MyISAM storage engine | Can't repeat (7711 days) | S2 | 4.0.12-log | Linux (RedHat 7.3) | Any | mysqld got signal 11 |
1165 | 2003-08-29 10:07 | 2003-09-02 10:57 | MySQL Server | Can't repeat (7682 days) | S1 | 4.0.14 | Windows (win 2000 pro) | Any | server crash on select statement |
1167 | 2003-08-30 7:10 | 2003-10-16 22:32 | Connector / ODBC | Can't repeat (7638 days) | S3 | 3.51.06 | Windows (Windows 98 SE) | Any | MyODBC and Describe Table |
2074 | 2003-12-10 3:51 | 2003-12-12 10:17 | MySQL Server: Embedded Library ( libmysqld ) | Can't repeat (7581 days) | S2 | 4.0.16 patched | Windows (Win 2000/XP) | Any | Another bug in Embedded mySql in a multithread application |
397 | 2003-05-08 5:13 | 2003-12-22 10:20 | MySQL Server: Command-line Clients | Can't repeat (7571 days) | S3 | 4.0.10-gamma-nt | Windows (Windows 2000 SP3) | Any | mysql.exe uses persistent connections which leads to 'too many connections' |
2253 | 2004-01-01 22:33 | 2004-01-13 13:58 | Connector / J | Can't repeat (7549 days) | S1 | 3.0.9 stable | Windows (windows server 2003) | Any | fail convert the encode(gbk or gb2312) when get data from DB (mysql4.1) |
2350 | 2004-01-11 18:32 | 2004-01-14 4:57 | MySQL Server: MyISAM storage engine | Can't repeat (7548 days) | S1 | Linux (Redhat 9) | Any | Locked table, with nothing using it. | |
2226 | 2003-12-28 10:31 | 2004-01-15 11:15 | MySQLCC | Can't repeat (7547 days) | S3 | 0.9.4-beta | Windows (Windows 2000 SP4) | Any | Ctrl+A in SQL Mode Fails |
2433 | 2004-01-16 23:23 | 2004-01-17 11:36 | MySQL Server | Can't repeat (7545 days) | S1 | 3.23.53 | Any | MYSQL database crash after every 3 month | |
2442 | 2004-01-19 4:07 | 2004-01-22 11:14 | MySQL Server: User-defined functions ( UDF ) | Can't repeat (7540 days) | S1 | 4.1.1-alpha | Linux (RH 9) | Any | mysql table get corrupted |
2395 | 2004-01-15 0:53 | 2004-01-22 11:24 | Connector / J | Can't repeat (7540 days) | S2 | 3.0.6, 3.0.8, 3.0.9, 3.0.10, 3.1.0 | Windows (Windows 2000) | Any | utf8 chars are unsupported |
1585 | 2003-10-17 5:43 | 2004-01-29 6:32 | MySQL Server: Compiling | Can't repeat (7533 days) | S2 | 4.0.15a | IBM AIX (AIX 5.2) | Any | Compilation error on AIX |
2551 | 2004-01-29 3:29 | 2004-01-29 10:59 | MySQL Server: MyISAM storage engine | Can't repeat (7533 days) | S3 | 4.1.1-alpha-standard-log | Linux (Linux (Kernel 2.4.21)) | Any | Different behavior of 4.0 and 4.1 w.r.t. LIKE '303%000' |
2549 | 2004-01-29 0:06 | 2004-01-29 11:54 | MySQL Server | Can't repeat (7533 days) | S3 | 4.1.1 | Linux (Linux) | Any | Server Dump when bind the sql with 'AND' operator |
2554 | 2004-01-29 6:14 | 2004-02-08 9:02 | MySQLCC | Can't repeat (7523 days) | S2 | 0.9.4-beta | Windows (Windows 2003 Server) | Any | Missing database in Control Center |
2713 | 2004-02-11 13:33 | 2004-02-23 7:05 | MySQL Server | Can't repeat (7508 days) | S2 | 4.1.1 | Solaris (Solaris 2.8) | Any | SELECT on derived table with no outer GROUP BY causes sig11 |
2540 | 2004-01-28 3:39 | 2004-02-23 12:31 | Connector / ODBC | Can't repeat (7508 days) | S3 | any | Any (any) | Any | SQLStatistics does not conform to the standard |
2823 | 2004-02-16 5:30 | 2004-02-24 11:10 | MySQL Server | Can't repeat (7507 days) | S2 | 4.0.16 | MacOS (OS X) | Any | auto_increment bug with (unsigned) bigint |
2958 | 2004-02-25 7:56 | 2004-02-25 11:22 | MySQL Server | Can't repeat (7506 days) | S1 | 4.1 | Windows (Windows 2000 Advanced Server) | Any | Crash the server |
2914 | 2004-02-21 6:21 | 2004-02-25 11:23 | MySQL Server | Can't repeat (7506 days) | S3 | 4.1.1 | Any | Adding UNIQUE index causes unexpected result of the query | |
3053 | 2004-03-03 3:00 | 2004-03-06 6:43 | MySQL Server | Can't repeat (7496 days) | S2 | 4.1.0 | Linux (SuSe linux) | Any | delete stmt's deletes rows but returns an error |
3042 | 2004-03-02 10:41 | 2004-03-06 23:34 | MySQL Administrator | Can't repeat (7496 days) | S1 | 1.0.1a-alpha | Windows (Windows 2000) | Any | MySQL Administrator install fails |
644 | 2003-06-12 14:56 | 2004-03-11 8:59 | MySQL Server | Can't repeat (7491 days) | S1 | 4.1 | Linux (linux 2.4) | Any | crash in add_key_field when using prepared statements |
2751 | 2004-02-12 9:09 | 2004-03-11 21:30 | MySQLCC | Can't repeat (7491 days) | S2 | 0.9.4 | Linux (Fedora(core1) gnome 2.4) | Any | Creating Database via SQL pane does not show up in database list |
3240 | 2004-03-19 1:44 | 2004-03-25 10:40 | MySQL Server | Can't repeat (7477 days) | S2 | 4.0.18-standard | Linux (Linux) | Any | MySQL process manager sometimes fails due to binding problem |
3242 | 2004-03-19 5:41 | 2004-03-25 11:25 | MySQL Server | Can't repeat (7477 days) | S2 | 3.23.58 | Linux (RHEL-3AS) | Any | binary blackhole |
2875 | 2004-02-18 12:36 | 2004-03-31 23:47 | MySQL Server | Can't repeat (7471 days) | S2 | 4.1.2 | Other (qnx) | Any | numerows safemalloc warnings on qnx |
3322 | 2004-03-29 5:12 | 2004-04-02 8:07 | MySQL Server | Can't repeat (7469 days) | S2 | 5.0.0a | Linux (Linux x86) | Any | Inserting items after a LOCK TABLES fails |
3364 | 2004-04-02 3:55 | 2004-04-03 9:17 | Connector / J | Can't repeat (7468 days) | S2 | Connector/J 3.1.1-alpha | Linux (Linux 2.4 RedHet9) | Any | Join-query error |
2426 | 2004-01-16 7:30 | 2004-05-03 10:44 | MySQL Server: Command-line Clients | Can't repeat (7438 days) | S3 | 4.1.1 and 4.1.0 | Linux (SuSE Linux 8.2, 9.0 Intel) | Any | Segfault on exit from mysql client, versions 4.1.0 and 4.1.1 |
3770 | 2004-05-15 9:55 | 2004-05-20 18:07 | MySQLCC | Can't repeat (7421 days) | S1 | 0.94 | Windows (win xp service pak 1) | Any | content of fields are changed on moving over it by using the cursor keys |
4095 | 2004-06-10 20:06 | 2004-06-17 9:48 | MySQL Server: MyISAM storage engine | Can't repeat (7393 days) | S1 | 4.0, 4.1, 5.0 | Any (any) | Any | MyISAM corruption happens with concurrent INSERTs |
3677 | 2004-05-06 16:40 | 2004-07-13 20:52 | MySQL Server: Installing | Can't repeat (7367 days) | S2 | Windows (Windows 2003 SERVER) | Any | Mysql and Windows server 2003 | |
3945 | 2004-06-01 5:22 | 2004-07-14 7:26 | MySQLCC | Can't repeat (7366 days) | S1 | 0.9.4-beta | Windows (Windows XP) | Any | Control Centre doesn't allow to type the query in query window |
5090 | 2004-08-18 12:40 | 2004-08-18 20:46 | MySQL Server | Can't repeat (7331 days) | S1 | 4.1.3b | Windows (Windows XP SP1) | Any | MySql (mysqld-nt.exe) service crashes on a simple LEFT function |
4019 | 2004-06-05 13:44 | 2004-08-20 3:34 | MySQL Server | Can't repeat (7329 days) | S2 | 4.0.20 | Any (any) | Any | 4.0.20 Optimiser makes a wrong decision |
5175 | 2004-08-23 23:00 | 2004-09-02 16:19 | MySQL Server: MyISAM storage engine | Can't repeat (7316 days) | S2 | 4.1.2 | Linux (Linux) | Any | can't DROP MERGE table if either file is missing |
3589 | 2004-04-28 14:56 | 2004-09-03 16:51 | MaxDB | Can't repeat (7315 days) | S1 | 7.5.00.08 | Windows (Windows 2000 , Linux) | Any | Problem with Data Type 'LONG VARCHAR' |
4244 | 2004-06-22 7:59 | 2004-10-22 20:51 | Connector / NET | Can't repeat (7266 days) | S2 | Windows (windows xp) | Any | bytefx.data + mysql + vb.net | |
6363 | 2004-11-01 13:45 | 2004-11-01 18:04 | MySQL Administrator | Can't repeat (7256 days) | S1 | 1.0.13 | Linux (linux - mandrake 10) | Any | mysql-administrator 1.0.13 segmentation fault - won't run at all |
6361 | 2004-11-01 11:18 | 2004-11-01 19:20 | MySQL Server: MyISAM storage engine | Can't repeat (7256 days) | S3 | 4.0.22-standard | Linux (RH Linux (2.4.22-1.2115.nptl)) | Any | Timestamp comparisons are failing at the second level |
12153 | 2005-07-25 14:10 | 2005-08-02 15:34 | MySQL Server | Can't repeat (6982 days) | S2 | 4.0.12,4.0.13,4.0.14 | Linux (Linux Fedora Core 4) | Any | LOCK TABLES with mysql_query() works wrong |
14413 | 2005-10-27 23:12 | 2005-11-04 16:03 | MySQL Server | Can't repeat (6888 days) | S2 | 5.0.15-source | Linux (Fedora Core 2) | Any | Linker fails with "undefined reference to `_create_index_by_sort'" |
3026 | 2004-03-01 12:36 | 2005-11-23 15:56 | Connector / ODBC Documentation | Can't repeat (6869 days) | S2 | 3.51 | Windows (windows 2000) | Any | Select statement must not have only substrings |
7516 | 2004-12-23 20:26 | 2005-11-26 13:02 | MySQL Server: Optimizer | Can't repeat (6866 days) | S2 | 4.0.25 and 4.1.10a | Linux (Linux (SuSE 8.2)) | Any | Wrong sort order when ORDER BY includes an ENUM column |
7670 | 2005-01-04 19:30 | 2006-01-16 19:25 | MySQL Server | Can't repeat (6815 days) | S3 | 5.0 | Any | Loss of precision for some integer values stored into DOUBLE column | |
16632 | 2006-01-19 14:22 | 2006-01-21 18:24 | MySQL Server | Can't repeat (6810 days) | S2 | 5.0.18 | Windows (win2k) | Any | like statement error |
16496 | 2006-01-13 21:04 | 2006-02-01 16:28 | MySQL Server | Can't repeat (6799 days) | S2 | 5.0.18-log | Linux (SUSE LINUX Enterprise Server 9) | Any | segfault when combining DISTINCT and GROUP BY in one query |
19221 | 2006-04-20 14:11 | 2007-02-03 7:29 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (6432 days) | S5 | 5.1 | Any | RBR performance regression in write_row | |
25460 | 2007-01-08 3:10 | 2007-03-15 18:08 | MySQL Server: General | Can't repeat (6392 days) | S1 | 5.0.27,5.1.11,5.1.14,5.1.15 | Solaris (Solaris 10) | Any | High concurrency MyISAM access causes severe mysqld crash. |
30999 | 2007-09-13 12:36 | 2007-10-21 12:49 | MySQL Server: Replication | Can't repeat (6172 days) | S2 | 5.0.41 | Linux (Linux nj-ckmd-01 2.6.9-55.ELsmp #1 SMP Fri Apr 20 16:36:54 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux ) | Any | Killed InnoDB transaction gets into binary log then stops replication slaves |
3028 | 2004-03-01 17:40 | 2008-01-04 23:07 | Connector / ODBC | Can't repeat (6097 days) | S2 | 5.1 | Windows (WIndows XP) | Any | error when updating a decimal, float or double field in .net |
33958 | 2008-01-21 13:25 | 2008-01-29 20:57 | MySQL Server: Compiling | Can't repeat (6072 days) | S2 | 5.1 | Linux | Any | A configure.in bug in 5.1.23 |
2094 | 2003-12-11 5:03 | 2008-09-27 9:37 | MySQL Server: InnoDB storage engine | Can't repeat (5830 days) | S3 | 4.1.1 | Any (any) | Any | ALTER TABLE allows change of the column containing NULL's to NOT NULL |
40379 | 2008-10-28 20:23 | 2008-11-14 15:18 | MySQL Server: Replication | Can't repeat (5782 days) | S1 | 5.0.72 | Linux (IA64 / ICC only) | Any | Server crash by "show slave status" (platform-specific) |
10195 | 2005-04-27 8:18 | 2011-02-16 23:43 | MySQL Server | Can't repeat (4988 days) | S2 | 4.1.8-nt | Windows (windows) | Any | LOAD DATA INFILE and UTF-8 |
14044 | 2005-10-15 1:38 | 2011-02-16 23:43 | MySQL Server | Can't repeat (5800 days) | S1 | 4.1.14-standard-log | Solaris (Solaris 10 FCS x86-64) | Any | mysqld crashes with an out-of-bounds exception and a SIGSEGV segment violation. |
18300 | 2006-03-17 10:45 | 2011-02-16 23:43 | MySQL Server: Stored Routines | Can't repeat (5520 days) | S1 | 5.0.19, 4.1.18 | Any | Any | Memory leak of st_lex (and maybe sp_pcontext?) structures? |
40251 | 2008-10-22 13:56 | 2011-02-16 23:43 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (5625 days) | S2 | 5.1-rpl | Any | Any | Replication failure on RBR + Innodb + PARTITIONs |
2119 | 2003-12-15 12:34 | 2012-04-26 19:28 | MySQL Server: Command-line Clients | Can't repeat (4523 days) | S2 | 4.0.16 | Linux (Debian Linux) | Any | mysqlbinlog 'Event too big' |
37318 | 2008-06-10 22:17 | 2013-02-03 19:24 | MySQL Server: Replication | Can't repeat (5932 days) | S1 | 5.1.26 | Any | Any | slave crash in replicated 'flush tables' |
69435 | 2013-06-10 12:46 | 2013-06-11 13:02 | MySQL Workbench: Modeling | Can't repeat (4112 days) | S3 | 5.2.47 | Any | Any | MySQL Workbench - EER Diagram not showing unicode(utf-8) text |
67133 | 2012-10-08 12:34 | 2013-07-28 17:07 | MySQL Server: Command-line Clients | Can't repeat (4065 days) | S2 | 5.6.7 RC | MacOS (10.6.8) | Any | mysql fails on OSX Symbol not found: _strnlen |
3334 | 2004-03-30 5:04 | 2014-03-28 13:52 | Connector / J | Can't repeat (3822 days) | S2 | 3.1.1-alpha | Windows (WinXP) | Any | Different behavior of complex query when execute by different method |
68871 | 2013-04-05 7:32 | 2014-08-27 4:36 | MySQL Server: Optimizer | Can't repeat (3670 days) | S3 | 5.1.58, 5.5.30, 5.6.10 | Any | Any | EXPLAIN does not show real plan used for query with HAVING |
72810 | 2014-05-30 7:47 | 2015-04-30 21:35 | MySQL Server: Replication | Can't repeat (3424 days) | S3 | Any | Any | Relay log without xid_log_event may case parallel crash in debug mode | |
66921 | 2012-09-21 20:33 | 2016-01-20 20:03 | MySQL Server: Replication | Can't repeat (4133 days) | S3 | 5.1, probably others | Any | Any | Seconds_behind_master distorted because of verbatim master's FDE in relaylog |
80029 | 2016-01-18 10:26 | 2016-03-10 9:36 | MySQL Server: InnoDB storage engine | Can't repeat (3109 days) | S3 | 5.7.10 | CentOS (7) | Any | [ERROR] InnoDB: Cannot allocate 0 bytes: Success weird error message |
81629 | 2016-05-27 20:22 | 2016-08-02 15:28 | MySQL Server: Stored Routines | Can't repeat (2964 days) | S3 | Ver 14.14 Distrib 5.7.12,for Linux (i686 | Any (14.04 LTS) | Any | ERROR 1137 occurs WHEN Execution TRIGGER |
71397 | 2014-01-16 9:04 | 2016-08-30 8:42 | MySQL Server: Replication | Can't repeat (3850 days) | S2 | 5.5.34 | Linux (Red Hat Enterprise Linux Server release 6.4 (Santiago)) | Any | Replicated slave stops replicating with Error_code: 1366 |
84555 | 2017-01-18 14:32 | 2017-01-18 17:19 | MySQL Server | Can't repeat (2795 days) | S3 | 5.6.30 | CentOS | Any | memory corruption when attempting to delete from renamed old general_log table |
77214 | 2015-06-01 18:42 | 2017-04-26 14:45 | MySQL Server: InnoDB storage engine | Can't repeat (2697 days) | S2 | 5.6 | Any | Any | InnoDB data lost if fast_shutdown=1 and trx_commit=0 |
87108 | 2017-07-19 6:51 | 2017-07-27 15:35 | MySQL Server: Optimizer | Can't repeat (2605 days) | S3 | 5.7.18 | MacOS (macOS Sierra, Version 10.12.5, Memory 8 GB) | Any | MySQL concurrent execution of queries are extremely slow |
86829 | 2017-06-26 17:42 | 2017-09-01 12:13 | MySQL Server: Replication | Can't repeat (2569 days) | S2 | 5.6.36/5.6.37 | Linux | Any | Slave IO Disconnects and binlog transfer slowed down on sync_master_info |
82764 | 2016-08-28 14:02 | 2017-11-24 14:48 | MySQL Server | Can't repeat (2485 days) | S2 | 5.17 | FreeBSD | Any | [Regression] MySQL server corrupts install if mysql user exists in FreeBSD |
7684 | 2005-01-05 11:15 | 2017-12-23 10:12 | MySQL Server: Parser | Can't repeat (3128 days) | S3 | 5.0, probably all, 5.1, 4.1 | Any (Windows XP) | Any | more than two UNION SELECT statement problem (with MS Access) |
82997 | 2016-09-14 17:18 | 2018-01-29 12:11 | MySQL Server: InnoDB storage engine | Can't repeat (2419 days) | S2 | 5.7.13 | CentOS | Any | Online DDL fails with |
90637 | 2018-04-26 2:54 | 2018-04-27 13:08 | MySQL Server: InnoDB storage engine | Can't repeat (2331 days) | S3 | 5.7.17 | Any | Any | innodb assertion failure at !trx_commit_disallowed when async io turned off |
90773 | 2018-05-06 21:34 | 2018-05-08 13:18 | MySQL Server | Can't repeat (2320 days) | S2 | 5.7.22 | Ubuntu (16.04.1) | Any | Subquery freezes |
91278 | 2018-06-15 10:21 | 2018-06-15 12:36 | MySQL Server: C API (client library) | Can't repeat (2282 days) | S3 | mysql-5.7.22 | SUSE (SUSE Linux Enterprise Server 12 (x86_64) Patchlevel 3) | x86 | preparing MySQL statement failed: Lost connection to MySQL server during query |
91077 | 2018-05-30 12:43 | 2018-06-15 12:43 | MySQL Server | Can't repeat (2282 days) | S3 | 5.5.60 | Any | Any | [FAIL] Starting MySQL database server: mysqld . . . . . . . . failed! |
91206 | 2018-06-11 8:28 | 2018-06-22 11:59 | MySQL Server | Can't repeat (2275 days) | S5 | 5.7.22 | CentOS (6.3) | x86 | can't use full key_len of the index |
90694 | 2018-04-30 17:18 | 2018-07-03 15:12 | MySQL Server | Can't repeat (2264 days) | S2 | 8.0.11 | Windows | Other (x64) | Server crashes |
79990 | 2016-01-14 16:28 | 2018-07-05 15:42 | MySQL Server: Optimizer | Can't repeat (2262 days) | S3 | 5.6.27 | Any | Any | index used to return data not range scanned |
79574 | 2015-12-09 12:15 | 2018-07-06 14:57 | MySQL Server: InnoDB storage engine | Can't repeat (2261 days) | S2 | 5.6.27 | Linux (Kernel 3.4.109, x86_64, glibc-2.19) | Any | InnoDB: unable to purge a record |
91036 | 2018-05-27 4:45 | 2018-07-10 14:53 | MySQL Server: InnoDB storage engine | Can't repeat (2258 days) | S3 | 8.0.11 | Any (3.10.0-514.26.2.el7.x86_64) | x86 | mysql 8.0.11 innodb corrupt after sysbench failed |
91598 | 2018-07-11 11:52 | 2018-07-12 12:51 | MySQL Server: DML | Can't repeat (2255 days) | S3 | 8.0.11 | Windows (Microsoft Windows 10 Home) | Any | Anti-joins running very slowly |
79674 | 2015-12-16 16:08 | 2018-07-17 7:36 | MySQL Server: InnoDB storage engine | Can't repeat (2250 days) | S1 | 5.5.46 | Any | Any | InnoDB table space corruption prevents MySQL server from starting |
92050 | 2018-08-17 5:35 | 2018-08-20 15:29 | MySQL Server | Can't repeat (2216 days) | S3 | 5.7.23 | Ubuntu (16.04.5 LTS) | x86 (4.4.0-122-generic) | flush-logs command does not work and causes the process to hang |
91719 | 2018-07-19 14:30 | 2018-08-27 11:53 | MySQL Server: InnoDB storage engine | Can't repeat (2209 days) | S2 | 5.7.22 | Debian (Linux server0 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux) | Any (Intel® Core™ i7-6700 Quadcore Skylake 64 GB DDR4 2 x 500 GB, SATA 6 Gb/s, SSD) | UTC - mysqld got signal 11 ; |
85132 | 2017-02-22 17:59 | 2018-08-27 12:00 | MySQL Server: InnoDB storage engine | Can't repeat (2209 days) | S3 | 5.6.34 | Any | Any | Performance regression with FusionIO between 5.6.16 and 5.6.34 |
77872 | 2015-07-29 14:17 | 2018-08-27 12:02 | MySQL Server | Can't repeat (2209 days) | S3 | 5.7.7 | Linux | Any | possible three way lock deadlock |
91827 | 2018-07-30 8:06 | 2018-08-31 12:05 | MySQL Server | Can't repeat (2205 days) | S3 | 8.0.11 | Windows (2012 R2) | x86 | The server itself stops |
91861 | 2018-08-01 21:47 | 2018-09-24 12:46 | MySQL Server: InnoDB storage engine | Can't repeat (2181 days) | S3 | 5.7.22 | Any | Any | The buf_LRU_free_page function may leak some memory in a particular scenario |
74003 | 2014-09-22 3:08 | 2018-09-25 12:27 | MySQL Server | Can't repeat (2180 days) | S3 | 5.6.16 | Any | Any | The server was crashed because of long semaphore wait |
79826 | 2016-01-03 8:41 | 2018-09-28 12:08 | MySQL Server: User-defined functions ( UDF ) | Can't repeat (2177 days) | S3 | 5.6.27 | Ubuntu | Any | MySql invalid argument reading |
72748 | 2014-05-26 8:56 | 2018-10-11 17:07 | MySQL Server: Locking | Can't repeat (2164 days) | S2 | 5.6.17, 5.6.19, 5.6.21 | Any | Any | INSERT...SELECT fails to block concurrent inserts, results in additional records |
92559 | 2018-09-25 13:09 | 2018-10-29 12:52 | MySQL Server | Can't repeat (2146 days) | S3 | 8.0.11 | CentOS | Any | The change of the time caused the all write thread pending |
89000 | 2017-12-21 8:18 | 2018-11-03 13:15 | MySQL Workbench | Can't repeat (2458 days) | S2 | 6.3.10 build 12092614 CE (64 bits) Commu | Ubuntu (Ubuntu based, Linux Mint Cinnamon) | Any | Workbench crash when connecting to database |
88914 | 2017-12-14 9:29 | 2018-11-26 13:03 | MySQL Server: InnoDB storage engine | Can't repeat (2118 days) | S3 | mysql-5.7.20 | Ubuntu (Ubuntu-14.04) | Any | Potential null pointer dereference at pointer node->undo_recs (row0purge.cc) |
93246 | 2018-11-19 12:36 | 2018-12-03 14:15 | MySQL Server: Documentation | Can't repeat (2111 days) | S3 | 5.5 | Any | Any | Select large mysql set as bitfield |
91989 | 2018-08-13 6:45 | 2018-12-06 8:40 | MySQL Server: InnoDB storage engine | Can't repeat (2220 days) | S1 | 8.0.12 | MacOS (10.13.6) | x86 | InnoDB: Assertion failure: dict0dict.cc |
74775 | 2014-11-11 4:42 | 2018-12-13 13:30 | MySQL Server: InnoDB storage engine | Can't repeat (2101 days) | S3 | 5.7.7 | Linux | ARM | buf_block_align relies on random timeouts, volatile rather than barriers |
75513 | 2015-01-15 10:20 | 2019-01-08 12:48 | MySQL Server: InnoDB storage engine | Can't repeat (2075 days) | S5 | 5.5.31 | Linux | Any | DROP TABLE creating a stall when foreign keys in use on other tables |
92728 | 2018-10-10 8:39 | 2019-01-30 13:41 | MySQL Server: Partitions | Can't repeat (2075 days) | S3 | 5.7.20 | Windows (WIndows Server 2016) | x86 (On a VM) | MySQL 5.7 issue with 16TB disk |
94077 | 2019-01-27 6:29 | 2019-02-05 17:15 | MySQL Server: Information schema | Can't repeat (2047 days) | S5 | 8.0.13 | Any | Any | Query to get processes from processlist is choking mysql to 30% speed |
93277 | 2018-11-21 15:11 | 2019-02-11 13:01 | MySQL Server: Options | Can't repeat (2080 days) | S3 | 8.0.13 | Any | Any | NON_PERSIST flags doesn't work without READ_ONLY |
93767 | 2018-12-30 22:22 | 2019-02-25 13:14 | MySQL Server | Can't repeat (2027 days) | S2 | 8.0.13 (git source) | Debian (9.6) | x86 | INSTALL COMPONENT fails - handled segfault during installation nothing in log |
94150 | 2019-01-31 8:47 | 2019-03-01 13:38 | MySQL Server | Can't repeat (2023 days) | S3 | 5.6 5.7 | Any | Any | When "show global status" hang, new connection can't be established |
94163 | 2019-02-01 9:52 | 2019-03-04 13:24 | MySQL Server: Errors | Can't repeat (2020 days) | S3 | 5.7.24-log MySQL Community Server | Red Hat (CentOS Linux release 7.6.1810 (Core)) | x86 (Intel(R) Xeon(R) CPU E5-2682 v4 @ 2.50GHz) | no clust rec is found for a deleted-marked secondary index record. |
93737 | 2018-12-26 1:57 | 2019-03-12 14:58 | MySQL Server: Command-line Clients | Can't repeat (2012 days) | S2 | 5.6 | Any | Any | mysqlbinlog mermory used grows unstoped |
94503 | 2019-02-28 1:56 | 2019-04-02 13:21 | Connector / C++ | Can't repeat (1991 days) | S2 | 1.1.9-4+b1 | Debian (buster) | x86 (amd64) | getString() fails for large text |
94537 | 2019-03-03 19:22 | 2019-04-05 13:00 | MySQL Server | Can't repeat (1988 days) | S2 | 5.7.25 | FreeBSD | x86 | memory leak |
82736 | 2016-08-26 3:01 | 2019-04-08 14:00 | MySQL Server: InnoDB storage engine | Can't repeat (1985 days) | S2 | 5.7.11 | Any | Any | Undo log corruption when using generated columns |
93715 | 2018-12-21 10:26 | 2019-04-23 13:29 | MySQL Server | Can't repeat (1970 days) | S2 | 5.7.24 | Windows | x86 | MySQL Server Crash (Access Violation) whilst reading from Information_schema |
94812 | 2019-03-28 10:12 | 2019-04-23 14:55 | MySQL Server | Can't repeat (1970 days) | S2 | 5.7.22 | Red Hat (6.5) | Any | mysql 5.7.22 crash |
94741 | 2019-03-22 5:26 | 2019-05-02 13:21 | MySQL Server | Can't repeat (1961 days) | S3 | 5.7.18 | CentOS (7.4) | x86 (2vCPU x 4GB RAM) | SQL mode error catching the wrong updated column |
94796 | 2019-03-27 8:02 | 2019-05-02 13:22 | MySQL Server: DDL | Can't repeat (1961 days) | S3 | 5.7 | Any | Any | Stack overflow in call open_dict_table function |
94798 | 2019-03-27 12:55 | 2019-05-06 13:08 | MySQL Server: Optimizer | Can't repeat (1957 days) | S5 | 8.0.12 | Linux | Any | Since MySQL 8.0.15 execution plan has changed in a bad way |
95292 | 2019-05-08 10:59 | 2019-05-09 15:52 | MySQL Server: Row Based Replication ( RBR ) | Can't repeat (1954 days) | S2 | 5.6.33 | Red Hat (rhel 7.5) | x86 (Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz * ) | slave crash when update a table with 'binlog_format=mix' in master |
634 | 2003-06-11 4:24 | 2019-05-14 14:30 | MySQL Server | Can't repeat (5830 days) | S3 | 4.1.1 current BK tree | Any (FreeBBSD-4.6) | Any | SELECT CAST(datetime_value AS DATE) GROUP by 1 |
95168 | 2019-04-27 20:33 | 2019-06-03 13:00 | MySQL Server: InnoDB storage engine | Can't repeat (1929 days) | S5 | 8.0.14 | Any | Any | Make log_flush_notifier thread more accurate |
95802 | 2019-06-14 2:12 | 2019-06-24 12:45 | MySQL Server | Can't repeat (1908 days) | S5 | 8.0.16 | Windows | Any | It is very efficient to execute SQL statements alone, but it is very inefficient |
95519 | 2019-05-24 9:04 | 2019-06-25 12:28 | MySQL Server: Security: Audit | Can't repeat (1907 days) | S3 | 5.7.25-28 | Ubuntu (14.14) | Any | Create a Denial of service |
95490 | 2019-05-23 10:53 | 2019-07-01 12:51 | MySQL Server: General | Can't repeat (1901 days) | S3 | 5.7.26 | Red Hat | Any | Select distinct returns actual distinct values and NULL. But No NULL Value |
95673 | 2019-06-06 13:50 | 2019-07-04 12:52 | MySQL Server: InnoDB storage engine | Can't repeat (1899 days) | S3 | 5.7.26 | Any | Any | Crash on import tablespace |
96040 | 2019-07-01 2:28 | 2019-07-08 12:31 | MySQL Server | Can't repeat (1897 days) | S3 | Any | Any | behavior of wndow function with range | |
95678 | 2019-06-06 21:22 | 2019-07-08 12:38 | MySQL Server: Optimizer | Can't repeat (1894 days) | S2 | 5.6.33 | Ubuntu | x86 | query gives empty result when using index_merge |
96135 | 2019-07-09 7:36 | 2019-07-09 12:33 | MySQL Server | Can't repeat (1893 days) | S3 | mysql-8.0.16-linux-glibc2.12-x86_64 | CentOS (3.10.0-123.el7.x86_64) | x86 (x86_64) | mysql server bug |
95883 | 2019-06-19 14:24 | 2019-07-22 11:49 | MySQL Server | Can't repeat (1880 days) | S3 | Windows (windows server 2012r2) | Any | server crash very day | |
95825 | 2019-06-15 12:50 | 2019-07-22 12:25 | Connector / J | Can't repeat (1880 days) | S3 | 5.7.26 | CentOS (.10.0-514.6.2.el7.x86_64) | x86 | Function does not exist but it does |
79274 | 2015-11-13 15:03 | 2019-07-25 12:42 | MySQL Server: Locking | Can't repeat (1877 days) | S2 | 5.6, 5.7, 8.0 | Any | Any | CREATE TRIGGER etc is not able to get a SHARED_NO_WRITE metadata lock |
95176 | 2019-04-29 7:03 | 2019-08-01 12:31 | MySQL Server | Can't repeat (1914 days) | S3 | 8.0.13 | CentOS | Any | when search table in information_schema when delete table, there is a error |
10862 | 2005-05-25 16:54 | 2019-08-08 13:06 | MySQL Server: MyISAM storage engine | Can't repeat (6792 days) | S1 | 4.1.12 | Linux (Linux, all) | Any | A crashing bug in MyISAM parallel repair after bulk insert from LOAD DATA |
96092 | 2019-07-04 12:10 | 2019-08-09 12:27 | MySQL Server: InnoDB storage engine | Can't repeat (1862 days) | S3 | 5.7.14 | Any | Any | Corrupted |
76243 | 2015-03-10 13:17 | 2019-08-09 12:28 | MySQL Server | Can't repeat (1862 days) | S3 | 5.5.41 | Linux (RH) | Any | rc script does not respect both delimiters for service timeout startup |
96240 | 2019-07-18 2:14 | 2019-08-22 13:36 | MySQL Server: InnoDB storage engine | Can't repeat (1849 days) | S3 | 5.6 | Any | Any | Crash loop during innodb recovery on startup |
96239 | 2019-07-17 20:39 | 2019-08-27 12:12 | MySQL Server: InnoDB storage engine | Can't repeat (1844 days) | S3 | 8.0 | Any | Any | Undo might not cleanup entries of innodb_ddl_log due to exception |
96774 | 2019-09-06 7:42 | 2019-09-06 13:28 | MySQL Server: Performance Schema | Can't repeat (1834 days) | S3 | 5.6.23,5.7.21 | CentOS | Any | The timer_start in performance_schema is much smaller than mysql' uptime |
96464 | 2019-08-08 8:39 | 2019-09-23 16:15 | MySQL Server: Optimizer | Can't repeat (1817 days) | S3 | 8.0 | Windows | Any | bug about json_table function |
96620 | 2019-08-22 13:14 | 2019-09-24 11:41 | MySQL Server: Data Types | Can't repeat (1816 days) | S2 | 5.6.10 | Any | Any | The CONVERT_TZ function fetches wrong value for "Asia/Irkutsk" timezone |
92394 | 2018-09-12 23:52 | 2019-09-24 13:58 | MySQL Server: C API (client library) | Can't repeat (1816 days) | S3 | 5.7.23 | Ubuntu | x86 | libmysqlclient enters infinite loop after signal (race condition) |
79710 | 2015-12-20 8:45 | 2019-09-30 12:06 | MySQL Server: Pluggable Authentication | Can't repeat (1810 days) | S3 | 5.7.10 | Any | Any | Unable to use my_malloc() and my_free() in dynamic client plugins |
82847 | 2016-09-02 14:07 | 2019-09-30 12:08 | MySQL Server: DDL | Can't repeat (1810 days) | S2 | 5.6.30 | Windows (2012 R2 x64) | Any | mysqld crashes |
96986 | 2019-09-24 7:21 | 2019-10-25 9:55 | MySQL Server: Replication | Can't repeat (1785 days) | S1 | 8.0.17 | CentOS (7.4 ) | x86 (CentOS Linux release 7.4.1708 (Core) ) | Column Ordinal Position Not orderly updating |
96988 | 2019-09-24 8:01 | 2019-10-25 11:58 | MySQL Server: InnoDB storage engine | Can't repeat (1785 days) | S3 | Any (8.0) | Any | Parallel read index may skip some records to get wrong result | |
77783 | 2015-07-20 7:01 | 2019-10-25 12:00 | MySQL Server: InnoDB storage engine | Can't repeat (1785 days) | S5 | 5.7, 5.6 | Any | Any | performance dropped when changing innodb_change_buffering from inserts to all |
97166 | 2019-10-09 16:16 | 2019-10-31 5:29 | MySQL Workbench | Can't repeat (1779 days) | S2 | 8.0.17 | Windows | Any | "Search Table Data..." for multiple tables fails if one has blob data |
97522 | 2019-11-06 20:56 | 2019-11-08 13:44 | MySQL Server: Information schema | Can't repeat (1771 days) | S3 | 8.0.11 | Windows (Server 2016 Standard) | x86 | Cannot delete non-existing table space |
97462 | 2019-11-03 15:05 | 2019-11-12 16:37 | MySQL Server: Optimizer | Can't repeat (1767 days) | S5 | 8.0.17 | FreeBSD (12.0) | x86 | Slow JOIN with ORDER BY due wrong index selection |
97697 | 2019-11-20 3:48 | 2019-11-21 13:00 | MySQL Server | Can't repeat (1758 days) | S3 | 5.7.25 | Any | Any | MySQL Crash during query from query cache |
97823 | 2019-11-28 7:05 | 2019-12-06 3:10 | MySQL Server | Can't repeat (1743 days) | S3 | 5.7.27 | CentOS (CentOS release 6.10 (Final)) | x86 (64-bit) | InnoDB: Failing assertion: UT_LIST_GET_LEN(rseg->update_undo_list) == 0 |
97941 | 2019-12-10 11:19 | 2019-12-10 14:19 | MySQL Server | Can't repeat (1739 days) | S3 | 5.6.29/5.7.25 | Any | Any | not in (null) returns wrong result |
97568 | 2019-11-09 15:48 | 2019-12-12 15:01 | MySQL Server: InnoDB storage engine | Can't repeat (1737 days) | S3 | 8.0.13 | CentOS | Any | Innodb crash recovery replay rename operation check rename validate wrong |
97983 | 2019-12-13 9:37 | 2019-12-16 13:50 | MySQL Server | Can't repeat (1733 days) | S3 | mysqld 5.7.26 | Linux | Any | InnoDB: Assertion failure in thread 139707135178496 in file fsp0fsp.cc line 2112 |
97593 | 2019-11-12 9:19 | 2019-12-16 13:54 | MySQL Server | Can't repeat (1733 days) | S2 | 5.6 | CentOS | x86 | mysql 5.6 crashes at fill_trx_row |
97450 | 2019-10-31 22:24 | 2019-12-26 11:54 | MySQL Package Repos | Can't repeat (1723 days) | S2 | 5.7.28 | Ubuntu (18.06) | x86 | Got an error reading communication packets MySQL docker overlay network |
97810 | 2019-11-27 10:10 | 2020-01-07 14:42 | MySQL Server | Can't repeat (1711 days) | S3 | 8.0.* | Any | Any | MySQL crash when compare with utf8mb4 |
97915 | 2019-12-06 12:55 | 2020-01-07 15:04 | MySQL Server: Charsets | Can't repeat (1711 days) | S3 | 5.7.27 | Ubuntu | x86 | utf8mb4_unicode_ci not converting letter "i" appropriate |
90587 | 2018-04-24 2:37 | 2020-02-10 13:05 | MySQL Server: InnoDB storage engine | Can't repeat (1677 days) | S3 | 5.7.21 | Any | Any | InnoDB: Assertion failure in thread 47255404480256 in file buf0lru.cc line 2213 |
98547 | 2020-02-11 7:18 | 2020-02-18 13:26 | MySQL Server | Can't repeat (1669 days) | S3 | 8.0.19 | CentOS | Other (x64) | Strange SUM value with GROUP BY |
98259 | 2020-01-16 22:56 | 2020-02-18 13:28 | MySQL Server: Errors | Can't repeat (1669 days) | S3 | 8.0.17 | Windows (Microsoft Windows 10 Pro) | Any | Bug with check like constraints |
98088 | 2019-12-28 5:54 | 2020-02-25 14:47 | MySQL Server: DML | Can't repeat (1662 days) | S3 | 8.0.18 | Any | x86 | Unique index is functioned unexpectedly when entire records are updated target |
98284 | 2020-01-19 8:58 | 2020-02-27 13:17 | MySQL Server: Connection Handling | Can't repeat (1660 days) | S3 | 8.0 | Linux (3.10.0-327.x86_64) | x86 | Low sysbench score in the case of a large number of connections |
77403 | 2015-06-18 12:27 | 2020-03-05 12:52 | MySQL Server: Optimizer | Can't repeat (1653 days) | S2 | 5.6.25 | Linux | Any | MySQL server 5.6 consumes all memory on server when running query |
98942 | 2020-03-13 11:53 | 2020-03-18 13:55 | MySQL Server: Optimizer | Can't repeat (1645 days) | S3 | 8.0.19 | Any | Any | Inconsistent results for the queries which should return same result |
99077 | 2020-03-26 9:47 | 2020-04-08 13:18 | MySQL Server: Performance Schema | Can't repeat (1619 days) | S1 | 5.7.29 | CentOS | Any | Crash on concurrent access to events_statements_history_long |
99108 | 2020-03-30 14:11 | 2020-05-04 12:20 | Connector / J | Can't repeat (1593 days) | S3 | 8.0.12 | Ubuntu | x86 | Zero-length branch qualifier causes SQL syntax error when starting transaction |
99183 | 2020-04-05 16:01 | 2020-05-07 12:37 | MySQL Server | Can't repeat (1590 days) | S3 | 8.0.19 | Any | Any | Comparison on FLOAT(9, 9) gives an incorrect result |
99496 | 2020-05-09 9:42 | 2020-05-14 12:30 | MySQL Server: Security: Privileges | Can't repeat (1583 days) | S3 | 8.0 | Any | Any | m_admin_interface_listen_socket and port not correspond in m_socket_map |
99320 | 2020-04-22 8:25 | 2020-05-25 12:00 | MySQL Server | Can't repeat (1572 days) | S2 | 8.0.19 | MacOS (10.15.3) | x86 | Unexpected restart after continuous querying |
99753 | 2020-06-01 12:50 | 2020-06-01 17:45 | MySQL Workbench: SQL Editor | Can't repeat (1565 days) | S2 | 8.0.20 | Windows (Microsoft Windows 10 Pro) | Any | The Workbenchs Table Inspector causes MySQL Server instance stops working |
99695 | 2020-05-26 13:38 | 2020-06-09 12:06 | MySQL Server: InnoDB storage engine | Can't repeat (1557 days) | S5 | 8.0 | Any | Any | Remove bloat caused by InnoDB logger class |
99914 | 2020-06-17 11:28 | 2020-06-18 12:12 | MySQL Server: InnoDB storage engine | Can't repeat (1549 days) | S5 | 8.0.20 | Debian (10 x64) | x86 (Xeon) | update slow Opening tables phase |
100049 | 2020-06-30 11:43 | 2020-06-30 14:48 | MySQL Server: Information schema | Can't repeat (1536 days) | S5 | 8.0.20 | Debian (Buster) | x86 (DigitalOcean dedicated 24 cpu) | Querying INFORMATION_SCHEMA.PROCESSLIST frequency stops all query execution |
98782 | 2020-02-28 18:57 | 2020-07-20 8:31 | MySQL Server: InnoDB storage engine | Can't repeat (1516 days) | S5 | 8.0.19 | Any | Any | Using TempTable engine for GROUP BY is slower than using MEMORY engine |
98163 | 2020-01-08 21:55 | 2020-08-03 13:36 | MySQL Server: Command-line Clients | Can't repeat (1502 days) | S3 | 8.0 | Any | Any | Heap Overflow Read in mysql client |
100148 | 2020-07-08 3:07 | 2020-08-10 12:22 | MySQL Server | Can't repeat (1495 days) | S2 | 8.0.18 | Red Hat | x86 | During a parallel read operation, the rollback of a table load operation causes |
100285 | 2020-07-22 8:14 | 2020-08-13 14:52 | MySQL Server | Can't repeat (1492 days) | S5 | 8.0.21 | Windows (Windows 10, Windows Server 2012 R2) | x86 | Large "insert ... select" takes twice as long |
100215 | 2020-07-14 13:19 | 2020-08-17 12:06 | MySQL Server | Can't repeat (1488 days) | S5 | 5.7.1.6 | Any | Any | insert into sql timeout spent 10s mysql 5.7 |
100186 | 2020-07-11 21:16 | 2020-08-17 12:09 | MySQL Server: InnoDB storage engine | Can't repeat (1488 days) | S3 | 8.0.* | Any | Any | some useless latch on Btree search and modify path |
99919 | 2020-06-17 16:29 | 2020-08-17 12:12 | MySQL Server: Command-line Clients | Can't repeat (1488 days) | S2 | mysql-community-client-8.0.20-1.el7.x86_ | CentOS (7.8.2003) | x86 | mysqladmin segmentation fault |
88523 | 2017-11-16 14:13 | 2020-08-28 13:13 | MySQL Server: InnoDB storage engine | Can't repeat (2179 days) | S3 | 5.7.16/5.7.22 | Windows | Any | InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the serv |
100659 | 2020-08-27 11:21 | 2020-08-30 5:28 | MySQL Server | Can't repeat (1475 days) | S3 | 5.7.17 | CentOS (7.2) | x86 | error_code=1146 write to binlog cause slave sql_thread stop |
100561 | 2020-08-18 12:40 | 2020-09-21 14:29 | MySQL Server: DML | Can't repeat (1487 days) | S3 | 8.0.21 | Any | Any | Renaming the table will cause inconsistent results of other queries |
100428 | 2020-08-04 17:14 | 2020-09-21 16:24 | MySQL Server: Data Dictionary | Can't repeat (1453 days) | S2 | 8.0.21 | Any (Fedora 32) | Any | assertion at database shutdown |
100883 | 2020-09-17 19:21 | 2020-09-22 12:02 | MySQL Server: Performance Schema | Can't repeat (1452 days) | S3 | 8.0.12 | Linux | Any | Performance Schema - Statement Tables - Digest is Null in Stored Procedures |
100795 | 2020-09-10 9:41 | 2020-10-09 12:22 | MySQL Server | Can't repeat (1435 days) | S3 | 5.7.29 | CentOS | Any | join performance_schema.events_statements_history_long with |
100983 | 2020-09-29 6:27 | 2020-10-15 13:44 | Connector / J | Can't repeat (1429 days) | S2 | 5.6.32 | Red Hat ( 4.4.7-18) | Any | the connection is disconnected, but the server CPU consumption is up to 700+% |
101199 | 2020-10-16 2:59 | 2020-10-16 11:58 | MySQL Server: DML | Can't repeat (1428 days) | S3 | 5.7.28 | Windows | Any | the result of replace function is inconsistent under different collations |
102206 | 2021-01-10 4:13 | 2021-01-14 13:23 | MySQL Server | Can't repeat (1338 days) | S2 | 8.0.22 | Ubuntu (20.10-Desktop) | x86 | Using double write buffer is 8x slower in SSD (compared with 2x~3x in HDD) |
102341 | 2021-01-22 8:45 | 2021-01-22 15:28 | MySQL Server | Can't repeat (1330 days) | S3 | 5.7.18 | CentOS (6.6) | Any | Why handle_fatal_signal redirect stderr to binlog index file? |
72735 | 2014-05-24 6:06 | 2021-01-23 17:01 | Connector / NET | Can't repeat (1329 days) | S3 | 6.8.3 | Windows | Any | prepared statement id incorrect in the Statement executed trace data |
102055 | 2020-12-22 22:56 | 2021-01-25 13:04 | MySQL Server: Performance Schema | Can't repeat (1327 days) | S3 | 5.7.19-log | Windows | Any | Performance Schema does not report procedure call |
96384 | 2019-07-31 10:39 | 2021-01-27 13:21 | MySQL Server | Can't repeat (1817 days) | S2 | 5.7.26 | Ubuntu (16.04.6) | Any | MySQL Crash with Assertion failure in file trx0trx.ic |
99234 | 2020-04-12 2:57 | 2021-02-18 13:18 | MySQL Server | Can't repeat (1613 days) | S1 | 8.0.19 | Ubuntu (18.04) | Any (amd64) | Crash on a specific query after upgrading to 8.0.19 |
102715 | 2021-02-24 3:20 | 2021-03-09 13:30 | MySQL Server: InnoDB storage engine | Can't repeat (1284 days) | S3 | 8.0 | Any | Any | InnoDB Discard tablespace is not crash safe |
102596 | 2021-02-15 6:45 | 2021-03-16 13:28 | MySQL Server: Parser | Can't repeat (1277 days) | S3 | 8.0 | Any | Any | Unhandles return value in multiple places |
102877 | 2021-03-09 10:00 | 2021-04-12 12:45 | MySQL Server | Can't repeat (1250 days) | S3 | 8.0.21 | Linux | ARM | x.connection_multi_bind_address_ipv6 failed in arm environment |
103256 | 2021-04-08 17:41 | 2021-04-13 17:51 | MySQL Server | Can't repeat (1249 days) | S3 | 5.7.26 | Debian | Any | Randomly fails to pick obvious index (primary key) for left join |
103260 | 2021-04-09 4:21 | 2021-04-20 23:32 | MySQL Server | Can't repeat (1242 days) | S3 | 8.0.21 | Red Hat (7.9) | Any | Unable to restart mysql server |
103434 | 2021-04-22 16:56 | 2021-04-26 13:23 | MySQL Server | Can't repeat (1239 days) | S3 | 8.0.23 | Ubuntu (18.4) | Any | Bug in MySQL Role MySQL community 8.0.20.23 |
86819 | 2017-06-24 5:56 | 2021-04-27 12:28 | MySQL Server: XA transactions | Can't repeat (1235 days) | S3 | 5.7.17 | Red Hat (Linux 2.6.32-642.13.1.el6.x86_64 #1 SMP Wed Jan 11 20:56:24 UTC 2017 x86_64 x86_64 x86_64 GNU) | Any | XAER_RMFAIL ERROR |
98294 | 2020-01-20 10:37 | 2021-04-29 19:04 | MySQL Server | Can't repeat (1663 days) | S2 | MySQL 5.7.28 | Ubuntu (16.04 LTS OS) | Any | mysqld got signal 6 ; |
100521 | 2020-08-13 16:21 | 2021-05-06 17:57 | MySQL Server | Can't repeat (1488 days) | S3 | 8.0.21 | Windows (Windows 2016) | Any | Cancelling active GR auto-initialization |
85979 | 2017-04-18 8:52 | 2021-05-18 15:55 | MySQL Server: mysqldump Command-line Client | Can't repeat (1254 days) | S3 | 5.7.12 | Ubuntu (14.04) | Any | System memory not released after mysqldump completes |
103356 | 2021-04-18 18:36 | 2021-05-20 13:41 | MySQL Server: Command-line Clients | Can't repeat (1212 days) | S3 | 5.6.51 / 5.7.32 | FreeBSD (12.2 and 13.0) | x86 | load data infile does not accept empty fields |
103603 | 2021-05-06 8:25 | 2021-05-21 12:34 | MySQL Server | Can't repeat (1211 days) | S3 | 5.7.x;8.0.x | Any | Any | heap use after free |
103452 | 2021-04-23 12:23 | 2021-05-27 12:52 | MySQL Server: Prepared statements | Can't repeat (1205 days) | S2 | 8.0.22 | Any | Any | utf8mb4_bin collation not derived by prepared statement, skipping index |
103479 | 2021-04-26 8:56 | 2021-05-31 12:15 | MySQL Server | Can't repeat (1201 days) | S3 | 8.0.23 | FreeBSD (12.2-STABLE) | x86 | tls_ciphersuites ignored in 8.0.23, works in 8.0.22 |
93361 | 2018-11-27 11:21 | 2021-06-11 2:52 | MySQL Server | Can't repeat (1939 days) | S3 | 5.7.17 | CentOS | x86 | memory/performance_schema/table_handles have momery leak! |
100416 | 2020-08-04 1:53 | 2021-06-15 14:18 | MySQL Server | Can't repeat (1495 days) | S3 | 8.0.19 | Red Hat (7.6) | x86 | UTC - mysqld got signal 11 |
103795 | 2021-05-24 19:54 | 2021-06-28 13:08 | MySQL Server | Can't repeat (1173 days) | S3 | 8.0.25-commercial MySQL Enterprise Serve | CentOS (7) | x86 | keyring_okv plugin setup fails |
104367 | 2021-07-20 13:14 | 2021-07-21 1:45 | MySQL Server: Performance Schema | Can't repeat (1150 days) | S3 | 8.0.25 | Linux | Any | Query all the locks in performance.schema.data_locks cause mysqld oom |
104138 | 2021-06-29 3:21 | 2021-08-02 12:21 | MySQL Server: InnoDB storage engine | Can't repeat (1138 days) | S3 | 8.0 | Any | Any | mtr index lock release fail |
104621 | 2021-08-13 19:35 | 2021-08-17 11:47 | MySQL Server | Can't repeat (1123 days) | S3 | 8.0.26 | Other (Official Docker image) | Any | MySQL 8.0.26: Access Denied during GRANT PROXY as root, when connected via TCP/I |
104658 | 2021-08-18 20:11 | 2021-08-25 12:21 | MySQL Server | Can't repeat (1115 days) | S3 | 8.0 | Any | Any | CLIENT_SESSION_TRACK results in inaccurate rows affected on single row inserts |
104735 | 2021-08-26 9:20 | 2021-08-27 11:46 | MySQL Server: InnoDB storage engine | Can't repeat (1113 days) | S3 | 5.7 | Windows (Server 2016 Standard) | Any (Inter Xeon CPU E5620 2.40 GHZ) | InnoDB: A long semaphore wait |
104704 | 2021-08-23 19:56 | 2021-09-27 12:27 | MySQL Server: Stored Routines | Can't repeat (1082 days) | S3 | 8.0.25 | Ubuntu | Any | A stored proc used to refresh a table became unusable with upgrade to 8.0.25 |
104877 | 2021-09-09 3:03 | 2021-10-11 12:48 | MySQL Server | Can't repeat (1068 days) | S3 | 8.0.26 | Any | Any | Linear read-ahead status values no have change |
105277 | 2021-10-20 10:18 | 2021-10-21 13:37 | MySQL Server: User-defined functions ( UDF ) | Can't repeat (1058 days) | S3 | 8.0.23 | CentOS (Centos7) | x86 (x86_64) | The user-defined function failed as the second parameter query of the FIND_IN_SE |
98889 | 2020-03-10 11:10 | 2021-11-16 3:35 | MySQL Server | Can't repeat (1614 days) | S3 | 8.0.18 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 | Crash Recovery & Waiting for GTID thread to start timed out |
105578 | 2021-11-15 14:10 | 2021-11-22 13:50 | MySQL Server | Can't repeat (1026 days) | S2 | 8.0 | Any | Any | Foreign key check 0 is not honored when dropping parent table |
105657 | 2021-11-22 10:21 | 2021-11-22 15:09 | MySQL Server | Can't repeat (1026 days) | S2 | 8.0.27 | Any | Any | Valgrind complains "Invalid write of size 8" |
105293 | 2021-10-22 9:31 | 2021-11-26 12:35 | MySQL Server | Can't repeat (1022 days) | S3 | 5.7.24 | Any | Any | Column 'sys_opt_status' cannot be null |
105803 | 2021-12-06 5:16 | 2021-12-06 13:26 | MySQL Server: Command-line Clients | Can't repeat (1012 days) | S3 | Windows | x86 | mysql.exe Application Error The exception unknown software exception... | |
105858 | 2021-12-10 8:40 | 2021-12-10 13:44 | MySQL Server | Can't repeat (1008 days) | S3 | 8.0 | Any | Any | Memory leak for the innodb_session while killing connection |
105988 | 2021-12-28 7:22 | 2022-01-11 14:09 | MySQL Server: InnoDB storage engine | Can't repeat (976 days) | S3 | 5.7.27/8.0.27 | Red Hat (Red Hat 4.8.5-39) | x86 (3.10.0-1127.10.1.el7.x86_64) | The problem about predicate lock in Serializable isolation level |
105464 | 2021-11-04 23:08 | 2022-01-21 13:37 | MySQL Server: Compiling | Can't repeat (967 days) | S3 | 8.0.27 | MacOS (12.0.1) | Any | MySQL 8.0.27 don't build on macOS 12.0.1 due to fragile cmake code |
106222 | 2022-01-20 8:28 | 2022-01-21 14:18 | MySQL Server: Connection Handling | Can't repeat (966 days) | S3 | 5.7.37, 8.0.28 | Linux | ARM | install/uninstall plugin concurrent with new connections my be deadlock |
104032 | 2021-06-16 7:35 | 2022-01-27 13:52 | Connector / ODBC | Can't repeat (960 days) | S2 | 8.0.25 | Windows (iis 7) | x86 (x64) | asp clasic, error C0000005 when using addnew on text fld |
106285 | 2022-01-26 3:25 | 2022-01-31 13:31 | MySQL Server: mysqlpump Command-line Client | Can't repeat (958 days) | S3 | Ver 8.0.26 for Linux on x86_64 (MySQL Co | Linux | Any | mysqlpump fails with Segmentation fault |
106357 | 2022-02-02 12:35 | 2022-02-02 14:51 | MySQL Server | Can't repeat (954 days) | S3 | 8.0.27 | Red Hat (CentOS 7) | x86 (64) | Alter table add column with algorithm=instant halts all other queries |
106382 | 2022-02-04 18:07 | 2022-02-08 13:32 | MySQL Server | Can't repeat (949 days) | S3 | 5.7.37 | Ubuntu (18.04.6 LTS) | Any | 5.7.37 drops support for symbolic links in the data directory |
85327 | 2017-03-06 18:09 | 2022-02-17 13:40 | MySQL Server: InnoDB storage engine | Can't repeat (939 days) | S3 | 5 | Linux (btr_page_get_prev and btr_page_get_next) | Any | MySQL crash on InnoDB: Failing assertion: btr_page_get_prev(get_page, mtr) == bu |
106553 | 2022-02-24 3:12 | 2022-02-24 14:04 | MySQL Server: Security: Privileges | Can't repeat (932 days) | S3 | 8.0.28 | CentOS | Any | ERROR 1095 (HY000) at line 1: You are not owner of thread 15000 |
106999 | 2022-04-13 8:44 | 2022-04-14 12:02 | MySQL Server: Replication | Can't repeat (883 days) | S2 | 5.7.37 | Any | Any | contributed by Tencent: shutdown hang due to binlog dump stick at wait_new_event |
107149 | 2022-04-28 10:59 | 2022-04-28 14:22 | MySQL Server: InnoDB storage engine | Can't repeat (869 days) | S3 | Any | Any | mysqld got signal 11 at btr_cur_compress_if_useful | |
107177 | 2022-05-02 11:12 | 2022-05-02 13:08 | MySQL Server | Can't repeat (865 days) | S3 | Oracle Linux | x86 | mysqld restart with message mysqld got signal 11 | |
106944 | 2022-04-07 12:28 | 2022-05-09 11:53 | MySQL Server: Optimizer | Can't repeat (858 days) | S5 | 8.0 | Any | Any | can_switch_from_ref_to_range() doesn't work for prepare statement |
107315 | 2022-05-17 11:48 | 2022-05-17 13:58 | MySQL Server: DDL | Can't repeat (850 days) | S3 | 8.0.29 | Any | Any | post_ddl rename space(`t-1`) to converted format (`t@002d1`) by mistake |
107053 | 2022-04-19 12:54 | 2022-05-30 11:53 | MySQL Server | Can't repeat (837 days) | S2 | 5.7.34 | Ubuntu (16.04.1 LTS (Xenial Xerus)) | x86 (x86_64) | Restart of mysql unexpectedly |
107271 | 2022-05-12 11:46 | 2022-06-14 12:11 | MySQL Server: Logging | Can't repeat (822 days) | S3 | 8.0 | Any | Any | XA transaction engine binlog pos info reset |
107594 | 2022-06-19 21:34 | 2022-06-27 18:14 | MySQL Server: InnoDB storage engine | Can't repeat (809 days) | S3 | 8.0.28 | Debian (docker) | Any | crash recovery process stuck with "Out of space in the redo log" |
107740 | 2022-07-03 23:35 | 2022-07-04 12:14 | MySQL Server | Can't repeat (802 days) | S3 | 8.0.29 | Ubuntu (20.04) | Any | Table space missing |
107889 | 2022-07-15 2:14 | 2022-07-15 12:35 | MySQL Server | Can't repeat (791 days) | S1 | 8.0.29 | Linux (Amzon RDS for mysql) | Any | sometimes. when executing UNION querying occurs Signal 11 occures |
107902 | 2022-07-18 13:49 | 2022-07-20 11:52 | MySQL Server | Can't repeat (787 days) | S5 | 8.0.27 | Red Hat | ARM | MySQL slow execution of IN query with PREPARE STATEMENT after upgrading from 5.7 |
107920 | 2022-07-20 7:45 | 2022-07-21 8:46 | MySQL Server: Archive storage engine | Can't repeat (785 days) | S2 | 8.0.29 | Windows (Windows Server 2016 Datacenter) | Any | exception 0xc0000005 |
107953 | 2022-07-23 12:33 | 2022-07-26 12:32 | MySQL Server: InnoDB storage engine | Can't repeat (780 days) | S3 | Any | Any | Query crash when building pre version of blob column | |
107968 | 2022-07-26 2:36 | 2022-07-26 14:24 | MySQL Server | Can't repeat (780 days) | S3 | Debian | x86 | MySQL crashes with InnoDB errors | |
107987 | 2022-07-26 19:39 | 2022-07-27 12:20 | MySQL Server: Stored Routines | Can't repeat (779 days) | S3 | 8.0.27 | Any | Any | DROP FUNCTION ERROR 1109 (442S02) if function references INNODB_SYS tables |
107919 | 2022-07-20 7:23 | 2022-07-27 12:52 | MySQL Server | Can't repeat (779 days) | S3 | 8.0.29 | Any | Any | InnoDB: insufficient history for index 0 |
108044 | 2022-08-01 10:43 | 2022-08-01 14:22 | MySQL Server: Installing | Can't repeat (774 days) | S3 | 8.0.30 | CentOS (7.9.2004) | x86 | First login failed when installer generate a password contains ">". |
108051 | 2022-08-02 13:37 | 2022-08-03 12:17 | MySQL Server: Stored Routines | Can't repeat (772 days) | S3 | 5.7 | Any | Any | Empty parameter name in MySQL 5.7 routines |
108006 | 2022-07-28 3:57 | 2022-08-03 12:30 | MySQL Server: C API (client library) | Can't repeat (772 days) | S3 | 8.0.28 | SUSE | Any | recipe for BLOBs and mysql_stmt_fetch(), using mysql_stmt_fetch_column() broken |
107806 | 2022-07-08 3:22 | 2022-08-12 11:40 | MySQL Server: InnoDB storage engine | Can't repeat (763 days) | S5 | 8.0.19 | Any | Any | AIO systerm optimize |
108141 | 2022-08-15 15:47 | 2022-08-16 12:47 | MySQL Server | Can't repeat (759 days) | S3 | 8.0.29 and 8.0.30 | Ubuntu (20.04.4 LTS) | x86 | Memory leak after upgrade from 8.0.28 to 8.0.29+ |
108206 | 2022-08-20 21:04 | 2022-08-22 12:01 | Shell Dump & Load | Can't repeat (753 days) | S3 | mysqlsh Ver 8.0.29 for Linux on x86_64 | Ubuntu | x86 | Dump utility does not chunk deterministically, which breaks differential backups |
108194 | 2022-08-19 3:22 | 2022-08-22 12:12 | MySQL Server: JSON | Can't repeat (756 days) | S3 | 8.0.30 | Any (12.4) | Any (64) | When I use JSON_CONTAINS(), the multi-value index is not used |
108211 | 2022-08-22 4:59 | 2022-08-22 12:59 | MySQL Server | Can't repeat (753 days) | S3 | Ver 8.0.30-0ubuntu0.22.04.1 for Linux o | Ubuntu | x86 | linux mysql partial query not displaying correctly before commit |
108269 | 2022-08-24 14:49 | 2022-08-25 12:07 | MySQL Server: Charsets | Can't repeat (750 days) | S3 | 5.7.38 8.0.29 | Linux | Any | Have the same character set and collation, but different results |
108288 | 2022-08-25 22:22 | 2022-08-29 11:51 | MySQL Server | Can't repeat (749 days) | S3 | 8.0.29 | Any | Any | HIGH_NUMBER_OF_BYTES_USED is incorrect |
108352 | 2022-08-31 14:52 | 2022-09-01 12:00 | MySQL Server: Query Cache | Can't repeat (743 days) | S3 | 10.4.24 | Windows (Windows 10) | Other ((AMD64) AMD A10-7870K Radeon R7 3.90 GHz) | From Virtual Column get Warning |
108343 | 2022-08-31 7:10 | 2022-09-02 11:28 | MySQL Server | Can't repeat (742 days) | S3 | 5.7.25 | Linux (CentOS release 6.6) | x86 (Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz) | mysql 5.7.25 sql stuck in closing table |
108186 | 2022-08-18 9:28 | 2022-09-19 13:37 | MySQL Server | Can't repeat (725 days) | S3 | 8.0.30 | Ubuntu (20.04) | x86 (AMD Ryzen 7 Pro 5850U) | mysqld got signal 11 when upgrade 8.0.29 to 8.0.30 |
107914 | 2022-07-19 15:14 | 2022-09-27 11:58 | MySQL Server: InnoDB storage engine | Can't repeat (786 days) | S3 | Any | Any | corruption in the InnoDB tablespace | |
108628 | 2022-09-28 8:20 | 2022-09-28 12:53 | MySQL Server: Connection Handling | Can't repeat (716 days) | S3 | 8.0.27 | Ubuntu | Any | I saved 1941-10-01, 1942-09-01, 1906-01-01 date on my DB and when I am trying to |
108632 | 2022-09-28 11:34 | 2022-09-29 12:01 | MySQL Server: Errors | Can't repeat (715 days) | S2 | 8.0.23 | Linux | Any | SQLSTATE[HY000]: General error: 1105 Unknown error |
108234 | 2022-08-23 7:00 | 2022-10-03 12:29 | MySQL Server: Replication | Can't repeat (711 days) | S3 | mysql 8.0.28 | Any | Any | A Document incorrect regarding Replication with Differing Table Definitions |
108675 | 2022-10-04 1:46 | 2022-10-05 11:43 | MySQL Server | Can't repeat (709 days) | S3 | 8.0.27 | Any | Any | Error log information was provided during mysql initialization |
108686 | 2022-10-05 11:08 | 2022-10-05 14:02 | MySQL Server: Optimizer | Can't repeat (709 days) | S3 | 8.0.28 | Any | x86 | Bug usibg limit 1 sub select |
108704 | 2022-10-06 19:32 | 2022-10-07 13:08 | MySQL Server | Can't repeat (707 days) | S3 | 8.0.30 | Red Hat (Rocky Linux 8) | x86 | Mysql failed to start after installation of Mysql Community 8.0.30 |
108716 | 2022-10-09 13:31 | 2022-10-10 13:20 | MySQL Server | Can't repeat (704 days) | S3 | 8.0.29 / 8.0.30 | Any | Any | Damaged table, unable to remove and repair |
108575 | 2022-09-22 7:45 | 2022-10-13 13:15 | MySQL Workbench | Can't repeat (701 days) | S2 | 8.0.30 | Windows (10 Professional) | x86 (AMD Ryzen 5 5500U) | Hardware accelerated ERR diagram renderer freezes application |
108752 | 2022-10-12 11:01 | 2022-10-14 9:01 | MySQL Server: Installing | Can't repeat (700 days) | S2 | 8.0.31 | Windows | Any | installer: Illegal mix of collations |
108729 | 2022-10-10 16:06 | 2022-10-14 13:28 | MySQL Server: FULLTEXT search | Can't repeat (701 days) | S3 | 8.0.30 | Linux | x86 | Adding fulltext index results in duplicate entry error for unrelated key |
108808 | 2022-10-18 7:25 | 2022-10-18 12:41 | MySQL Server: Optimizer | Can't repeat (696 days) | S5 | 8.0.27 | Red Hat (CentOS Linux release 7.9.2009 (Core)) | x86 | MySQL optimizer: the execution order of explain execution plan and explain analy |
71520 | 2014-01-30 8:43 | 2022-10-31 13:19 | MySQL Server: Locking | Can't repeat (2328 days) | S3 | 5.6.14 | Any (CentOS release 5.6) | Any | Constantly increasing Innodb_row_lock_current_waits value |
108836 | 2022-10-20 14:36 | 2022-10-31 13:53 | MySQL Server | Can't repeat (683 days) | S3 | 8.0.22 | Any | Any | update table set b = a, c = b; Inconsistent expected results |
108919 | 2022-10-28 14:19 | 2022-11-03 13:02 | MySQL Server: Security: Privileges | Can't repeat (681 days) | S2 | 8.0 | Any | Any | acl_cache_lock is not consistent in acl_authenticate function for proxy_user |
109138 | 2022-11-18 16:24 | 2022-11-18 16:33 | MySQL Server | Can't repeat (665 days) | S3 | 8.0.30 | Ubuntu (22.04.4) | Any | Assertion failure: os0file.cc:2872 |
96650 | 2019-08-26 7:01 | 2022-11-21 19:57 | MySQL Server | Can't repeat (1810 days) | S3 | 8.0.17 | Any | Any | SERVER_MORE_RESULTS_EXISTS is not set when response multiple BINLOG statements |
109124 | 2022-11-17 14:58 | 2022-11-22 6:44 | MySQL Server | Can't repeat (665 days) | S1 | 8.0 | Linux (Redhat, CentOS, Kylin) | Any | skip scan retrieves incorrect result after delete |
108990 | 2022-11-03 14:59 | 2022-11-22 13:04 | MySQL Server: Charsets | Can't repeat (661 days) | S3 | 8.0.29 | Debian (11) | x86 | Update integer value via integer key raises collation error |
109188 | 2022-11-24 4:09 | 2022-11-25 13:01 | MySQL Server | Can't repeat (658 days) | S3 | 8.0.28 | Any | Any | mysql_real_connect() giving error on trying to connect Mysql 8.0.28 and above |
109216 | 2022-11-28 6:02 | 2022-11-28 13:03 | MySQL Server | Can't repeat (655 days) | S2 | 5.7.39 | Any | Any | ERROR 1345 (HY000): EXPLAIN/SHOW can not be issued; lacking privileges for under |
109230 | 2022-11-29 9:19 | 2022-11-29 12:57 | MySQL Server | Can't repeat (654 days) | S2 | 8.0.30 | Windows | Any | could not import all the data from csv file |
109297 | 2022-12-06 12:03 | 2022-12-06 13:08 | Shell General / Core Client | Can't repeat (647 days) | S3 | 8.0.31 | CentOS (7.9.2009) | x86 | MySQL client 8.0 showing "fwrite: Broken pipe" on large query when using a pager |
109301 | 2022-12-06 23:05 | 2022-12-08 4:36 | MySQL Server | Can't repeat (645 days) | S2 | 8.0.31 | Fedora | Any | MySQL 5.7 -> 8.0.31 Page old data size XXX new data size YYY error |
109310 | 2022-12-08 1:52 | 2022-12-09 3:12 | MySQL Cluster: Replication | Can't repeat (644 days) | S2 | 5.7.30 to 8.0.31 | Linux | Any | Fail to upgrade MySQL5.7 cluster to MySQL 8 |
109329 | 2022-12-09 12:54 | 2022-12-12 10:20 | MySQL Workbench | Can't repeat (641 days) | S3 | 8.0 CE | Windows (Windows 10) | Any | MySQL Workbench has encountered a problem when I try to open a .mvb file |
109055 | 2022-11-10 16:12 | 2022-12-12 12:59 | MySQL Workbench | Can't repeat (641 days) | S1 | 8.0.31 | Windows (during windows update) | Any | Computer in a "sleep" state, signed on the windows did an update, workbench ope |
109357 | 2022-12-13 7:11 | 2022-12-13 12:55 | MySQL Server | Can't repeat (640 days) | S3 | Mysql Operator 8.0.31 | Ubuntu | x86 | TLS/SSL Certificates with MySQL Operator now working |
109342 | 2022-12-12 14:13 | 2022-12-15 12:43 | MySQL Server | Can't repeat (639 days) | S3 | 8.0.31 | Windows (Server 2016 Standard) | Other (Xeon CPU E5-2670 (2 processors)) | Randomly crashes and stops mysql server |
109121 | 2022-11-17 11:31 | 2022-12-19 12:50 | MySQL Utilities: Binlog Events | Can't repeat (634 days) | S3 | Ver 8.0 | Any | Any | add my_b_bytes_in_cache in IO_CACHE_binlog_cache_storage::next before my_b_fill |
109428 | 2022-12-19 15:42 | 2022-12-19 16:09 | MySQL Server | Can't repeat (634 days) | S3 | Any | Any | bug, as I'm opening sqly it is showing some kind of bug. Kindly fix it | |
109438 | 2022-12-20 15:17 | 2022-12-23 12:26 | MySQL Server: Installing | Can't repeat (630 days) | S1 | 8.0.31 | Windows (Windows 10) | Any | MySQL installation stuck on "Initializing database (may take a long time)" |
109260 | 2022-12-01 12:20 | 2023-01-03 12:51 | MySQL Server: InnoDB storage engine | Can't repeat (619 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
109515 | 2023-01-03 11:03 | 2023-01-03 14:33 | MySQL Server | Can't repeat (619 days) | S2 | 8.0.30 | Windows | Any | Out of memory (Needed 1062936 bytes) |
109320 | 2022-12-08 13:19 | 2023-01-05 13:20 | MySQL Server | Can't repeat (645 days) | S3 | 8.0.31 | CentOS (CentOS Linux release 7.9.2009 (Core)) | x86 (Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz) | mysql freeze on SHOW GLOBAL STATUS |
109349 | 2022-12-12 23:36 | 2023-01-10 12:54 | MySQL Server: DDL | Can't repeat (612 days) | S2 | 8.0.31 | Windows | Any | "Could not load libmysql.dll" when using MYSQL 8.0.31 |
109563 | 2023-01-10 5:25 | 2023-01-10 13:07 | MySQL Server: InnoDB storage engine | Can't repeat (612 days) | S3 | 8.0.31 | Ubuntu (20.04.4) | x86 | show engine innodb status:Innodb_data_pending_fsyncs Is Constantly Rising |
108086 | 2022-08-08 5:39 | 2023-02-06 14:11 | MySQL Server | Can't repeat (665 days) | S2 | Server version: 8.0.30-0ubuntu0.20.04.2 | Ubuntu (20) | Any | Backup crash server - Assertion failure: block->page.get_space() != nullptr |
109859 | 2023-01-31 9:36 | 2023-02-06 14:35 | MySQL Server: InnoDB storage engine | Can't repeat (585 days) | S5 | 8.0.30 | Ubuntu (20.04) | x86 | very slow converting table to row_format=compressed |
110008 | 2023-02-09 12:20 | 2023-02-09 13:42 | MySQL Server | Can't repeat (582 days) | S3 | 8.0.25 | Linux | Any | Crash at sp_prepare_func_item(THD*, Item**) when calling a procedure |
110014 | 2023-02-10 1:29 | 2023-02-10 13:34 | MySQL Server | Can't repeat (581 days) | S3 | 5.7.38 | CentOS | x86 | Crash during pquery: process_str_arg & my_vsnprintf_ex |
110099 | 2023-02-16 14:00 | 2023-02-17 12:19 | MySQL Workbench: Migration | Can't repeat (574 days) | S3 | 8.0.32 Build 261262 CE 64 bits | Windows (Windows 11 Pro) | Any (Intel i7 Quad core) | MySQL Workbench Migration Postgres to MySQL Error |
110110 | 2023-02-17 12:25 | 2023-02-21 13:07 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (570 days) | S3 | 8.0.31 | Red Hat (8.7) | x86 (Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz) | MGR SECONDARY UNREACHABLE |
110094 | 2023-02-16 7:34 | 2023-02-22 13:55 | MySQL Server: Replication | Can't repeat (569 days) | S2 | 8.0.25 | Any | Any | When slave replays the STOP EVENT, the stop slave will cause a dead cycle |
110268 | 2023-03-03 10:16 | 2023-03-03 14:45 | MySQL Server: InnoDB storage engine | Can't repeat (560 days) | S2 | 8.0.25 | Linux | ARM | ibuf cursor restoration fails |
110269 | 2023-03-03 13:28 | 2023-03-03 15:05 | MySQL Server | Can't repeat (560 days) | S3 | 8.0.30 | Ubuntu (Rel 20.04.2) | Any (Intel Xeon E5620) | Server crashed on ALTER TABLE. Now crashes on SELECT. |
109289 | 2022-12-06 8:20 | 2023-03-06 13:48 | MySQL Server | Can't repeat (557 days) | S3 | 8.0.30, 8.0.32 | Windows (Server 2019) | Any | MySQL 8.0.32 corrupted table causing MySQL to crash |
110416 | 2023-03-17 16:21 | 2023-03-20 14:43 | MySQL Server: General | Can't repeat (543 days) | S3 | 8.0.32 | Ubuntu (22.04) | x86 (x86_64) | mysqld strange exit code |
110399 | 2023-03-16 15:42 | 2023-03-21 13:49 | MySQL Utilities: Binlog Events | Can't repeat (543 days) | S3 | 8.0.28 | Any | Any | Incorrect Signedness in Table Map Binlog Event for Int Following Year |
110382 | 2023-03-15 18:35 | 2023-03-27 13:40 | MySQL Websites: bugs.mysql.com | Can't repeat (536 days) | S3 | 8.0.32 | Ubuntu (mysql server has gone away) | Any | SQLSTATE[HY000] [2006] MySQL server has gone away |
110514 | 2023-03-27 14:29 | 2023-03-27 14:49 | Shell VSCode Extension | Can't repeat (536 days) | S3 | 1.9.1 | Windows | Any | managing my society database |
109490 | 2022-12-28 3:39 | 2023-04-03 12:40 | MySQL Server: Performance Schema | Can't repeat (619 days) | S3 | 8.0.24 | CentOS (7.7.1908) | x86 (x86_64) | memory_summary_by_thread_by_event_name display wrong value |
110598 | 2023-04-04 5:40 | 2023-04-04 13:11 | MySQL Server | Can't repeat (528 days) | S3 | 8.0.30 | Windows (Windows Server 2016 Datacenter) | x86 (Intel Xeon Silver 4216) | [ERROR] [MY-013183] [InnoDB] Assertion failure: fsp0fsp.cc:2152:inode thread |
110625 | 2023-04-06 10:32 | 2023-04-06 12:52 | MySQL Server: Documentation | Can't repeat (526 days) | S3 | Any | Any | Flickering | |
110633 | 2023-04-07 5:20 | 2023-04-07 11:55 | MySQL Server | Can't repeat (525 days) | S3 | 8.0.32 | CentOS | Any | Orphaned full-text indexes |
110676 | 2023-04-13 8:46 | 2023-04-13 11:52 | MySQL Server | Can't repeat (519 days) | S2 | 8.0.32 | Ubuntu (20.04) | x86 | mysqld got signal 11 after update from 8.0.31 to 8.0.32 |
107894 | 2022-07-15 10:58 | 2023-04-19 13:18 | MySQL Server: Command-line Clients | Can't repeat (513 days) | S3 | 8.0 | Any | Any | mysql client crash when FIDO device is not present |
106280 | 2022-01-25 14:14 | 2023-05-10 12:01 | MySQL Server: InnoDB storage engine | Can't repeat (928 days) | S3 | 5.7 | Any | Any | innodb print tons of partial read in error log |
110991 | 2023-05-11 10:23 | 2023-05-11 12:41 | MySQL Server | Can't repeat (491 days) | S2 | 8.0.33 | Ubuntu (20.04.1) | x86 | After server upgrade it does not start |
110592 | 2023-04-03 10:00 | 2023-05-11 12:54 | MySQL Server: FULLTEXT search | Can't repeat (491 days) | S3 | 8.0.30 | Any | Any | InnoDB FULLTEXT search result lost a record when recovery from a crash |
110972 | 2023-05-10 7:14 | 2023-05-12 2:59 | MySQL Server: FULLTEXT search | Can't repeat (491 days) | S2 | 8.0.32 | Linux | Any | Innodb Fulltext search returns incorrect results when kill and restart mysqld |
111029 | 2023-05-15 12:01 | 2023-05-15 12:29 | MySQL Server | Can't repeat (487 days) | S3 | 8.0.29 | Red Hat (7.6) | x86 | corruption in the InnoDB tablespace |
111043 | 2023-05-16 10:58 | 2023-05-16 15:19 | MySQL Server: DDL | Can't repeat (486 days) | S1 | 8.0.33 | Windows | Any | Table data corrupt after upgrading MySql from 5.7.37 to MySql 8.0.33 version |
111044 | 2023-05-16 13:12 | 2023-05-16 15:20 | MySQL Server: InnoDB storage engine | Can't repeat (486 days) | S2 | 8.0.33 | Fedora (36) | x86 | Assertion failure in buf0buf.cc::Buf_fetch<T>::read_page() |
111073 | 2023-05-18 12:14 | 2023-05-18 12:50 | MySQL Server | Can't repeat (484 days) | S3 | 5.7.41 | CentOS | x86 | The mutil-layer subquery results are inconsistent after group by. |
111102 | 2023-05-22 9:40 | 2023-05-23 12:01 | MySQL Server: InnoDB storage engine | Can't repeat (480 days) | S5 | 8.0.* | CentOS | x86 | Performance issue in simulated AIO in sysbench oltp_insert auto_inc mode |
111198 | 2023-05-30 10:42 | 2023-05-30 12:11 | MySQL Server: Optimizer | Can't repeat (472 days) | S3 | 8.0.31 | Any | Any | Using index for skip scan optimization produces wrong result |
111063 | 2023-05-17 20:39 | 2023-05-31 12:04 | MySQL Server: InnoDB storage engine | Can't repeat (472 days) | S1 | 5.7.42, 8.0.31, 8.0.32, 8.0.33 | Any | Any | Assert: !dummy_big_rec on rollback of delete or update of row_format=compressed. |
111302 | 2023-06-06 18:35 | 2023-06-07 12:45 | MySQL Server | Can't repeat (464 days) | S3 | 8.0.32 build 2612062 CE (64 bits) | Any | Any | Returns OK in Message |
111323 | 2023-06-07 20:22 | 2023-06-13 12:00 | MySQL Server | Can't repeat (459 days) | S3 | 8.0.28 | Any | Any | Index column size too large. The maximum column size is 767 bytes. |
111382 | 2023-06-13 3:46 | 2023-06-13 12:37 | MySQL Server | Can't repeat (458 days) | S3 | latest | Any (ran number of tables) | Any | got abug |
111420 | 2023-06-14 12:37 | 2023-06-14 13:25 | MySQL Server | Can't repeat (457 days) | S2 | 8.0.32 | Ubuntu | Other | DB instance restarted with AWS RDS database |
111414 | 2023-06-14 9:26 | 2023-06-16 9:32 | MySQL Server: Optimizer | Can't repeat (455 days) | S3 | 8.0.33 | Any | Any | HASH JOIN results in wrong query results |
111463 | 2023-06-16 16:28 | 2023-06-19 11:36 | MySQL Server: Windows | Can't repeat (452 days) | S3 | 8.0.31 | Windows (2019 Datacenter) | x86 (Intel) | File .\undo_002: 'aio write' returned OS error 1560. Cannot continue operation |
111626 | 2023-06-30 7:09 | 2023-06-30 13:26 | MySQL Server | Can't repeat (441 days) | S3 | 8.0.23-commercial | Any | Any | The MGR configuration is partially incorrect as expected |
111621 | 2023-06-29 12:03 | 2023-07-03 1:20 | MySQL Server | Can't repeat (438 days) | S3 | 8.0.22 | Any | Any | Crash occured when run sql query on 8022 debug environment |
111647 | 2023-07-04 2:41 | 2023-07-06 12:14 | MySQL Server: JSON | Can't repeat (435 days) | S3 | 8.0.33 | Linux | x86 | Blob partial update in undo record may lead potential crash |
111442 | 2023-06-15 19:02 | 2023-07-17 12:48 | MySQL Server | Can't repeat (424 days) | S3 | 8.0.32 | Any | Any | misleading startup error message related to GTID configuration |
110345 | 2023-03-11 21:50 | 2023-07-18 12:50 | MySQL Server | Can't repeat (512 days) | S2 | 8.0.32 | MacOS (Ventura 13.0.1) | ARM | MySQL crash on MacOS typically when restoring a MySQL 5.7 sql |
111812 | 2023-07-19 10:13 | 2023-07-19 12:51 | MySQL Server: InnoDB storage engine | Can't repeat (422 days) | S3 | 8.0.33 | Linux | ARM | Unable to open '#innodb_redo/#ib_redo31_tmp', no permission |
111811 | 2023-07-19 9:38 | 2023-07-20 14:06 | MySQL Server | Can't repeat (421 days) | S2 | 8.0.33 | Linux | x86 | UPDATE statement with JOIN doesn't update any records |
111833 | 2023-07-20 22:09 | 2023-07-21 13:06 | MySQL Server | Can't repeat (420 days) | S3 | all | Any | Any | couldn't distinguish a normal resultset from an OUT parameter set |
111848 | 2023-07-21 16:55 | 2023-07-24 12:33 | MySQL Server: C API (client library) | Can't repeat (417 days) | S3 | 8.0.32-1 | Red Hat (8) | ARM | libmysqlclient.a missing on mysql-devel-8.0.32-1.module_el8.8.0+3567+56a616e4.aa |
111859 | 2023-07-24 8:43 | 2023-07-24 13:16 | MySQL Server | Can't repeat (417 days) | S3 | Any | Any | assertion fails by shutdown trx_sys_close: m_views and trx_sys->mysq | |
111882 | 2023-07-25 12:36 | 2023-07-25 12:41 | MySQL Workbench | Can't repeat (416 days) | S3 | Windows | Any | mysql workbench | |
111906 | 2023-07-27 16:43 | 2023-07-27 17:49 | MySQL Workbench | Can't repeat (414 days) | S3 | 8.0.34 | Any | Any | I can not open my MySQL connection on the MySQL Workbench |
111961 | 2023-08-03 18:21 | 2023-08-03 18:32 | MySQL Server | Can't repeat (407 days) | S3 | 8.0.34 | Windows (Windows Server 2019) | Other (x64) | MySQL 8.0.34 crashing suddenly |
111962 | 2023-08-03 18:27 | 2023-08-03 19:14 | MySQL Workbench: Administration | Can't repeat (407 days) | S1 | 8.0.34 | Windows | x86 | MySQL Workbench 8.0.34 with MySQL innovation 8.1 |
111946 | 2023-08-02 15:12 | 2023-08-04 12:12 | MySQL Server | Can't repeat (408 days) | S3 | 5.7 | Debian | Any | Fulltext index not being maintained, nothing shows up in error log or mysqlcheck |
111971 | 2023-08-04 10:54 | 2023-08-07 12:50 | MySQL Server: Data Types | Can't repeat (403 days) | S3 | MySQL Community Server 8.1.0 | Windows (Python MySQl connector V8) | x86 | Data format changed during Select/Insert query |
111987 | 2023-08-07 11:26 | 2023-08-08 12:25 | MySQL Server | Can't repeat (402 days) | S3 | 5.7.42 | Any | Any | Error filesort result when max_length_for_sort_data is set to a big value |
112012 | 2023-08-09 12:33 | 2023-08-09 13:13 | MySQL Server | Can't repeat (401 days) | S3 | 8.0.32 | Red Hat | Any | [Warning] [MY-011825] [InnoDB] |
111978 | 2023-08-04 14:22 | 2023-08-10 14:27 | MySQL Cluster: Replication | Can't repeat (400 days) | S1 | 8.0.30 | CentOS (CentOS Linux release 7.7.1908 (Core)) | x86 (Intel(R) Xeon(R) Gold 5220 CPU @ 2.20GHz) | Our PRD env mysql 8.0.30 group-replication cluster lost some data |
111872 | 2023-07-25 6:46 | 2023-08-15 7:05 | MySQL Server | Can't repeat (395 days) | S3 | 8.0.33 | Red Hat (RHEL 8.8) | x86 | VIEW reference in a SELECT subquery returns different results between 5.7 & 8.0 |
112032 | 2023-08-10 12:57 | 2023-08-16 11:53 | MySQL Server: C API (client library) | Can't repeat (395 days) | S3 | 8.0.33 | CentOS | Any | Using C program to execute query and report errors |
112099 | 2023-08-17 11:36 | 2023-08-17 13:44 | MySQL Server: Information schema | Can't repeat (393 days) | S3 | 8.0.25 | Linux | x86 | The query result is incorrect. |
112111 | 2023-08-18 8:54 | 2023-08-18 12:50 | MySQL Server | Can't repeat (392 days) | S3 | 8.1.0 | Any | Any | Incorrect query results on comparing with SOME including some null value |
112103 | 2023-08-18 2:02 | 2023-08-18 13:03 | MySQL Server: Data Types | Can't repeat (392 days) | S3 | Any | Any | The query takes too long to execute with no results | |
112148 | 2023-08-23 3:34 | 2023-08-23 12:53 | MySQL Server | Can't repeat (387 days) | S3 | 8.0.34 | Red Hat (Red Hat Enterprise Linux Server 7.7(Maipo)) | x86 (Hygon C86 7375) | Description Failed to upgrade mysql from 8.0.20 to 8.0.34 |
112176 | 2023-08-24 14:01 | 2023-08-25 12:31 | MySQL Server | Can't repeat (385 days) | S3 | Any (Parameter not valid window appears) | Any | Unable to run SQL due to parameter not valid | |
112178 | 2023-08-25 3:38 | 2023-08-25 14:12 | MySQL Server: InnoDB storage engine | Can't repeat (385 days) | S3 | 8.0.34 | Any | Any | Transaction inconsistency when the undo space truncate is incomplete |
97707 | 2019-11-20 12:39 | 2023-09-12 10:49 | MySQL Server: Group Replication | Can't repeat (367 days) | S1 | all version with MGR | Any | Any | group replication lost transaction when init by ansible |
98151 | 2020-01-08 1:03 | 2023-09-12 11:14 | MySQL Server: Group Replication | Can't repeat (367 days) | S3 | 8.0.18 | Any | Any | group replication with wrong member_state after server shutdown |
111052 | 2023-05-17 0:49 | 2023-09-20 1:39 | MySQL Server | Can't repeat (485 days) | S3 | 5.7.40-enterprise-commercial-advanced-lo | Windows | Any | Mysql connections will hang for several minutes |
112372 | 2023-09-18 7:19 | 2023-09-21 9:36 | MySQL Server: Parser | Can't repeat (358 days) | S3 | 8.0.33 | MacOS | x86 | Select query returns duplicate rows |
112378 | 2023-09-19 2:03 | 2023-09-25 11:01 | MySQL Server: Optimizer | Can't repeat (355 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
112421 | 2023-09-22 1:46 | 2023-09-25 11:02 | MySQL Server | Can't repeat (355 days) | S3 | 8.0.32 | CentOS (7) | Any | zero and null value, left or right join result wrong |
112154 | 2023-08-23 7:38 | 2023-09-25 11:06 | MySQL Server: DML | Can't repeat (354 days) | S3 | 8.0.34 | Any | Any | Slow Queries Exceeding 1 Second in Concurrent Insert Scenario on MySQL 8.0.34 |
112454 | 2023-09-25 7:50 | 2023-09-25 11:26 | MySQL Server: Optimizer | Can't repeat (354 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
112453 | 2023-09-25 7:42 | 2023-09-25 11:28 | MySQL Server: Optimizer | Can't repeat (354 days) | S3 | 8.0.28 | Any | Any | Incorrect result |
112581 | 2023-09-30 20:49 | 2023-10-02 12:31 | MySQL Server | Can't repeat (347 days) | S3 | 8.0 | Other (Docker) | x86 | "Plugin mysql_native_password reported"- user already uses caching_sha2_password |
112583 | 2023-10-02 2:47 | 2023-10-02 16:55 | MySQL Server: CSV | Can't repeat (347 days) | S3 | 8.0.27 | Ubuntu | x86 | Inconsistencies have been observed using COUNT and COALESCE(SUM…) |
112446 | 2023-09-24 23:24 | 2023-10-03 10:07 | MySQL Server | Can't repeat (347 days) | S2 | 8.0.34 | Debian (Debian 11) | x86 (x86-64) | Fractured read at SERIALIZABLE |
112714 | 2023-10-13 12:45 | 2023-10-16 14:02 | MySQL Server: Clone Plugin | Can't repeat (336 days) | S3 | 8.0.34 | Any | Any | Assertion failure: clone0api.cc:1159:ib::fatal in cloning when undo_x_trunc.log |
111909 | 2023-07-28 7:02 | 2023-10-18 10:21 | MySQL Websites: bugs.mysql.com | Can't repeat (331 days) | S5 | 8.0.28 | CentOS | x86 | While using federate tables in mysql 8.0.28 getting communication packet error |
112761 | 2023-10-18 10:55 | 2023-10-18 11:59 | MySQL Server: Partitions | Can't repeat (331 days) | S3 | 8.0.2 | Any | Any | Partition prune always with the first partition when range(to_days(xxx)) |
107447 | 2022-06-01 15:25 | 2023-10-25 0:25 | Connector / J | Can't repeat (324 days) | S3 | 8.0.29 | Any | Any | Delete-select not working with temporary tables |
112897 | 2023-10-31 11:44 | 2023-11-02 11:50 | MySQL Server: InnoDB storage engine | Can't repeat (316 days) | S3 | 8.0.32 | Linux | Any | next-transaction isolation level has problem if current transaction end by begin |
112934 | 2023-11-02 2:27 | 2023-11-02 13:39 | MySQL Server: Errors | Can't repeat (316 days) | S5 | MySQL 8.0 | Any | Any | mysqld assertion failure in os_file_fsync_posix |
112694 | 2023-10-12 0:00 | 2023-11-09 11:50 | MySQL Server | Can't repeat (337 days) | S2 | 8.0.34 | Linux | Any | MYSQL master crashes frequently after upgrade from 8.0.28 to 8.0.34 |
112990 | 2023-11-07 13:21 | 2023-11-09 14:59 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Can't repeat (309 days) | S2 | 5.7.43 | Any | Any | MySQL cluster hang forever |
113035 | 2023-11-10 6:05 | 2023-11-10 12:43 | MySQL Server: Optimizer | Can't repeat (308 days) | S3 | CentOS | Any | why MySQL 8.0.32 chooses wrong drive tables in this situation | |
113054 | 2023-11-12 10:36 | 2023-11-13 10:40 | MySQL Server: Optimizer | Can't repeat (305 days) | S3 | 8.0.32 | CentOS | Any | mysql explain filtered inaccurate when find_in_set function used |
113100 | 2023-11-16 8:52 | 2023-11-16 13:06 | MySQL Server | Can't repeat (302 days) | S3 | 8.0.18 | Red Hat (7.6) | x86 (x64) | [FATAL] fsync() returned EIO,aborting.[InnoDB] Assertion failure: ut0ut.cc:532 |
91078 | 2018-05-30 13:37 | 2023-11-20 11:34 | MySQL Server | Can't repeat (298 days) | S3 | 5.7.21 | Red Hat (RHEL 6.7) | x86 | Queries stuck in 'query end' forever |
112650 | 2023-10-06 11:25 | 2023-11-23 13:25 | MySQL Workbench: Migration | Can't repeat (295 days) | S3 | 8.0.33 | Windows (Microsoft Windows 10 Pro) | Any | Faulting application name: wbcopytables.exe |
113229 | 2023-11-27 7:57 | 2023-11-27 11:11 | MySQL Server: Replication | Can't repeat (291 days) | S3 | 8.0.33 | Any (CentOS Linux 7) | Any | mysqld: Duplicate entry 'mysql/slave_worker_info' for key 'tablespaces.name' |
113276 | 2023-11-29 5:55 | 2023-11-29 13:00 | MySQL Server | Can't repeat (289 days) | S3 | 8.0.24 | CentOS (7.9) | x86 | MYSQL does not respond after applications are inserted in batches |
113334 | 2023-12-05 8:32 | 2023-12-05 10:38 | MySQL Server | Can't repeat (283 days) | S2 | 8.0.30 | Windows (2016) | Any (12 CPUs) | Mysql memory bloating and causing server out of memory |
113343 | 2023-12-05 18:12 | 2023-12-15 14:13 | MySQL Server | Can't repeat (273 days) | S3 | 8.0.32 | Windows (Windows server 2019 standard) | Any | Expression #1 of ORDER BY is not in SELECT / incompatible with DISTINCT (#3065) |
113380 | 2023-12-08 16:36 | 2023-12-16 18:59 | Connector / NET | Can't repeat (273 days) | S2 | 8.0.32 | Windows (2019 Server) | Any | MySql.Data Client creates trailing space in datetime parameter causing app crash |
113463 | 2023-12-19 16:07 | 2023-12-20 11:54 | MySQL Server: Data Types | Can't repeat (268 days) | S3 | 8.0 | Any | Any | bigint、int、tinyint数据类型bug 8.0版本 |
113466 | 2023-12-19 18:31 | 2023-12-20 13:47 | MySQL Server | Can't repeat (268 days) | S3 | 8.0.34 | Windows | x86 | MySQL provides Truncated incorrect DOUBLE value: '0A000' error in trigger |
113469 | 2023-12-20 6:54 | 2023-12-20 15:44 | MySQL Server | Can't repeat (268 days) | S5 | 8.0 | Any | Any | Affected by Bug 104576 partition table access second index lead to cpu high load |
113422 | 2023-12-14 13:14 | 2023-12-20 15:57 | MySQL Server: Compiling | Can't repeat (270 days) | S3 | 8.2.0 | Any | Any | Handler_test.TableCreateReturnsRecordFileFullWhenTempTableAllocatorThrowsRecordF |
113360 | 2023-12-07 11:17 | 2023-12-21 13:38 | Connector / ODBC | Can't repeat (280 days) | S2 | 8.2 | Windows | Any | ODBC driver 8.2 causes crash when setting prefetch option |
113524 | 2023-12-29 8:08 | 2024-01-08 13:25 | MySQL Server: InnoDB storage engine | Can't repeat (249 days) | S3 | 8.0.35 | Any | Any | Value in ibuf bitmap page of R-Tree could be incorrect after recovery |
113535 | 2024-01-02 9:58 | 2024-01-08 13:31 | MySQL Server: DDL | Can't repeat (249 days) | S3 | 8.0.35 | Any | Any | Drop table in background list will remain file exists in directory |
113439 | 2023-12-15 11:03 | 2024-01-15 10:11 | MySQL Server: DDL | Can't repeat (272 days) | S3 | 8.0.35 | Linux | Any | Alter database charset lead to cpu high load |
113663 | 2024-01-17 11:37 | 2024-01-17 12:04 | MySQL Server: Replication | Can't repeat (240 days) | S3 | 8.0.32 | CentOS | x86 | Crash occurs when applying binlog_transaction_dependency_tracking to slave node. |
113706 | 2024-01-22 11:46 | 2024-01-22 13:20 | MySQL Server: Errors | Can't repeat (235 days) | S3 | mysql Ver 8.0.35 for Linux on 86_64 | Linux (Centos 7 Linux ) | x86 (x86_64) | InnoDB : Corruption of an index tree which stopped mysqld service |
113742 | 2024-01-24 13:37 | 2024-01-24 19:50 | MySQL Operator | Can't repeat (233 days) | S1 | 8.2.0-2.1.1 | Any | Any | the container' file system changed to read-only |
113759 | 2024-01-25 12:15 | 2024-01-25 13:58 | MySQL Server | Can't repeat (232 days) | S3 | 8.0.0.33 | Any | Any | Program crashes when I try to access the reverse engineering tab |
111944 | 2023-08-02 13:14 | 2024-01-29 8:59 | Connector / ODBC | Can't repeat (231 days) | S2 | 8.0.36 | Windows | x86 | Issue with ADO transactions when using MySQL Connector ODBC 8.0.33 32-bit |
113791 | 2024-01-29 11:59 | 2024-01-29 12:15 | MySQL Workbench: SQL Editor | Can't repeat (228 days) | S3 | Any | Any | Can't use MySQL | |
113793 | 2024-01-29 13:13 | 2024-01-29 13:29 | MySQL Workbench | Can't repeat (228 days) | S2 | 8.0.32 | Windows | Any | Parameter not found |
113831 | 2024-01-31 11:28 | 2024-01-31 13:17 | MySQL Server: Command-line Clients | Can't repeat (226 days) | S3 | 8.0.35 | Windows (windows server 2016) | Any | mysql crashes ramdonally during backup |
113844 | 2024-02-01 3:30 | 2024-02-02 11:15 | MySQL Server | Can't repeat (224 days) | S5 | 8.0.16 | Ubuntu | Any | The execution time of queries and written statements took a long time |
113862 | 2024-02-02 6:22 | 2024-02-02 12:11 | MySQL Server: InnoDB storage engine | Can't repeat (224 days) | S3 | Any | Any | problem with btree latch acquisition when updating histogram | |
113889 | 2024-02-04 6:17 | 2024-02-05 11:08 | MySQL Server: Locking | Can't repeat (221 days) | S3 | Any | Any | Lock is not released when thread is killed | |
109542 | 2023-01-06 1:22 | 2024-02-19 11:18 | MySQL Server: JSON | Can't repeat (550 days) | S2 | 8.0.30 | Linux | Any | Multiple different-looking crashes after upgrade to 8.0.30 |
113950 | 2024-02-10 23:25 | 2024-02-19 12:32 | MySQL Server: InnoDB storage engine | Can't repeat (210 days) | S3 | 8.0.30 | Linux | x86 | MySQL 8.0.30 is stuck due to the processing of a large transaction |
114060 | 2024-02-20 10:13 | 2024-02-20 13:42 | MySQL Server | Can't repeat (206 days) | S3 | 8.0.28 | Ubuntu | Any | Unreasonable SQL Error (1054) |
114133 | 2024-02-27 2:39 | 2024-02-27 12:38 | MySQL Server: InnoDB storage engine | Can't repeat (199 days) | S3 | 8.3.0-debug | Oracle Linux (v9, WSL v2 over Windows11) | x86 | dd corrupt assert lob0impl.cc:1237:total_read == len || total_read == avail_lob |
114152 | 2024-02-28 7:53 | 2024-02-29 10:50 | MySQL Server: Command-line Clients | Can't repeat (197 days) | S2 | mysqldump Ver 8.0.36-0ubuntu0.22.04.1 | Ubuntu (Pop!_OS 22.04 LTS) | x86 (Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz) | Invalid mysqldump file generated for some views with collate statements |
114181 | 2024-03-01 9:43 | 2024-03-01 11:45 | MySQL Server | Can't repeat (196 days) | S3 | 8.0.31 | Windows (Server 2022 Standard (21H2)) | x86 (Xeon Gold 6242 CPU * 2) | MySQL Crashes on query with row_number over order by concat with cast to char |
114158 | 2024-02-28 13:09 | 2024-03-05 12:11 | MySQL Workbench | Can't repeat (192 days) | S2 | 8.0.36 | Windows (Win 10 Pro) | Any | unable to connect to a new database |
114240 | 2024-03-06 8:12 | 2024-03-06 15:02 | MySQL Server: Compiling | Can't repeat (191 days) | S3 | Any | Any | LeakSanitizer has encountered a fatal error | |
110266 | 2023-03-03 6:40 | 2024-03-14 6:59 | MySQL Server: Group Replication | Can't repeat (556 days) | S3 | 8.0.27 | Any | Any | The secondary node of the mgr cluster has a deadlock |
114386 | 2024-03-18 5:01 | 2024-03-26 11:09 | MySQL Server | Can't repeat (178 days) | S3 | 8.0.31 | CentOS | Any | MySQL server sometimes suddenly hangs, queries to tables global_status also hang |
114469 | 2024-03-25 2:55 | 2024-03-26 11:15 | MySQL Server | Can't repeat (171 days) | S3 | 8.0 | Any | Any | utf8mb4_general_ci can't convert to utf8mb4_0900_ai_ci |
114466 | 2024-03-24 15:15 | 2024-03-26 11:25 | MySQL Server: Partitions | Can't repeat (171 days) | S3 | mysql 8.0 | CentOS | x86 | online ddl and virtual column related crash problems |
114538 | 2024-04-03 7:13 | 2024-04-03 10:34 | MySQL Server: Optimizer | Can't repeat (163 days) | S3 | 8.0 | Any | Any | Item_ref replaced by new item in Item_ref::transform lead to wrong result |
114544 | 2024-04-03 12:28 | 2024-04-03 14:07 | MySQL Server | Can't repeat (163 days) | S3 | 8.0.36 | MacOS | ARM | MySQL crash after too many INSTANT DDL |
114546 | 2024-04-04 1:11 | 2024-04-05 10:22 | MySQL Server | Can't repeat (162 days) | S3 | 8.0.36 | Debian | x86 | function sometime returns a NULL value |
114570 | 2024-04-08 2:00 | 2024-04-08 10:00 | MySQL Server: mysqldump Command-line Client | Can't repeat (158 days) | S2 | 8.0.35 | Debian | x86 | Error running mysqldump with tables with big blobs on docker |
114580 | 2024-04-08 10:41 | 2024-04-09 11:35 | MySQL Server | Can't repeat (157 days) | S5 | 8.0.35 | Ubuntu (Ubunutu 20.04 LTS) | x86 | Mysql 8.0.35 - The query to get foreign keys are slower than MySQL 8.0.20 |
114286 | 2024-03-08 18:15 | 2024-04-09 18:49 | MySQL Server | Can't repeat (157 days) | S1 | 8.0.36 | Debian (12) | x86 | Using Clone Recovery for addInstance on MySQL Innodb Cluster uses 100% Memory |
114629 | 2024-04-12 8:43 | 2024-04-15 9:59 | MySQL Server | Can't repeat (154 days) | S3 | 8.0.34 | Any | Any | partially upgraded DD |
114661 | 2024-04-16 22:51 | 2024-04-17 10:41 | MySQL Server | Can't repeat (149 days) | S3 | 8.0.30 | Any | Any | ibuf_merge_or_delete_for_page cause crash |
109292 | 2022-12-06 9:28 | 2024-04-18 12:39 | Connector / J | Can't repeat (148 days) | S2 | 8.0.19 and later | Any (Windows server) | Any | Retrieval of DateTime field with the value lost in DST lost hour causes error |
114684 | 2024-04-18 13:54 | 2024-04-18 16:46 | MySQL Server | Can't repeat (148 days) | S3 | 8.0.36 | Any | Any | Inconsistent data representation |
114738 | 2024-04-23 8:03 | 2024-04-23 9:38 | MySQL Server | Can't repeat (143 days) | S3 | 8.0.27 | Any (Linux) | Any | tried to purge non-delete-marked record in index `idx_code` of table |
114743 | 2024-04-23 11:30 | 2024-04-23 11:58 | MySQL Server | Can't repeat (143 days) | S3 | Any | Any | result incorrect | |
114756 | 2024-04-24 7:10 | 2024-04-24 9:55 | MySQL Server | Can't repeat (142 days) | S3 | 8.0.27 | CentOS (CentOS Linux release 7.6.1810 (Core) ) | Any (32 cores) | The purge thread cause the server crash |
114809 | 2024-04-29 7:35 | 2024-04-29 10:20 | MySQL Server: InnoDB storage engine | Can't repeat (137 days) | S3 | 8.0.32 | Any | Any | inconsistent page no in btr_pcur_t's move_to_next_page |
114803 | 2024-04-27 13:38 | 2024-04-29 10:31 | MySQL Server: InnoDB Plugin storage engine | Can't repeat (137 days) | S3 | 8.0.28 | Any | Any | rename table failed |
97709 | 2019-11-20 13:03 | 2024-04-30 16:32 | MySQL Server: InnoDB storage engine | Can't repeat (1711 days) | S5 | 8.0.17 | Ubuntu (Ubuntu 18.04.1 LTS) | Any | MySQL 8 Select Count(*) is very slow |
114931 | 2024-05-09 7:17 | 2024-05-09 10:42 | MySQL Server: General | Can't repeat (127 days) | S3 | 8.0.30 | Linux | Any | start transaction read only not work |
114944 | 2024-05-09 12:58 | 2024-05-09 13:31 | MySQL Server: DML | Can't repeat (127 days) | S3 | Any | Any | cant open the database | |
114704 | 2024-04-19 14:25 | 2024-05-13 7:09 | MySQL Workbench: SQL Editor | Can't repeat (123 days) | S1 | 8.0.34 | MacOS (12.7.4) | Any | Black box covering line numbers |
114960 | 2024-05-10 18:19 | 2024-05-13 10:36 | MySQL Server: C API (client library) | Can't repeat (123 days) | S3 | MySQL 8.4 | Linux (Amazon Linux 2) | x86 | ssl_session_data_print |
114965 | 2024-05-11 7:03 | 2024-05-13 13:34 | MySQL Server | Can't repeat (123 days) | S3 | 5.7,8.0 | Any | Any | The user has permission to the DB, but denied to SELECT it |
114964 | 2024-05-11 6:36 | 2024-05-14 10:36 | MySQL Server: DDL | Can't repeat (122 days) | S3 | 8.0 | Any | Any | update statistics for a specified index |
114995 | 2024-05-14 10:00 | 2024-05-14 12:53 | MySQL Server: DML | Can't repeat (122 days) | S3 | 8.0.28 && 8.0.30 | CentOS (7.9) | x86 (3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) | by using 'with ....as ...inner join ...' bug |
114988 | 2024-05-13 17:02 | 2024-05-14 22:50 | MySQL Server | Can't repeat (122 days) | S3 | 8.0.36 | Fedora | x86 | WHERE ({date} < zeroDate OR zeroDate is NULL) is incorrect in MySQL 8 |
115025 | 2024-05-16 5:56 | 2024-05-16 9:58 | MySQL Server: mysqlpump Command-line Client | Can't repeat (120 days) | S2 | Linux (Rocky) | Any | mysqldump: Error: 'Access denied; need PROCESS privileges for Tablespaces | |
115032 | 2024-05-16 8:27 | 2024-05-17 20:45 | MySQL Server | Can't repeat (119 days) | S3 | Linux | Any | -DHAVE_V8=OFF Missing connection symbol, causing error | |
115024 | 2024-05-16 5:04 | 2024-05-17 20:46 | MySQL Server: Replication | Can't repeat (119 days) | S2 | 8.0.33 | Linux (Rocky Linux release 8.9) | Any | MySQL Crash occurs during MySQL Replication stop process |
115047 | 2024-05-17 7:12 | 2024-05-20 9:34 | MySQL Server: XA transactions | Can't repeat (119 days) | S3 | 8.0.32 | Ubuntu (ubuntu0.20.04.2 ) | Any | XA_prepare_log_event holds an invalid XID |
115059 | 2024-05-20 9:10 | 2024-05-20 9:56 | MySQL Server | Can't repeat (116 days) | S3 | 8.0 | Linux | x86 | record in index not found on update |
115078 | 2024-05-22 9:54 | 2024-05-22 14:08 | MySQL Server | Can't repeat (114 days) | S3 | 8.0.37 | Any (Linux) | Any | RC isolation happen dead lock like gap lock |
115102 | 2024-05-23 15:15 | 2024-05-29 16:54 | MySQL Workbench | Can't repeat (107 days) | S2 | 8.0.36 | Ubuntu (22.04) | x86 | Welcome Screen does not decrease in size once resized to be larger |
115132 | 2024-05-27 2:48 | 2024-05-31 7:13 | MySQL Server: Charsets | Can't repeat (105 days) | S3 | 8.0.32 | Any | Any | group by with COLLATE return unexpected result |
115197 | 2024-06-03 10:43 | 2024-06-03 12:15 | Connector / NET | Can't repeat (102 days) | S3 | 8.0.33 | Windows | x86 | Post upgrade 8.0.33 - 8.0.35 .net nullable exception writes |
115198 | 2024-06-03 13:09 | 2024-06-03 14:00 | MySQL Workbench | Can't repeat (102 days) | S2 | 8.0 | Any | x86 | On windpw 10 start up |
115216 | 2024-06-04 16:46 | 2024-06-04 17:18 | MySQL Server: Optimizer | Can't repeat (101 days) | S5 | 8.0.34 | Any | Any | range_optimizer_max_mem_size calculation on with large IN queries |
114934 | 2024-05-09 7:33 | 2024-06-05 2:06 | MySQL Server: Replication | Can't repeat (100 days) | S3 | 5.7.44 | Any | Any | In Heavy workload, it degenerates to use single thread replication in fact |
115207 | 2024-06-04 7:15 | 2024-06-05 9:23 | MySQL Server | Can't repeat (100 days) | S3 | 8.0.22 | Any | Any | mysql 8.0.22 mysqld got signal 11 |
115212 | 2024-06-04 13:19 | 2024-06-05 9:30 | MySQL Server | Can't repeat (100 days) | S3 | 8.0.36 | Debian | Any | duplicates_removal weedout semijoin crashes mysql8 |
115232 | 2024-06-05 14:04 | 2024-06-06 12:07 | MySQL Workbench | Can't repeat (99 days) | S2 | 8.0.36 | Windows (10) | x86 | MySQL Workbench has encountered a problem during search |
115362 | 2024-06-17 14:58 | 2024-06-18 10:04 | MySQL Server | Can't repeat (88 days) | S2 | 8.0.37 | Any | Any | Incorrect result in simple query with condition false |
115371 | 2024-06-18 17:07 | 2024-06-18 17:46 | MySQL Server | Can't repeat (87 days) | S3 | MySQL80 | Any | Any | parameter not defined |
115422 | 2024-06-25 6:40 | 2024-06-25 10:15 | MySQL Server | Can't repeat (80 days) | S3 | 8.0.36 | Linux (AlmaLinux 8.4) | Any | MySQL 8.0.36 restart frequently unexpected |
115259 | 2024-06-10 6:20 | 2024-06-28 13:25 | MySQL Server: Optimizer | Can't repeat (95 days) | S3 | 8.0.34 | Any | Any | query_rewrite not working in 8.0.34 |
115438 | 2024-06-27 2:53 | 2024-07-01 8:05 | MySQL Operator | Can't repeat (74 days) | S3 | Linux | x86 | the pod alway terminating | |
115459 | 2024-06-28 16:07 | 2024-07-01 9:47 | MySQL Server | Can't repeat (77 days) | S3 | 8.0.34 | Ubuntu (20.04.6 LTS) | x86 (Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz) | global read_only = 1 with read only = 0 on schema level blocks writes to schema |
115463 | 2024-06-29 18:03 | 2024-07-01 11:32 | MySQL Server | Can't repeat (74 days) | S3 | 8.0.20 | Any | Any | select wrong value after update statement when another session update the same r |
115490 | 2024-07-02 14:06 | 2024-07-03 9:09 | MySQL Server: Optimizer | Can't repeat (73 days) | S3 | 8.4,8.0,5.7 | Any | Any | Different execution plans erroneously have the same execution cost (query_cost). |
110765 | 2023-04-21 18:26 | 2024-07-03 9:20 | MySQL Server: Stored Routines | Can't repeat (73 days) | S3 | 8.0.32 | Linux (EC2) | Any | Function returns incorrect value inside a session |
115512 | 2024-07-04 12:14 | 2024-07-04 12:20 | MySQL Server | Can't repeat (71 days) | S3 | 8.0.36 | Red Hat (8.8) | x86 | MySQL 8.0.36 crashed due to Assertion failure error |
115547 | 2024-07-09 9:04 | 2024-07-09 10:05 | MySQL Server | Can't repeat (66 days) | S3 | 8.4.0 | Windows (Microsoft Windows 11 Pro) | Any | against('+m\'otorbuch' in boolean mode) no result but it should deliver one |
115573 | 2024-07-12 10:48 | 2024-07-15 9:34 | MySQL Server | Can't repeat (63 days) | S3 | 8.4 | Red Hat | x86 | mysql_secure_installation: unknown variable default-character-set=utf8mb4 |
115351 | 2024-06-17 4:32 | 2024-07-15 13:49 | MySQL Server: InnoDB storage engine | Can't repeat (88 days) | S3 | mysql-8.0.32 | Any | Any | page tracking cannot find stop point |
115449 | 2024-06-27 14:07 | 2024-07-16 10:34 | Connector / J | Can't repeat (59 days) | S2 | 8.2.0 | Any | Any | NativePacketPayload.readInteger causes ArrayIndexOutOfBoundsException |
115437 | 2024-06-26 18:17 | 2024-07-16 12:22 | MySQL Server | Can't repeat (59 days) | S3 | 8.0 | Any | Any | Query rewrite plugin not working |
115625 | 2024-07-17 9:27 | 2024-07-17 9:54 | MySQL Server | Can't repeat (58 days) | S3 | 8.0.33 | Any | Any | blob supports exceptions after java object serialization |
115632 | 2024-07-17 15:07 | 2024-07-17 15:36 | MySQL Server: Compiling | Can't repeat (58 days) | S3 | Any | Any | issue in importing and compiling data files | |
115651 | 2024-07-19 14:25 | 2024-07-19 14:40 | MySQL Server | Can't repeat (56 days) | S3 | 8.0.30 | CentOS | x86 | mysql8 cannot drop database or table |
115073 | 2024-05-22 3:10 | 2024-07-24 17:10 | MySQL Operator | Can't repeat (51 days) | S3 | 8.4.0-2.1.3 | CentOS (CentOS7) | x86 | Handler 'on_pod_create' failed temporarily: Sidecar of mysql-innodbcluster-2 is |
115701 | 2024-07-26 17:11 | 2024-07-29 8:57 | MySQL Server | Can't repeat (49 days) | S3 | 8.0.36 | CentOS (Linux 3.10.0-1160.76.1.el7.x86_64) | x86 (Linux 3.10.0-1160.76.1.el7.x86_64) | [ERROR] [MY-012441] [InnoDB] Unable to find a record to delete-mark |
113285 | 2023-11-29 16:22 | 2024-07-30 6:25 | Connector / ODBC | Can't repeat (45 days) | S2 | 8.0.33 | Windows | Any | ODBC error reading DECIMAL values : Multiple-step OLE DB operation ... |
114208 | 2024-03-04 15:41 | 2024-07-31 5:45 | MySQL Workbench | Can't repeat (45 days) | S3 | 8.0.31, 8.0.32, 8.0.33, 8.0.34, 8.0.36 | Windows (10, 11) | Any | table update fails with an "Column xxxx cannot be null" error. |
115732 | 2024-07-31 13:57 | 2024-08-01 19:05 | MySQL for Windows: Installer | Can't repeat (43 days) | S2 | v8.0.39 | Windows (Pro x64 English) | x86 (x64) | MySql installer hangs after successful installation |
115774 | 2024-08-05 17:18 | 2024-08-05 17:43 | MySQL Workbench | Can't repeat (39 days) | S3 | 8.0 CE | Windows | Any | MySQL Workbench: Index out of range |
115522 | 2024-07-05 9:43 | 2024-08-06 10:33 | MySQL Server: Compiling | Can't repeat (70 days) | S3 | 8.0.38 | Any | x86 (intel xeon) | MySQL fails to build on centos 9 stream |
115792 | 2024-08-07 19:10 | 2024-08-08 9:15 | MySQL Server | Can't repeat (36 days) | S3 | 8.0 | Windows (11) | x86 (intel core i5) | Gif file stored as blob in table is not able to open |
115727 | 2024-07-30 11:37 | 2024-08-09 13:18 | MySQL Server: Group Replication | Can't repeat (35 days) | S3 | 8.0.36 | Red Hat | x86 | MySQL InnoDB Cluster - Systemd - Kill the process |
115766 | 2024-08-05 8:36 | 2024-08-12 9:33 | MySQL Server: InnoDB storage engine | Can't repeat (35 days) | S3 | 8.0.35 | Linux (RDS) | Any | Database page corruption on disk or a failed file read of page |
115811 | 2024-08-09 18:59 | 2024-08-12 19:51 | MySQL Server: Replication | Can't repeat (32 days) | S3 | 8.0.35-27 | Ubuntu (Only Tested on Ubuntu) | Any | Replication Delay consistent at 1 second. |
115823 | 2024-08-13 3:03 | 2024-08-13 14:59 | MySQL Server | Can't repeat (31 days) | S3 | 8.0.28 | Any | Any | When the select .. from .. where xx < .. order by xx asc limit .., .. command |
115847 | 2024-08-16 2:35 | 2024-08-16 9:46 | MySQL Server | Can't repeat (28 days) | S3 | 8.0.27 | CentOS | x86 | Mysql Server memory trap |
115852 | 2024-08-16 14:19 | 2024-08-19 9:45 | MySQL Server | Can't repeat (28 days) | S3 | 8.0.37,9.0.1 | Any | Any | allocated memory to prepared statement are not releaed after connection gone. |
115860 | 2024-08-19 11:03 | 2024-08-20 8:26 | MySQL Server: InnoDB storage engine | Can't repeat (25 days) | S5 | 8.0.37 | Linux | x86 | CPU IDLE consumption regression introduced in 8.0.30 |
115891 | 2024-08-22 9:24 | 2024-08-22 10:53 | MySQL Workbench | Can't repeat (22 days) | S2 | 8.0.38 | Windows (Microsoft Windows 10 Home) | Any | I cannot see the wizard to upload date from CSV to a table in my Schema. |
Showing all 503 (Edit, Save, CSV, Feed) |