Showing 1-90 of 726 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
118121 | 2025-05-06 14:40 | 2025-05-06 15:07 | MySQL Server: InnoDB storage engine | Analyzing (2 days) | S3 | 8.0.37 | Any | Any | lob pages leak when mysqld crashed |
118074 | 2025-04-28 17:23 | 2025-05-07 10:58 | MySQL Server: InnoDB storage engine | Need Feedback (1 day) | S1 | 8.0.40 | Any | x86 | Frequent MySQL Failovers After Upgrade to 8.0.40 |
118054 | 2025-04-24 16:23 | 2025-05-07 15:55 | MySQL Server: InnoDB storage engine | Verified (2 days) | S5 | Any | Any | Potential optimization in row_ins_sec_index_entry_low(): avoid second btr_cur_search_to_nth_level() under certain condit | |
117962 | 2025-04-13 15:19 | 2025-04-13 17:26 | MySQL Server: InnoDB storage engine | Verified (25 days) | S3 | 8.0.37, 8.0.41, 9.2.0 | Any | Any | ibd2sdi failed when table COMPRESSION='lz4' |
117943 | 2025-04-11 8:07 | 2025-05-06 15:13 | MySQL Server: InnoDB storage engine | Verified (2 days) | S3 | 8.4.4, 9.2.0 | Any | Any | Startup ibd-file validation uses too much CPU threads |
117931 | 2025-04-10 9:57 | 2025-04-15 12:40 | MySQL Server: InnoDB storage engine | Need Feedback (23 days) | S3 | 8.0.22 | Any | Any | virtual column index record wrong data |
117917 | 2025-04-08 16:01 | 2025-04-09 15:19 | MySQL Server: InnoDB storage engine | Need Feedback (29 days) | S1 | 8.0.32、5.7.44 | Linux | x86 | InnoDB: Failing assertion: lock->lock_word == X_LOCK_DECR |
117898 | 2025-04-07 8:26 | 2025-05-08 10:10 | MySQL Server: InnoDB storage engine | Verified (7 days) | S3 | 8.0.41 | Any | Any | User Records may be skipped when Persistent Cursor restores Infimum and Supremum Record |
117835 | 2025-03-31 10:44 | 2025-04-01 4:44 | MySQL Server: InnoDB storage engine | Analyzing (37 days) | S1 | 9.2.0 | Any (Ubuntu 22.04) | Any | Non Repeatable Read WITH CONSISTENT SNAPSHOT |
117733 | 2025-03-18 2:59 | 2025-03-21 1:13 | MySQL Server: InnoDB storage engine | Verified (51 days) | S2 | 9.2.0 | Any (Ubuntu 22.04) | Any | Dirty reads due to isolation level settings |
117717 | 2025-03-16 5:05 | 2025-03-16 11:41 | MySQL Server: InnoDB storage engine | Verified (53 days) | S2 | 8.0.41, 8.4.4, 9.2.0 | Any | Any | Import Tablespace Fails Due to Inconsistent max_prefix in dict_col_t After Dropping Index |
117691 | 2025-03-12 19:12 | 2025-03-28 9:54 | MySQL Server: InnoDB storage engine | Verified (43 days) | S2 | 8.4.0, 8.4.4, 9.2.0 | Linux | Any | MySQL 8.4 and 9 are not taking advantage of the Linux Page Cache (contrarily to 8.0). |
117659 | 2025-03-10 19:24 | 2025-03-11 11:23 | MySQL Server: InnoDB storage engine | Verified (58 days) | S3 | 8.4.4, 9.2.0 | Any | Any | OpenTelemetry symbols pollute MySQL Community Edition binaries. |
117553 | 2025-02-24 9:15 | 2025-03-11 8:25 | MySQL Server: InnoDB storage engine | Verified (58 days) | S2 | 8.4.4 | Any | Any | Crash caused by race condition between MVCC::view_open and purge view |
117533 | 2025-02-20 13:37 | 2025-03-27 9:50 | MySQL Server: InnoDB storage engine | Verified (42 days) | S5 | 8.0.41 | Any | Any | The performance is poor when concurrently reading undo records |
117498 | 2025-02-18 9:37 | 2025-03-27 13:44 | MySQL Server: InnoDB storage engine | Verified (42 days) | S5 | 8.0.41 | Any | Any | Traversing a relatively long undo-chain will seriously affect write performance |
117448 | 2025-02-12 9:22 | 2025-02-12 16:15 | MySQL Server: InnoDB storage engine | Verified (85 days) | S5 | 8.0 | Any | Any | When a large number of undo logs accumulate, reading the undo logs during the undo purge process may become a bottleneck |
117436 | 2025-02-11 7:22 | 2025-04-29 10:27 | MySQL Server: InnoDB storage engine | Verified (22 days) | S2 | 8.0 | Any | Any | PCursor::move_to_next_block may skip records incorrectly |
117314 | 2025-01-28 14:41 | 2025-01-28 15:25 | MySQL Server: InnoDB storage engine | Verified (100 days) | S3 | 9.2.0 | MacOS (15.3) | ARM | Test innodb.tablespace_encrypt_9 failing |
117256 | 2025-01-21 13:19 | 2025-01-28 18:24 | MySQL Server: InnoDB storage engine | Verified (100 days) | S2 | 8.4.4 | Any | Any | Repeating uncaused error "Column cannot be null" after single error on table with trigger |
117237 | 2025-01-19 4:13 | 2025-01-21 11:41 | MySQL Server: InnoDB storage engine | Verified (107 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Unexpected Duplicate Error in DDL Row Log Apply |
117231 | 2025-01-17 20:50 | 2025-01-27 6:57 | MySQL Server: InnoDB storage engine | Verified (101 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | Wrong SDI after upgrade from 8.0.23 because Bug#98501 (Exchanging partition does not update SDI). |
117189 | 2025-01-13 8:26 | 2025-01-13 8:40 | MySQL Server: InnoDB storage engine | Verified (115 days) | S3 | 8.0.39, 8.0.40 | Any | Any | InnoDB index stats many orders of magnitude wrong |
117099 | 2025-01-02 18:20 | 2025-01-08 15:18 | MySQL Server: InnoDB storage engine | Verified (120 days) | S2 | 8.0.40 | Any | Any | Variable innodb_ddl_buffer_size does not limit memory usage in the first phase of an ALTER TABLE |
116934 | 2024-12-11 2:04 | 2024-12-11 5:33 | MySQL Server: InnoDB storage engine | Verified (148 days) | S3 | 8.0,8.4 | Any | Any | Recovery should abort immediatly if meet corrupt log |
116933 | 2024-12-11 1:47 | 2024-12-11 5:33 | MySQL Server: InnoDB storage engine | Verified (148 days) | S3 | 8.0,8.4 | Any | Any | Function recv_single_rec doesn't handle corrupt_log correctly |
116878 | 2024-12-04 17:10 | 2025-02-21 12:40 | MySQL Server: InnoDB storage engine | Verified (90 days) | S5 | 8.0.21 and above | Any | Any | False sharing with hardcoded cache line size |
116815 | 2024-11-28 3:51 | 2024-12-04 17:38 | MySQL Server: InnoDB storage engine | Analyzing (155 days) | S2 | 8.0.30 | Any | Any | INSERT locks primary key supremum after secondary index duplicate key collision |
116813 | 2024-11-28 2:57 | 2024-12-02 13:26 | MySQL Server: InnoDB storage engine | Analyzing (157 days) | S5 | 8.0.40 | Any | Any | The transaction commit takes a long time even if it doesn't affect any rows |
116794 | 2024-11-27 4:10 | 2024-11-28 14:27 | MySQL Server: InnoDB storage engine | Verified (161 days) | S3 | 8.0 | Any | Any | Blobs in dropped columns will be residual after a update. |
116793 | 2024-11-27 3:51 | 2024-11-27 7:14 | MySQL Server: InnoDB storage engine | Verified (162 days) | S2 | 8.0.40 | Any | Any | AHI crash : ut_a(old_index != nullptr) |
116778 | 2024-11-26 4:28 | 2024-11-26 7:03 | MySQL Server: InnoDB storage engine | Verified (163 days) | S2 | 8.0.40, 8.4.3, 9.1.0 | Any | Any | mysql crash when optimize table and update |
116761 | 2024-11-24 4:46 | 2024-11-26 7:51 | MySQL Server: InnoDB storage engine | Verified (163 days) | S3 | 8.0.40 | Any | Any | Page tracking stops working when disk is full |
116760 | 2024-11-23 13:44 | 2024-11-25 7:24 | MySQL Server: InnoDB storage engine | Verified (164 days) | S3 | 8.0.40,8.4.3,9.1.0 | Any | Any | Page deadlock occured when searching BTREE after nullable cols dropped by INSTAN |
116715 | 2024-11-19 17:03 | 2024-11-20 17:23 | MySQL Server: InnoDB storage engine | Verified (169 days) | S2 | 9, 8.4, 8.0 | Any | Any | Optimize Normal Startup with Many Tables. |
116714 | 2024-11-19 16:04 | 2024-11-21 14:17 | MySQL Server: InnoDB storage engine | Verified (169 days) | S3 | 8.0 | Any | Any | With 8000 to 15,999 Tablespaces, MySQL Startup Spawns one Useless Sub-Thread. |
116713 | 2024-11-19 15:57 | 2024-11-21 14:15 | MySQL Server: InnoDB storage engine | Verified (169 days) | S2 | 9.0 | Any | Any | Function rename_partition_files should not be in MySQL 9, and more. |
116709 | 2024-11-19 11:59 | 2024-11-19 12:22 | MySQL Server: InnoDB storage engine | Verified (170 days) | S3 | 9.1.0 | Any | Any | scripts/mysql_system_tables.sql still treating InnoDB as an optional SE |
116647 | 2024-11-13 19:28 | 2025-04-25 16:55 | MySQL Server: InnoDB storage engine | Verified (175 days) | S3 | 8.4.2,9.0 | Any | Any | Bufferpool Index Stats are not decremented on btr_page_free |
116627 | 2024-11-12 10:30 | 2024-11-12 18:57 | MySQL Server: InnoDB storage engine | Verified (177 days) | S3 | 8.0 | Any | Any | innodb print tons of partial read in error log |
116626 | 2024-11-12 9:55 | 2024-11-12 10:02 | MySQL Server: InnoDB storage engine | Verified (177 days) | S3 | 8.0.40 | Any | Any | Lack of error handling when temp tablespace truncate fails |
116574 | 2024-11-07 3:20 | 2024-11-07 15:18 | MySQL Server: InnoDB storage engine | Verified (182 days) | S3 | 8.0 | Any | Any | btr_page_reorganize_low may cause crash recovery failure |
116531 | 2024-11-01 17:02 | 2025-04-25 14:39 | MySQL Server: InnoDB storage engine | Need Feedback (13 days) | S5 | 8.0 | Linux | x86 | Performance regressions from the diff that adds instant add and drop column |
116504 | 2024-10-30 12:52 | 2024-11-07 15:25 | MySQL Server: InnoDB storage engine | Verified (182 days) | S3 | 8.0 | Linux | Any | Insert into punch hole compression table drop of zero randomly |
116502 | 2024-10-30 4:31 | 2025-01-20 6:58 | MySQL Server: InnoDB storage engine | Verified (189 days) | S2 | 8.0.40 | Any | Any | Duplicate Detection Flaw for NULL Values in UK During DDL Rollback Operations |
116501 | 2024-10-29 13:27 | 2024-11-07 15:22 | MySQL Server: InnoDB storage engine | Verified (182 days) | S3 | 8.0 | Linux | Any | Compression not work with file system which sector size is not 512 |
116489 | 2024-10-28 10:59 | 2024-10-28 12:20 | MySQL Server: InnoDB storage engine | Verified (192 days) | S3 | 8.0.30 | Any | Any | no need to check log_upgrade when recv_apply_hashed_log_recs |
116455 | 2024-10-23 3:31 | 2024-11-14 8:19 | MySQL Server: InnoDB storage engine | Verified (175 days) | S3 | 8.0.40 | Any | Any | Server upgrade progress will open all tablespaces and not close |
116445 | 2024-10-22 11:01 | 2024-10-23 5:20 | MySQL Server: InnoDB storage engine | Verified (197 days) | S3 | 8.4,8.1,8.0 | Any | Any | recv_sys->scanned_epoch_no lost assignment when parse_start_lsn is first set |
116383 | 2024-10-16 20:57 | 2024-11-19 20:18 | MySQL Server: InnoDB storage engine | Verified (203 days) | S3 | 8.4 | Any | Any | Contribution: Fix for resetting innodb_redo_log_capacity and innodb_buffer_ ... |
116374 | 2024-10-16 12:35 | 2024-11-12 8:47 | MySQL Server: InnoDB Plugin storage engine | Verified (177 days) | S3 | 8.0.40 | Any | Any | Undo tablespace was created unexpectedly |
116319 | 2024-10-09 6:50 | 2024-10-10 3:58 | MySQL Server: InnoDB storage engine | Verified (211 days) | S2 | 8.0, 8.4, 8.0.39 | Any | Any | When locks exhaust the BP, an incorret assert about semi_consistent causes crash |
116305 | 2024-10-06 11:05 | 2024-10-09 13:54 | MySQL Server: InnoDB storage engine | Verified (211 days) | S2 | 9.0 | Any | Any | row_search_mvcc process wrong page of small buffer pool |
116291 | 2024-10-03 12:11 | 2024-11-12 13:46 | MySQL Server: InnoDB storage engine | Verified (216 days) | S5 | 8.0 | Any | Any | innodb crash recovery optimize for MLOG_REC_INSERT |
116209 | 2024-09-24 7:44 | 2024-09-27 8:59 | MySQL Server: InnoDB storage engine | Verified (226 days) | S5 | 8.0 | Any | Any | Crash recovery is slow because of repeated scans of double-wrtie |
116198 | 2024-09-23 10:51 | 2025-04-03 13:56 | MySQL Server: InnoDB storage engine | Verified (222 days) | S5 | 8.0 | Any | Any | Addressing the compatibility issues of the CATS algorithm in NUMA scenarios. |
116142 | 2024-09-18 11:34 | 2025-01-21 11:13 | MySQL Server: InnoDB storage engine | Verified (231 days) | S2 | 8.0 | Any | Any | Add another uk to a field that already has a uk results in a duplicate key error |
116118 | 2024-09-16 8:51 | 2024-09-16 13:19 | MySQL Server: InnoDB storage engine | Verified (234 days) | S3 | 8.0.39 | Any | Any | Need to bound optimise-like statement in order to reclaim the disk space back |
116067 | 2024-09-11 21:51 | 2024-09-23 14:27 | MySQL Server: InnoDB storage engine | Verified (237 days) | S3 | 8.0.28 | Any | Any | Upsert not visible within own transaction when querying by unique index |
116035 | 2024-09-09 1:55 | 2024-09-12 1:25 | MySQL Server: InnoDB storage engine | Verified (239 days) | S3 | Any | Any | with parallel instant ddl and select INFORMATION_SCHEMA will show Duplicate row | |
116005 | 2024-09-04 23:43 | 2025-02-09 14:10 | MySQL Server: InnoDB storage engine | Verified (88 days) | S5 | all versions | Any | Any | With NUMA and Read Committed, performance worsens under high concurrency. |
115994 | 2024-09-04 6:19 | 2024-11-25 14:16 | MySQL Server: InnoDB storage engine | Verified (246 days) | S2 | 5.7.41, 8.0 | Any | Any | InnoDB: system hang because of buf flush wait flushed keeps waiting for ever |
115988 | 2024-09-03 15:03 | 2024-09-12 2:11 | MySQL Server: InnoDB storage engine | Verified (246 days) | S5 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Too Much Disk Read on Startup, penalizing deployments with many tables (1M+). |
115951 | 2024-08-28 12:17 | 2024-09-14 11:36 | MySQL Server: InnoDB storage engine | Verified (253 days) | S2 | 8.0.32, 8.0.39, 8.4.2 | Linux | Any | ALTER TABLE ... IMPORT TABLESPACE may cause unsafe reads |
115942 | 2024-08-28 6:32 | 2024-10-30 1:23 | MySQL Server: InnoDB storage engine | Verified (190 days) | S3 | 8.0.37 | Linux | x86 | The delete operation performed in an uncommitted transaction affects the query r |
115931 | 2024-08-26 12:32 | 2024-08-26 14:32 | MySQL Server: InnoDB storage engine | Verified (255 days) | S3 | 8.0.39, 8.4.0 | Any | Any | MySQL hangs on installing plugin with innodb_thread_concurrency=1 |
115886 | 2024-08-21 19:15 | 2024-08-22 7:06 | MySQL Server: InnoDB storage engine | Verified (259 days) | S3 | 8.0.39, 8.4.2, 9.0.1 | Any | Any | Crash recovery logs after clean restart with log_error_verbosity = 3. |
115780 | 2024-08-06 7:25 | 2024-08-20 3:42 | MySQL Server: InnoDB storage engine | Verified (274 days) | S2 | 8,9, 8.0.39 | Any | Any | InnoDB aborts when a DB_OUT_OF_RESOURCES error occurs in Parallel_reader |
115668 | 2024-07-22 23:46 | 2024-07-23 5:04 | MySQL Server: InnoDB storage engine | Verified (289 days) | S3 | Any | Any | Contribution: innobase: respect transaction isolation for innodb_api | |
115527 | 2024-07-05 14:35 | 2024-12-04 9:52 | MySQL Server: InnoDB storage engine | Verified (155 days) | S3 | 8.0 | Any | Any | Contribution: Ensure FTS auxiliary tables are cleaned up properly |
115499 | 2024-07-03 11:30 | 2024-12-26 6:41 | MySQL Server: InnoDB storage engine | Verified (309 days) | S3 | 8.0.38, 8.0.40 | Any | Any | InnoDB: key buffer sort could be skipped when pk order preserved |
115480 | 2024-07-02 4:26 | 2025-01-24 13:52 | MySQL Server: InnoDB storage engine | Verified (104 days) | S3 | 8.0.41 | MacOS (14.5) | ARM | Test innodb.log_first_rec_group failing |
115348 | 2024-06-16 15:56 | 2025-01-09 11:24 | MySQL Server: InnoDB storage engine | Verified (119 days) | S3 | 8.0.40 | Any | Any | Expansion of the undo tablespace |
115328 | 2024-06-14 2:13 | 2024-07-06 14:02 | MySQL Server: InnoDB storage engine | Analyzing (324 days) | S5 | 8.4.0 | Red Hat (Rocky Linux 8.8) | x86 | Poor write performance due to new default value of innodb_doublewrite_pages |
115256 | 2024-06-08 0:10 | 2024-06-08 7:47 | MySQL Server: InnoDB storage engine | Verified (334 days) | S3 | 8.4, 8.0.37 | Any | Any | Import tablespace does not work properly for decimal data type |
115242 | 2024-06-06 8:43 | 2024-06-20 12:56 | MySQL Server: InnoDB storage engine | Verified (322 days) | S3 | 8.0.37, 8.4.0 | Any | Any | Unexpected dd_table_open_on_id_low() failure on concurrent RENAME TABLE |
115157 | 2024-05-29 7:34 | 2024-05-29 7:53 | MySQL Server: InnoDB storage engine | Verified (344 days) | S3 | mysql-trunk, 8.0 | Any | Any | Potential Nullptr Derefence in file `storage\innobase\lob\zlob0update.cc` |
115136 | 2024-05-27 9:01 | 2024-09-26 11:01 | MySQL Server: InnoDB storage engine | Verified (225 days) | S3 | 8.0 | Any | Any | Skip value when add an auto_increment column |
115124 | 2024-05-25 15:47 | 2024-05-29 10:26 | MySQL Server: InnoDB storage engine | Verified (346 days) | S3 | 8.0 | Any | Any | The sort file cache is not fully controlled by innodb_disable_sort_file_cache |
115107 | 2024-05-23 18:54 | 2024-10-17 10:42 | MySQL Server: InnoDB storage engine | Verified (203 days) | S5 | 5.7, 8.0 | Any | Any | Optimization in row_purge_poss_sec Function for Undo Purge Process |
114966 | 2024-05-11 8:49 | 2024-05-13 12:37 | MySQL Server: InnoDB storage engine | Verified (360 days) | S3 | 8.0 | Any | Any | innodb_parallel_read_threads can be set with neg vals |
114924 | 2024-05-08 14:01 | 2024-07-02 9:48 | MySQL Server: InnoDB storage engine | Verified (350 days) | S5 | 8.0.37 | Any | Any | Significant regression between 8.0.25 and 8.0.37 in a simple OLTP workload |
114903 | 2024-05-07 7:22 | 2024-11-25 9:52 | MySQL Server: InnoDB storage engine | Verified (199 days) | S5 | 8.4.0 | Any | Any | MySQL 8.4.0 is 10% slower for write workloads than MySQL 8.0.37 |
114838 | 2024-05-01 13:48 | 2024-08-19 12:10 | MySQL Server: InnoDB storage engine | Verified (262 days) | S1 | 8.4.0 | Ubuntu | Any | 8.4.0 requires unique constraint for FK |
114829 | 2024-04-30 21:15 | 2024-06-06 9:21 | MySQL Server: InnoDB storage engine | Verified (370 days) | S3 | 8.0 | Any | Any | Scoped_heap incorrect usage may have memory leak |
114821 | 2024-04-30 5:32 | 2024-05-02 20:19 | MySQL Server: InnoDB storage engine | Verified (373 days) | S3 | 8.0 | Any | Any | Server upgrade can fail due to badly configured session variables |
114799 | 2024-04-26 16:41 | 2025-01-22 1:52 | MySQL Server: InnoDB storage engine | Verified (374 days) | S3 | 8.0.33, 8.0.36 | Any | Any | ERROR 1216 vs ERROR 1452 in MySQL 8.0 |
114708 | 2024-04-19 19:34 | 2024-04-22 7:40 | MySQL Server: InnoDB storage engine | Verified (381 days) | S3 | 8.0 | Any | Any | Contribution: Fix build if UNIV_ZIP_DEBUG is enabled |
114641 | 2024-04-12 22:11 | 2024-04-14 13:05 | MySQL Server: InnoDB storage engine | Verified (389 days) | S3 | 8.0 | Any | Any | Contribution: fix stale comment in trx0undo.cc |
114468 | 2024-03-24 21:51 | 2024-04-10 8:34 | MySQL Server: InnoDB storage engine | Verified (409 days) | S5 | 8.3.0, 8.0.36 | Any | Any | Inconsistent table performance: fresh data import vs after optimization |
Showing 1-90 of 726 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |