Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
70202 | 2013-08-30 15:36 | 2013-09-02 11:53 | MySQL Server: DML | Verified (4167 days) | S3 | 5.5, 5.6 | Any | Any | REPLACE working differently for a table having PK or UK only versus both PK+UK |
71211 | 2013-12-23 9:21 | 2013-12-23 9:31 | MySQL Server: Archive storage engine | Verified (4055 days) | S2 | 5.1, 5.5, 5.6 | Any | Any | ARCHIVE engine does not guarantee UNIQUE and PRIMARY KEY constraints |
76566 | 2015-04-01 16:34 | 2015-04-02 7:30 | MySQL Server: InnoDB storage engine | Verified (3590 days) | S3 | 5.5 5.6, 5.5.44, 5.6.25 | Any | Any | Double transaction id for a DDL statements |
77318 | 2015-06-11 14:40 | 2015-06-12 12:42 | MySQL Server: InnoDB storage engine | Verified (3519 days) | S3 | 5.5.44, 5.5.45 | Any | Any | Selects waiting on MDL when altering partitioned table |
77826 | 2015-07-24 8:19 | 2015-10-13 6:41 | MySQL Server: Replication | Verified (3473 days) | S1 | 5.6.25, 5.6.26 | Any | Any | Transaction applied partially on a slave with relay_log_info_repository=table |
78896 | 2015-10-21 10:32 | 2015-10-21 12:59 | MySQL Server: Errors | Verified (3388 days) | S3 | 5.7.8, 5.6.27, 5.6.28 | Any | Any | Inconsistent error on using view with missing definer |
82599 | 2016-08-16 14:14 | 2022-06-02 20:27 | MySQL Server: Replication | Verified (3087 days) | S2 | 5.7.14,5.6, 5.6.32 | Any | Any | slave_type_conversions messing with data which still fits within allowed range |
88720 | 2017-11-30 14:52 | 2018-02-24 10:49 | MySQL Server: Replication | Verified (2616 days) | S3 | 5.6, 5.7, 8.0.3, 5.6.38, 5.7.20 | Any | Any | Inconsistent and unsafe FLUSH behavior in terms of replication |
89182 | 2018-01-11 9:51 | 2018-01-11 13:10 | MySQL Server: Optimizer | Verified (2575 days) | S3 | 5.6.38, 5.7.20, 8.0.3 | Any | Any | Optimizer unable to ignore index part entering less optimal query plan |
92558 | 2018-09-25 12:02 | 2018-09-26 5:47 | MySQL Server: Information schema | Verified (2317 days) | S3 | 5.7.23, 8.0.12 | Any | Any | information_schema.innodb_trx trx_is_read_only not set for all RO transactions |
94187 | 2019-02-04 9:14 | 2019-02-05 5:44 | MySQL Server: Command-line Clients | Verified (2186 days) | S3 | 5.7.21 | Any | Any | Downgrade minor 5.7 version leaves incorrect innodb_table_stats schema |
95547 | 2019-05-27 14:37 | 2019-05-31 11:57 | MySQL Server: Replication | Verified (2070 days) | S2 | 5.7.26 | Any | Any | MySQL restarts automatically after ABORT_SERVER due to disk full |
96001 | 2019-06-26 12:07 | 2019-09-02 12:14 | MySQL Server: MyISAM storage engine | Verified (2044 days) | S3 | 8.0.16, 5.7.26 | Any | Any | No warning when creating foreign key in MyISAM tables |
96400 | 2019-08-01 13:30 | 2022-06-15 21:07 | MySQL Server: Replication | Verified (2007 days) | S3 | 5.7.25, 5.7.27 | Any | Any | MTS STOP SLAVE takes over a minute when master crashed during event logging |
96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (1965 days) | S3 | 5.7.26, 5.7.27 | Any | Any | Set read_only on a master waiting for semi-sync ACK blocked on global read lock |
96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (1959 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
97913 | 2019-12-06 11:15 | 2019-12-23 5:55 | MySQL Server: InnoDB storage engine | Verified (1878 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1764 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1463 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1461 days) | S3 | 5.7.33, 8.0.23 | Any | Any | Table space path for partitioned table goes crazy after CREATE TABLE ... LIKE |
103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1400 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (1030 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (984 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (863 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (833 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (805 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (709 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (712 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (457 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (477 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
Showing 1-30 of 44 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |