« Show Previous 30 Entries | Showing 31-60 of 77 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
101142 | 2020-10-12 22:49 | 2020-10-13 12:50 | MySQL Server: Logging | Not a Bug (1283 days) | S3 | 5.7.31, 8.0.20 | Any | Any | Queries long due to Lock_time not logged in the slow log |
78406 | 2015-09-11 10:21 | 2019-12-20 14:13 | MySQL Server | Not a Bug (1581 days) | S3 | 5.6.25 | Any | Any | Simple insert deadlock when selected from partitioned table being updated |
84574 | 2017-01-20 0:39 | 2017-02-09 12:53 | MySQL Server: Group Replication | Not a Bug (2625 days) | S2 | 5.7.17 | Any | Any | In Group Replication, DDL execute on partitioned node leads to split brain |
76247 | 2015-03-10 17:33 | 2015-08-19 13:16 | MySQL Server: Optimizer | Not a Bug (3165 days) | S5 | 5.6 5.7 | Any | Any | Regression case with semijoin - query with many INs stuck on statistics state |
114468 | 2024-03-24 21:51 | 2024-04-10 8:34 | MySQL Server: InnoDB storage engine | Verified (24 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
113644 | 2024-01-15 14:13 | 2024-01-16 10:53 | MySQL Server: InnoDB storage engine | Verified (94 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
113440 | 2023-12-15 13:06 | 2024-01-03 6:17 | MySQL Server: InnoDB storage engine | Verified (123 days) | S2 | 8.0.35 | Any | Any | Table spaces with instant_col information can no longer be imported |
112717 | 2023-10-13 15:14 | 2023-10-25 8:12 | MySQL Server: Replication | Verified (176 days) | S3 | 8.0.34 | Any | Any | Undo log truncation does not finalize when super_read_only=1 |
112780 | 2023-10-20 10:05 | 2023-10-23 8:57 | MySQL Server: Documentation | Verified (178 days) | S3 | 8.0.34, 8.1.0 | Any | Any | innodb_temp_data_file_path changed from relative to absolute path in 8.0 |
112705 | 2023-10-12 12:39 | 2023-10-12 12:53 | MySQL Server: SYS Schema | Verified (189 days) | S3 | 8.0.34 | Any | Any | sys.schema_table_statistics reset values upon index addition or removal |
112670 | 2023-10-09 15:47 | 2023-10-10 5:04 | MySQL Server: Documentation | Verified (191 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (423 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 (426 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (519 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (547 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
108825 | 2022-10-19 10:26 | 2022-11-21 10:17 | MySQL Server: Group Replication | Verified (547 days) | S4 | 8.0.31 | Any | Any | Timestamps needed in the GCS_DEBUG_TRACE file |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (577 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
107293 | 2022-05-15 13:34 | 2022-05-21 20:52 | MySQL Server: Replication | Verified (698 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (744 days) | S3 | 8.0, 5.7 | Any | Any | Table stats in P_S not updated on rows updated via FK constraint |
105962 | 2021-12-22 20:35 | 2023-04-28 9:09 | MySQL Server: InnoDB storage engine | Verified (847 days) | S4 | 8.0 | Any | Any | Add zstd as supported algorithm for InnoDB Page Compression |
103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1114 days) | S3 | 8.0.23 | Any | Any | Inconsistent terminology change in error messages |
102417 | 2021-01-29 9:54 | 2021-01-29 10:22 | MySQL Server: DDL | Verified (1175 days) | S3 | 5.7.33, 8.0.23 | Any | Any | Table space path for partitioned table goes crazy after CREATE TABLE ... LIKE |
102395 | 2021-01-27 11:33 | 2021-01-27 12:18 | MySQL Server: DDL | Verified (1177 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1478 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
91697 | 2018-07-18 12:13 | 2020-03-04 14:13 | MySQL Server: InnoDB storage engine | Verified (1506 days) | S4 | 5.7+ | Any | Any | Improve dedicated log file for InnoDB monitor |
97913 | 2019-12-06 11:15 | 2019-12-23 5:55 | MySQL Server: InnoDB storage engine | Verified (1592 days) | S3 | 5.7.28 | Any | Any | Undo logs growing during partitioning ALTER queries |
96931 | 2019-09-18 13:55 | 2019-09-19 6:51 | MySQL Server: Optimizer | Verified (1673 days) | S4 | 5.7, 8.0 | Any | Any | Implement max_rows_examined limit as another optimizer hint |
96853 | 2019-09-12 15:10 | 2019-09-19 10:19 | MySQL Server: Replication | Verified (1673 days) | S3 | 5.7.27 | Any | Any | Inconsistent super_read_only status when changing the variable is blocked |
96644 | 2019-08-25 11:58 | 2019-09-13 10:03 | MySQL Server: Replication | Verified (1679 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 |
96690 | 2019-08-29 8:50 | 2020-02-12 13:01 | MySQL Server: Replication | Verified (1694 days) | S4 | 8.0 | Any | Any | sql_require_primary_key should not apply to temporary tables |
« Show Previous 30 Entries | Showing 31-60 of 77 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |