Showing 1-30 of 88 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
116944 | 2024-12-11 14:09 | 2024-12-11 14:24 | MySQL Server: Documentation | Verified (216 days) | S3 | 8.0, 8.4 | Any | Any | Documentation about online DDL missing collation changes |
116943 | 2024-12-11 13:50 | 2024-12-20 15:18 | MySQL Server: DDL | Verified (207 days) | S3 | 8.0.40 | Any | Any | Inconsistent metadata-only table and column collation changes behavior of ALTER TABLE |
116886 | 2024-12-05 20:06 | 2024-12-06 5:49 | Shell Dump & Load | Verified (221 days) | S4 | 8.0, 8.4 | Any | Any | Allow the Shell Dump/Import utils be gentle regarding load and replication lag |
115954 | 2024-08-28 15:17 | 2024-08-29 9:09 | MySQL Server: Logging | Verified (320 days) | S3 | 8.4.2, 8.0.x | Any | Any | Confusing warning "Cannot add field x in table y because after adding it ..." |
115798 | 2024-08-08 11:54 | 2024-09-18 9:51 | Shell Upgrade Checker | Closed (300 days) | S2 | 8.4.1 | Any | Any | util.checkForServerUpgrade() claims upgrade version 8.0.x to 8.4.x not supported |
115563 | 2024-07-11 7:54 | 2024-07-16 6:53 | MySQL Server: Group Replication | Verified (364 days) | S3 | 8.0.38 | Any | Any | Group replication conflict resolutions seem inconsistent |
115327 | 2024-06-13 22:01 | 2024-06-19 12:26 | MySQL Server: Optimizer | Verified (391 days) | S5 | 8.0.37, 8.4.0 | Any | Any | Higher memory requirements for range optimizer in v. 8.0 vs 5.7 |
115062 | 2024-05-20 11:02 | 2024-05-20 15:05 | MySQL Server: Documentation | Verified (421 days) | S3 | 8.0 | Any | Any | Guidelines for estimating range optimization memory usage inaccurate |
114924 | 2024-05-08 14:01 | 2025-06-16 5:39 | MySQL Server: InnoDB storage engine | Won't fix (29 days) | S5 | 8.0.37 | Any | Any | Significant regression between 8.0.25 and 8.0.37 in a simple OLTP workload |
114815 | 2024-04-29 12:15 | 2025-01-10 11:43 | Shell Upgrade Checker | Closed (216 days) | S3 | 8.0.36 | Any | Any | Prepared statement in stored procedure - error on util.checkForServerUpgrade |
114717 | 2024-04-20 18:57 | 2024-04-22 9:30 | MySQL Server: DDL | Verified (449 days) | S3 | 8.0.36 | Any | Any | Inconsistent behavior of explicit CHARSET/COLLATE column definition |
114468 | 2024-03-24 21:51 | 2025-05-27 12:59 | MySQL Server: InnoDB storage engine | Verified (477 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 (547 days) | S3 | 8.0 | Any | Any | Confusing thread id vs processlist id information in SEIS |
113482 | 2023-12-21 9:23 | 2024-06-24 20:52 | MySQL Server: InnoDB storage engine | Closed (386 days) | S5 | 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 (576 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 (631 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 (629 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 (641 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 (642 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 (644 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 (624 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 (879 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 (876 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 (875 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 (776 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 (972 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 (1000 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 (1000 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 (972 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 (1030 days) | S3 | 8.0.30 | Any | Any | Documentation missing redo log upgrade |
Showing 1-30 of 88 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |