| Showing all 100 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 109547 | 2023-01-07 20:23 | 2023-01-15 18:15 | MySQL Server: C API (client library) | Analyzing (460 days) | S1 | 5.7, 8.0 | Windows | Any | Query return NO_DATA, when the data is present |
| 85634 | 2017-03-27 2:08 | 2017-03-28 13:35 | MySQL Server: C API (client library) | Verified (2579 days) | S1 | 5.7.7 | SUSE | Any | C API prepared statement update/insert MYSQL_TYPE_TINY fails with 8th bit |
| 89359 | 2018-01-23 13:05 | 2021-02-05 13:08 | MySQL Server: Command-line Clients | Verified (1169 days) | S1 | 5.6, 5.7, 8.0, 5.6.39, 5.7.21, 5.7.33, 8.0.23 | Linux | Any | Segmentation fault if multibyte character used in prompt string |
| 81429 | 2016-05-16 8:53 | 2016-05-16 9:05 | MySQL Server: Command-line Clients | Verified (2895 days) | S1 | 5.7.12 | CentOS (7) | Any | innochecksum rises an error with encryption enabled table at page 1 |
| 81782 | 2016-06-09 3:44 | 2022-10-22 2:20 | MySQL Server: Command-line Clients | Verified (545 days) | S1 | 5.7.12, 5.6.31, 5.7.13 | Any | Any | --binary-mode disables SOURCE command |
| 81784 | 2016-06-09 4:52 | 2018-03-02 2:43 | MySQL Server: Command-line Clients | Verified (2240 days) | S1 | 5.7.12, 5.5.50, 5.6.31, 5.7.13 | Any | Any | Position of --force within command line matters for mysql client |
| 99857 | 2020-06-12 3:32 | 2021-08-05 10:16 | MySQL Server: Command-line Clients | Verified (1338 days) | S1 | 5.7.31，8.0.20 | Any | Any | mysql_use_result() can't get result if slave no set slave_uuid |
| 67290 | 2012-10-18 16:10 | 2015-08-10 14:34 | MySQL Server: mysqldump Command-line Client | Verified (4159 days) | S1 | 5.5.27, 5.5.30, 5.7.1, 5.1.67 | Linux (RHEL 5.5 linux2.6 (x86_64) ) | Any | mysqldump 5.5.27 throws error 1049 while dumping routines for db with spl chrs |
| 93008 | 2018-10-30 13:34 | 2019-04-01 21:26 | MySQL Server: mysqldump Command-line Client | Verified (1997 days) | S1 | 5.6.41, 5.6.42, 5.7.23, 5.7.24 | Linux | x86 | mysqldump crashes with segmentation fault on last 5.6 and 5.7 versions |
| 81926 | 2016-06-20 8:50 | 2020-07-27 12:17 | MySQL Server: mysqldump Command-line Client | Verified (2860 days) | S1 | 5.7.11, 5.7.13 | CentOS (6.5) | Any | mysqldump produce wrong sql on table with virtual json column as primary key |
| 86807 | 2017-06-23 3:07 | 2019-03-05 4:16 | MySQL Server: mysqldump Command-line Client | Verified (2485 days) | S1 | 5.7.16 | Any | Any | mysqldump export empty mysql.proc |
| 89076 | 2017-12-29 7:39 | 2021-01-11 9:56 | Connector / NET | Verified (2279 days) | S1 | 5.7.19 | Linux (AWS RDS) | Any | Application has timeout exception,Still find queries getting executed on backend |
| 113432 | 2023-12-15 0:35 | 2024-01-08 13:23 | MySQL Package Repos | Verified (126 days) | S1 | 5.7 | Ubuntu | x86 | Expired Package repo |
| 86251 | 2017-05-10 2:43 | 2017-05-10 6:11 | MySQL Utilities: Binlog Events | Verified (2536 days) | S1 | 5.7.17, 5.7.18 | Any | Any | Assertion `head->variables.gtid_next.type == ANONYMOUS_GROUP' failed. |
| 85706 | 2017-03-30 11:19 | 2017-05-18 4:24 | MySQL Cluster: Cluster (NDB) storage engine | Verified (2535 days) | S1 | mysql-5.7.17 ndb-7.5.5 | Oracle Linux (6.8 (Santiago) kernel 4.1.12-37.4.1.el6uek.x86_64) | Any | Rowid already allocated under heavy load |
| 104584 | 2021-08-10 14:27 | 2021-08-12 3:20 | MySQL Server: Compiling | Verified (982 days) | S1 | 5.7.35 | Ubuntu (20.04) | x86 | Freshly built mysql client crashes in libedit/terminal.c |
| 76688 | 2015-04-14 13:47 | 2015-07-06 11:54 | MySQL Server: Compiling | Analyzing (3210 days) | S1 | 5.6.24, 5.7.7-rc | Linux (CentOS 7) | Any | -DMYSQL_DATADIR impact on compiling MySQL with cmake |
| 96942 | 2019-09-19 9:03 | 2020-03-19 15:04 | MySQL Server: Connection Handling | Verified (1663 days) | S1 | 5.7. 8.0, 8.0.17 | Linux | Any | net_read_timeout and net_write_timeout do not work |
| 88299 | 2017-10-30 15:39 | 2017-12-24 18:26 | MySQL Server: CSV | Verified | S1 | 5.7.17 | Windows | Any | csv:binlog corruption, abort, An error occurred during flush stage of the commit |
| 71299 | 2014-01-05 12:36 | 2017-10-31 7:31 | MySQL Server: CSV | Verified (3757 days) | S1 | 5.7.4 | Windows | Any | simple DML causes too many corrupt csv tables. |
| 74480 | 2014-10-21 11:44 | 2018-01-01 3:30 | MySQL Server: DDL | Verified (3147 days) | S1 | 5.6.20-debug,5.6.26, 5.6.27, 5.6.28, 5.7.8 and 5.7.9 | Linux (CentOS 7) | Any | Failing assertion: os_file_status(newpath, &exists, &type), os0file.cc line 1950 |
| 80360 | 2016-02-14 2:09 | 2016-02-17 16:08 | MySQL Server: DDL | Verified (2984 days) | S1 | 5.7, 5.7.12 | Any | Any | CREATE TABLE .. SELECT on table with TIMESTAMP column raises error with 5.7 |
| 93728 | 2018-12-22 3:12 | 2019-01-21 6:41 | MySQL Server: DDL | Verified (1945 days) | S1 | 5.7.18 | Linux | x86 | mysqld crash after using alter table with SPATIAL key |
| 87835 | 2017-09-22 8:19 | 2018-12-19 1:41 | MySQL Server: DML | Verified (2401 days) | S1 | 5.7.19 | Ubuntu (Ubuntu 16.04.2 LTS) | Any | the combination of SELECT DISTINCT and ORDER BY give wrong result for some data |
| 86253 | 2017-05-10 4:31 | 2017-10-13 12:30 | MySQL Server: DML | Verified (2536 days) | S1 | 5.7.17, 5.7.18 | Any | Any | Errno: 168 - Unknown (generic) error from engine on RENAME TABLE |
| 103278 | 2021-04-12 6:56 | 2021-04-12 9:36 | MySQL Server: DML | Verified (1103 days) | S1 | 8.0, 8.0.23, 5.7.33 | Any | Any | SUM(decimal) produces wrong result |
| 91720 | 2018-07-19 16:16 | 2018-08-20 10:28 | MySQL Server: DML | Verified (2069 days) | S1 | 5.7.22 | Ubuntu (16.04 LTS) | Any | Different results when using a subquery based on a view compared to a table |
| 81684 | 2016-06-02 6:05 | 2016-06-02 13:22 | MySQL Server: DML | Verified (2878 days) | S1 | 5.7.8, 5.6.30, 5.7.12 | Any | Any | select + where exists( select + group by + limit) works incorrectly |
| 74747 | 2014-11-08 7:20 | 2015-02-05 7:55 | MySQL Server: DML | Verified (3361 days) | S1 | 5.6.20, 5.6.22, 5.7.5 | Any | Any | Failing assertion: index->id == btr_page_get_index_id(page) btr0cur.cc line 899 |
| 73946 | 2014-09-17 9:17 | 2014-09-25 8:46 | MySQL Server: DML | Verified (3502 days) | S1 | 5.5.39/5.6/5.7 | Windows (x64) | Any | Wrong result with agregate with join with no resultset |
| 79830 | 2016-01-04 9:42 | 2016-01-04 12:08 | MySQL Server: DML | Verified (3028 days) | S1 | 5.7.8, 5.5.48, 5.6.28, 5.7.10 | Any | Any | IN operator works incorrectly with NULL |
| 80118 | 2016-01-22 14:45 | 2016-01-25 9:59 | MySQL Server: DML | Verified (3007 days) | S1 | 5.6.26, 5.6.28, 5.7.10 | Any | Any | STR_TO_DATE doesn't work properly |
| 77509 | 2015-06-26 14:22 | 2015-06-27 5:54 | MySQL Server: Errors | Verified (3219 days) | S1 | MySQL5.6.21, 5.6.27, 5.7.8, 5.5.46 | CentOS | Any | Using an alias to perform DELETE statement in information_schema |
| 82330 | 2016-07-25 5:55 | 2024-04-06 9:15 | MySQL Server: FULLTEXT search | Verified (13 days) | S1 | 5.7.13, 5.7.22, 8.0.16, 8.3.0 | CentOS (6.6) | Any | Don't recursively-evaluate stopword after tokenize |
| 102833 | 2021-03-05 18:04 | 2021-03-05 20:25 | MySQL Server: FULLTEXT search | Verified (1141 days) | S1 | 5.7.33 | Ubuntu | x86 | Fulltext index error [ERROR] InnoDB: Duplicate FTS_DOC_ID value on table |
| 82581 | 2016-08-15 10:21 | 2021-11-03 0:08 | MySQL Server: Group Replication | Verified (2657 days) | S1 | 5.7.14 | CentOS (7) | Any | altering table engine from innodb to memory will break group replication |
| 97266 | 2019-10-17 2:39 | 2022-08-29 3:34 | MySQL Server: Group Replication | Verified (1638 days) | S1 | 5.7.28 | CentOS (aliyun ECS CentOS 7.4) | x86 | GR fail to start,conflict with k8s CNI(flannel) |
| 91722 | 2018-07-20 3:08 | 2018-11-01 8:40 | MySQL Server: Group Replication | Verified (2075 days) | S1 | 5.7.22 | Any | Any | MGR may becomes a one-member-online system but still provide service |
| 92159 | 2018-08-23 13:37 | 2018-08-27 8:45 | MySQL Server: GIS | Verified (2062 days) | S1 | 5.7/8.0 | Windows | Any | st_intersects with srid 4326 unexpected values as a result |
| 69100 | 2013-04-30 9:53 | 2015-03-15 20:45 | MySQL Server: InnoDB storage engine | Verified (4001 days) | S1 | 5.5.31-0, 5.5.30-1, 5.5.29-0, 5.5.25-1, 5.5.16, 5.5.30-1.1, 5.6.10, 5.0.97, 5.1.70, 5.5.29, 5.7.2 | Linux (Debian 6 / Debian 7 / Ubuntu 12.10 / Windows 8) | Any | CAST in IF function fails in some case |
| 88808 | 2017-12-07 10:03 | 2018-01-01 22:23 | MySQL Server: InnoDB storage engine | Verified (2300 days) | S1 | 5.7.20 | Any | Any | InnoDB errors on mysql db tables when using innodb-force-recovery |
| 75910 | 2015-02-15 21:00 | 2015-02-27 23:00 | MySQL Server: InnoDB storage engine | Verified (3339 days) | S1 | 5.7.5-m15, 5.6.23 | Any | Any | Odd tablespace discard messages in error log |
| 89098 | 2018-01-03 15:07 | 2018-01-04 14:14 | MySQL Server: InnoDB storage engine | Verified (2297 days) | S1 | 5.7/8.0 | Any | Any | Adding an auto_increment column to existing table creates gaps |
| 86809 | 2017-06-23 8:47 | 2018-12-13 3:52 | MySQL Server: InnoDB storage engine | Verified (2492 days) | S1 | 5.7.18 | Any | Any | Failed to drop tablespace after unsuccessful attempt to create partitioned table |
| 80268 | 2016-02-04 13:18 | 2016-02-05 7:58 | MySQL Server: InnoDB storage engine | Verified (2996 days) | S1 | 5.7.10 | CentOS (7) | Any | Can create general tablespace with same name several times after crash |
| 89534 | 2018-02-05 13:06 | 2020-02-05 10:17 | MySQL Server: InnoDB storage engine | Verified (2264 days) | S1 | 5.7.21 | Any | Any | Crash during innodb recovery when working with encryption |
| 86257 | 2017-05-10 5:53 | 2023-07-21 16:54 | MySQL Server: InnoDB storage engine | Verified (2536 days) | S1 | 5.7.17, 5.7.18 | Any | Any | Error log: Got error 155 when reading table |
| 80183 | 2016-01-28 8:03 | 2016-06-18 21:45 | MySQL Server: InnoDB storage engine | Verified (3004 days) | S1 | 5.7.10 | CentOS (7) | Any | ALTER TABLESPACE is not crash resistant |
| 82060 | 2016-06-30 2:55 | 2019-05-08 4:17 | MySQL Server: InnoDB storage engine | Verified (2850 days) | S1 | 5.7.12, 5.7.13 | CentOS (CentOS release 6.5 (Final)) | Any | mysqld will read dropped table when it start |
| 108087 | 2022-08-08 10:23 | 2022-08-11 15:12 | MySQL Server: InnoDB storage engine | Verified (617 days) | S1 | 5.6, 5.7 | Any | Any | InnoDB：crash because of failure to rename file in DDL |
| 96236 | 2019-07-17 14:56 | 2023-07-25 5:44 | MySQL Server: InnoDB storage engine | Verified (1737 days) | S1 | 5.7.25, 8.0.16 | Any | Any | Big intrinsic tmp InnoDB table make InnoDB engine get totally stuck |
| 84025 | 2016-12-01 4:02 | 2023-02-10 9:35 | MySQL Server: InnoDB storage engine | Verified (2650 days) | S1 | 5.7.16, 5.7.17 | Any | Any | 5.7 Shutdown and startup take a long time after creating 100k tables |
| 83557 | 2016-10-27 3:08 | 2016-10-27 9:03 | MySQL Server: InnoDB storage engine | Verified (2731 days) | S1 | 5.7.16 | CentOS | Any | Can't use LOCK=NONE to drop columns in table with virtual columns |
| 103478 | 2021-04-26 8:40 | 2021-04-26 10:54 | MySQL Server: InnoDB storage engine | Verified (1089 days) | S1 | 5.7.26, 5.7.32, 5.7.33. 5.7.34 | Windows (10 Pro) | Any | Internal Temp Tables used under heavy load cause the system to hang |
| 82355 | 2016-07-27 8:45 | 2016-08-02 8:28 | MySQL Server: InnoDB storage engine | Verified (2817 days) | S1 | 5.7.13, 5.7.14 | CentOS (7) | Any | [FATAL] InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for redo log |
| 73829 | 2014-09-08 5:06 | 2015-02-26 6:13 | MySQL Server: Locking | Verified (3397 days) | S1 | 5.6, 5.6.21, 5.6.23, 5.7.6 | Any | Any | Multi-threaded mysqld lockup issue with ~50-55 second timeout |
| 72053 | 2014-03-17 7:09 | 2014-03-17 18:53 | MySQL Server: MyISAM storage engine | Verified (3686 days) | S1 | 5.5,5.6,5.7 | Any | Any | mysql client command coredump when disk space is full! |
| 69585 | 2013-06-26 11:23 | 2014-07-22 18:41 | MySQL Server: MyISAM storage engine | Verified (3559 days) | S1 | 5.5.30 x64, 5.5.39, 5.6.21, 5.7.5 | Any (MS Windows W2K8 64bit, Linux) | Any | low-priority-updates not working on replication slave |
| 67123 | 2012-10-07 13:02 | 2012-10-12 12:56 | MySQL Server: MyISAM storage engine | Verified (4207 days) | S1 | 5.5.27, 5.5.29, 5.1.67, 5.7.0 | Any (MS Windows 2008 64bit, Linux) | Any | error in mi_update.c:226 |
| 82308 | 2016-07-21 14:54 | 2023-07-31 15:25 | MySQL Server: MyISAM storage engine | Verified (2829 days) | S1 | 5.7 | Any | Any | use of DISTINCT with BIT and LONGTEXT leads to erroneous results |
| 71206 | 2013-12-22 17:13 | 2013-12-31 20:00 | MySQL Server: Optimizer | Verified (3770 days) | S1 | 5.5.32-0ubuntu0.12.04.1-log, 5.6.15, 5.1.72, 5.5.35, 5.7.3 | Linux (ubuntu 12.04) | Any | GROUP_CONCAT changes GROUP BY behavior |
| 104629 | 2021-08-16 3:08 | 2021-08-16 7:09 | MySQL Server: Optimizer | Verified (977 days) | S1 | 8.0.25,5.7.35, 8.0.26 | Any | Any | wrong result when outer join prune partition tables with is null predicate |
| 106651 | 2022-03-07 4:34 | 2022-03-11 14:21 | MySQL Server: Optimizer | Verified (774 days) | S1 | 5.7.*, 5.7.37, 8.0.28 | Any | Any | Query wrong result when the condition is "where id ('decimal_a', 'decimal_b')" |
| 110125 | 2023-02-19 8:48 | 2023-02-20 5:04 | MySQL Server: Optimizer | Verified (424 days) | S1 | 8.0.32, 5.7 | Ubuntu | Any | Unexpected query result fetched from an indexed column |
| 110587 | 2023-04-03 7:51 | 2023-04-03 9:37 | MySQL Server: Optimizer | Verified (382 days) | S1 | 8.0.27, 8.0.32, 5.7.41 | Any | Any | Bit with index range query may produce different results |
| 58604 | 2010-11-30 21:28 | 2018-09-09 20:45 | MySQL Server: Optimizer | Verified (4887 days) | S1 | 5.5.7, 5.5.9, 5.6.1 | Any | Any | crash in cleanup code of explain partitions after killing connection |
| 91362 | 2018-06-21 15:18 | 2019-02-13 14:05 | MySQL Server: Optimizer | Verified (2128 days) | S1 | 5.6.36 - 5.6.40 and 5.7.18 - 5.7.22, 5.6.40, 5.7.22 | Any | Any | Incorrect query results under certain conditions. |
| 90847 | 2018-05-12 16:57 | 2018-08-18 11:52 | MySQL Server: Optimizer | Verified (2167 days) | S1 | 5.7.22, 8.0.11 | Windows (W10 64bit) | x86 | Query returns wrong data if order by is present |
| 110984 | 2023-05-11 2:24 | 2023-05-11 6:59 | MySQL Server: Optimizer | Verified (344 days) | S1 | 8031, 5.7.42, 8.0.33 | Linux | x86 | Subqueries with 'limit 1' cause concat strings to report errors |
| 86973 | 2017-07-06 13:26 | 2017-07-07 7:19 | MySQL Server: Optimizer | Verified (2478 days) | S1 | 5.6, 5.5.56, 5.6.36, 5.7.18 | Any | Any | BIN() function error |
| 100504 | 2020-08-12 11:58 | 2020-08-18 2:50 | MySQL Server: Optimizer | Verified (1340 days) | S1 | 8.0.21, 5.7.31 | Linux (Arch Linux) | x86 (x86_64) | Count distinct is inconsistent when swapping two fields being counted. |
| 111097 | 2023-05-22 6:40 | 2024-04-10 9:51 | MySQL Server: Optimizer | Verified (333 days) | S1 | 8031, 5.7.42, 8.0.33, 8.0.36 | Linux | x86 | Query statement results with subqueries are unstable |
| 78238 | 2015-08-27 5:09 | 2016-11-24 12:11 | MySQL Server: Options | Verified (3149 days) | S1 | 5.6, 5.7.8 (RC2), 5.7.9 | Any | Any | --query-alloc-block-size issues with numerous different crash examples |
| 82237 | 2016-07-15 3:15 | 2016-07-15 5:54 | MySQL Server: Options | Verified (2835 days) | S1 | 5.7.13, 5.6.31 | Any | Any | OPTIMIZER_SWITCH cannot be modified once a different collation is selected |
| 99382 | 2020-04-28 7:34 | 2020-04-29 8:13 | MySQL Server: Parser | Verified (1451 days) | S1 | 5.7, 8.0 | Any | Any | Complex nested views take up a lot of memory |
| 83435 | 2016-10-19 0:40 | 2020-09-08 22:05 | MySQL Server: Partitions | Verified (2739 days) | S1 | 5.7.15/5.6 | Any | Any | ALTER TABLE is very slow when using PARTITIONED table |
| 88639 | 2017-11-24 7:05 | 2017-11-27 9:48 | MySQL Server: Partitions | Verified (2335 days) | S1 | 5.6.38/5.7/8.0 | Any | Any | ERROR 1030 (HY000): Got error -1 from storage engine on PARTITION CREATE TABLE |
| 97041 | 2019-09-26 16:20 | 2019-09-28 14:33 | MySQL Server: Partitions | Verified (1665 days) | S1 | 8.0+, 8.0.17, 5.7.27 | Any | Any | main&sub partition field order different from combined pk, query result lose row |
| 105014 | 2021-09-23 3:32 | 2021-09-23 15:33 | MySQL Server: Partitions | Verified (939 days) | S1 | 8.0.25, 8.0.26, 8.0.11, 5.7.35 | Any (rhel-7.4) | Any (x86-64) | query gets incorrect resultset from table with subpartitions |
| 82663 | 2016-08-20 5:12 | 2017-06-27 7:40 | MySQL Server: Performance Schema | Verified (2793 days) | S1 | 5.7.13, 5.7.14 | Any | Any | mysqld hangs when accessing Performance Schema tables |
| 87674 | 2017-09-06 4:39 | 2017-09-06 6:02 | MySQL Server: Security: Privileges | Verified (2417 days) | S1 | 5.7.17, 5.6.37, 5.7.19 | Any | Any | Table 'user' was not locked with LOCK TABLES on FLUSH PRIVILEGES |
| 83030 | 2016-09-17 7:34 | 2016-09-19 7:19 | MySQL Server: Row Based Replication ( RBR ) | Verified (2769 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using REPLACE INTO |
| 83090 | 2016-09-22 2:13 | 2016-09-22 7:26 | MySQL Server: Row Based Replication ( RBR ) | Verified (2766 days) | S1 | 5.7.13, 5.7.15 | Any | Any | AUTO_INCREMENT not updated when using INSERT ON DUPLICATE KEY UPDATE |
| 103943 | 2021-06-08 11:42 | 2022-08-15 3:26 | MySQL Server: Replication | Verified (969 days) | S1 | 5.7.33 | CentOS (7.6) | x86 (64) | Semi-Replication Rotate And Purge Relaylog Leads To Increased Response |
| 80581 | 2016-03-02 8:03 | 2016-03-04 9:48 | MySQL Server: Replication | Verified (2968 days) | S1 | 5.7.11 | Any | Any | rpl_semi_sync_[non_]group_commit_deadlock crash on ASan, debug |
| 103084 | 2021-03-24 7:43 | 2024-04-03 10:31 | MySQL Server: Replication | Verified (1122 days) | S1 | 5.7.18, 5.7.33, 8.0.23 | Linux | x86 | Add auto_increment primary key causes data inconsistent in replication |
| 102586 | 2021-02-12 16:35 | 2023-10-12 16:30 | MySQL Server: Replication | Verified (190 days) | S1 | 8.1.0, 8.0.34, 8.0.23, 5.7.33 | Any | Any | Foreign Key ON DELETE CASCADE breaks with RBR and multiple-table DELETE. |
| 99082 | 2020-03-26 11:26 | 2024-01-08 15:08 | MySQL Server: Replication | Verified (1484 days) | S1 | 5.7.27, 5.7.29 | Any | Any | Problem with replication: XA transaction, temp tables and row based binlog |
| 98743 | 2020-02-26 1:02 | 2023-03-02 19:31 | MySQL Server: Replication | Verified (1514 days) | S1 | 5.7,8.0, 5.7.29, 8.0.19 | Any | Any | Invalid entry on mysql.gtid_executed table is unrecoverable |
| 83900 | 2016-11-21 8:04 | 2019-10-20 10:08 | MySQL Server: Replication | Verified (2457 days) | S1 | 5.7.12-log | CentOS (6.5) | Any | mysql server is crashed by binlog dump thread |
| 85064 | 2017-02-20 2:39 | 2017-02-20 8:42 | MySQL Server: Replication | Verified (2615 days) | S1 | 5.7.17 | Any | Any | end_anonymous_gtid_violating_transaction(): Assertion `old_value >= 1' failed. |
| 93779 | 2019-01-02 9:18 | 2019-01-30 14:53 | MySQL Server: Replication | Verified (1906 days) | S1 | 5.7.24 | Windows | Any | dml in table with trigger to other Table map in binlog lead to slave sql stopped |
| 85220 | 2017-02-28 8:34 | 2017-05-04 4:17 | MySQL Server: Replication | Verified (2542 days) | S1 | 5.7.17 | Any | Any | Assertion `(*thd)->get_transaction()->xid_state()-> has_state(XID_STATE::XA_... |
| 85695 | 2017-03-30 5:34 | 2019-11-07 17:39 | MySQL Server: Replication | Verified (2575 days) | S1 | 5.7, 5.7.17 | Any | Any | An incident event has been written to the binary log which will stop the slaves |
| 78495 | 2015-09-21 5:17 | 2016-11-21 12:48 | MySQL Server: Replication | Verified (2706 days) | S1 | 5.7.8 (RC2), 5.7.10, 8.0.0 | Any | Any | Table 'mysql.gtid_executed' cannot be opened. |
| 78195 | 2015-08-25 0:39 | 2015-08-25 8:43 | MySQL Server: Replication | Verified (3160 days) | S1 | 5.6.26, 5.7.8 | Any | Any | Bug #77684 leads to practically unrecoverable slave |
| 86797 | 2017-06-22 16:16 | 2017-07-27 17:06 | Shell AdminAPI InnoDB Cluster / ReplicaSet | Verified (2458 days) | S1 | 5.7.18 | Linux | Any | InnoDB Cluster does not report when nodes fall behind or stop writing data. |
| 73381 | 2014-07-24 22:31 | 2023-04-04 16:30 | MySQL Server: Stored Routines | Verified (381 days) | S1 | 5.6.19, 5.6.21, 5.7.5, 8.0 | Windows | Any | Can't find temp table created in stored proc. using CREATE TEMPORARY TABLE AS |
| 73399 | 2014-07-25 18:32 | 2014-07-25 18:56 | MySQL Server: Stored Routines | Verified (3556 days) | S1 | 5.6.14, 5.0.97, 5.1.74, 5.5.39, 5.6.21, 5.7.5 | Any | Any | BEFORE INSERT TRIGGER not fired |
| 88534 | 2017-11-17 11:04 | 2021-03-23 8:17 | MySQL Server: XA transactions | Verified (1123 days) | S1 | 5.7, 5.7.20 | Any | Any | XA may lost prepared transaction and cause different between master and slave. |
| Showing all 100 (Edit, Save, CSV, Feed) |
