Showing 1-30 of 77 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
114468 | 2024-03-24 21:51 | 2024-03-28 11:38 | MySQL Server: InnoDB storage engine | Verified (3 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 (73 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
113482 | 2023-12-21 9:23 | 2024-01-17 14:25 | MySQL Server: InnoDB storage engine | Verified (90 days) | S3 | 8.0.35, 8.2.0 | Any | Any | innodb_parallel_read_threads>1 makes simple select count more expensive |
113440 | 2023-12-15 13:06 | 2024-01-03 6:17 | MySQL Server: InnoDB storage engine | Verified (102 days) | S2 | 8.0.35 | Any | Any | Table spaces with instant_col information can no longer be imported |
112780 | 2023-10-20 10:05 | 2023-10-23 8:57 | MySQL Server: Documentation | Verified (157 days) | S3 | 8.0.34, 8.1.0 | Any | Any | innodb_temp_data_file_path changed from relative to absolute path in 8.0 |
112717 | 2023-10-13 15:14 | 2023-10-25 8:12 | MySQL Server: Replication | Verified (155 days) | S3 | 8.0.34 | Any | Any | Undo log truncation does not finalize when super_read_only=1 |
112714 | 2023-10-13 12:45 | 2023-10-16 14:02 | MySQL Server: Clone Plugin | Can't repeat (167 days) | S3 | 8.0.34 | Any | Any | Assertion failure: clone0api.cc:1159:ib::fatal in cloning when undo_x_trunc.log |
112705 | 2023-10-12 12:39 | 2023-10-12 12:53 | MySQL Server: SYS Schema | Verified (168 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 (170 days) | S3 | 8.0.34 | Any | Any | Documentation outdated related ANALYZE TABLE locking |
112252 | 2023-09-04 16:20 | 2023-11-07 11:29 | MySQL Server: InnoDB storage engine | Analyzing (150 days) | S3 | 8.0.33, 8.0.34 | Any | Any | InnoDB page compression impacts checkpointing |
110117 | 2023-02-17 13:22 | 2023-02-17 15:32 | MySQL Server: Documentation | Verified (405 days) | S3 | 8.0 | Any | Any | Lack of instrumentation for index condition impact on the query plan |
110111 | 2023-02-17 12:53 | 2023-02-20 12:35 | MySQL Server: Optimizer | Verified (402 days) | S5 | 8.0.31 | Any | Any | Optimizer chooses worst plan when index condition pushdown opportunity |
109701 | 2023-01-19 11:11 | 2023-02-21 22:39 | MySQL Server: mysqldump Command-line Client | Duplicate (401 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 introduces regression when --set-gtid-purged=OFF |
109700 | 2023-01-19 10:52 | 2023-05-31 3:36 | MySQL Server: Documentation | Closed (302 days) | S3 | 8.0.32 | Any | Any | Fix for #33630199 in 8.0.32 not reflected in the documentation and release notes |
109107 | 2022-11-16 8:19 | 2022-11-22 14:06 | MySQL Server: DML | Verified (498 days) | S5 | 8.0.31 | Any | Any | Non optimal query plan chosen for DELETE |
108825 | 2022-10-19 10:26 | 2022-11-21 10:17 | MySQL Server: Group Replication | Verified (526 days) | S4 | 8.0.31 | Any | Any | Timestamps needed in the GCS_DEBUG_TRACE file |
108824 | 2022-10-19 10:21 | 2022-10-19 10:52 | MySQL Server: Group Replication | Verified (526 days) | S3 | 8.0.31 | Any | Any | GCS_DEBUG_TRACE log not possible to rotate/archive without downtime |
108821 | 2022-10-19 10:01 | 2022-11-16 13:46 | MySQL Server: Documentation | Closed (498 days) | S3 | 8.0.31 | Any | Any | DOC issue with group_replication_communication_debug_options description |
108532 | 2022-09-19 9:32 | 2022-09-19 9:42 | MySQL Server: Documentation | Verified (556 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 (677 days) | S2 | 5.7.37, 8.0.28 | Any | Any | CURRENT_TIMESTAMP not safe after all? |
106323 | 2022-01-28 9:48 | 2022-10-18 0:48 | MySQL Server | Closed (527 days) | S3 | 8.0, 5.7 | Any | Any | relay_log_space_limit VALID_RANGE improperly defined |
106012 | 2021-12-30 18:26 | 2022-04-06 11:48 | MySQL Server: InnoDB storage engine | Verified (723 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 (826 days) | S4 | 8.0 | Any | Any | Add zstd as supported algorithm for InnoDB Page Compression |
104718 | 2021-08-25 9:59 | 2021-09-28 1:00 | MySQL Server: Documentation | No Feedback (913 days) | S3 | 8.0.25 | Any | Any | Documentation inaccurate about UPDATE_TIME in I_S.tables |
104099 | 2021-06-24 8:53 | 2021-08-26 23:04 | MySQL Server: Documentation | Closed (945 days) | S3 | 5.6, 5.7 | Any | Any | Replication and max_allowed_packet documentation incomplete for 5.6 and 5.7 |
103157 | 2021-03-30 22:01 | 2021-03-31 6:32 | MySQL Server: Replication | Verified (1093 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 (1154 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 (1156 days) | S2 | 5.7.32, 8.0.23 | Any | Any | CREATE TABLE ... LIKE inconsistent behavior in regards to DATA DIRECTORY |
101142 | 2020-10-12 22:49 | 2020-10-13 12:50 | MySQL Server: Logging | Not a Bug (1262 days) | S3 | 5.7.31, 8.0.20 | Any | Any | Queries long due to Lock_time not logged in the slow log |
98324 | 2020-01-22 9:57 | 2022-03-07 6:04 | MySQL Server: InnoDB storage engine | Verified (1457 days) | S2 | 5.7.26, 5.7.29, 8.0.20 | Any | Any | Deadlocks more frequent since version 5.7.26 |
Showing 1-30 of 77 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |