| Showing 1-30 of 326 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120582 | 2026-05-31 10:11 | 2026-05-31 10:11 | MySQL Server: Optimizer | Open | S3 | 8.0.44 | MacOS | Any | unique index causes incorrect result when comparing DOUBLE and BIGINT |
| 120581 | 2026-05-31 9:02 | 2026-05-31 9:02 | MySQL Server: Optimizer | Open | S2 | 8.0.44 | MacOS | Any | unique index causes incorrect result for IN comparison with implicit type conversion |
| 120580 | 2026-05-31 7:52 | 2026-05-31 7:53 | MySQL Server: Optimizer | Open | S3 | 8.0.44 | Any | Any | MyISAM prefix index causes incorrect range query result |
| 120579 | 2026-05-30 11:39 | 2026-05-30 11:39 | MySQL Server: Optimizer | Open | S3 | 8.0.45 | Any | Any | LIKE query returns inconsistent results with MyISAM prefix index |
| 120578 | 2026-05-30 9:05 | 2026-05-30 9:05 | MySQL Server: Optimizer | Open | S3 | 8.0.45 | Any | Any | Multiple-Column Index Creation Changes Query Results |
| 120577 | 2026-05-30 7:58 | 2026-05-30 7:58 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different results |
| 120576 | 2026-05-30 7:15 | 2026-05-30 7:15 | MySQL Server: MyISAM storage engine | Open | S3 | 8.0.45 | Any | Any | drop index can lead to different results |
| 120575 | 2026-05-30 6:57 | 2026-05-30 6:57 | MySQL Server: Optimizer | Open | S2 | 8.0.41+ | Any | Any | Range optimizer chooses bad range plan for large IN lists and execution is very slow and memory usage spikes. |
| 120574 | 2026-05-29 14:05 | 2026-05-29 14:12 | MySQL Server: Optimizer | Open | S2 | 8.0.41 | Any | Any | Range optimizer exceeds memory limit and chooses bad range plan for large IN lists |
| 120570 | 2026-05-29 7:28 | 2026-05-29 7:28 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_PREPARE triggers List<Item_param>::end(): `(*last)->next == &end_of_list` |
| 120569 | 2026-05-29 7:25 | 2026-05-29 7:25 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_EXECUTE triggers Materialized_cursor::~Materialized_cursor(): `!is_open()` |
| 120568 | 2026-05-29 7:22 | 2026-05-29 7:22 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_EXECUTE triggers Prepared_statement::check_parameter_types(): `false` |
| 120567 | 2026-05-29 7:18 | 2026-05-29 7:19 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_EXECUTE triggers set_parameter_value(): `len == 0 || len == 4 || len == 7 || len == 11 || len == 13` |
| 120566 | 2026-05-29 7:12 | 2026-05-29 7:13 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_PREPARE triggers send_statement(): `CountVisibleFields(param_list) == stmt->m_param_count` |
| 120565 | 2026-05-29 7:05 | 2026-05-29 7:10 | MySQL Server: Prepared statements | Open | S6 | 9.6.0-debug-asan | Ubuntu (22.04) | x86 (x86_64) | Raw COM_STMT_EXECUTE triggers Diagnostics_area::assert_not_set(): `!invalid_da_status__check_error_log` |
| 120564 | 2026-05-29 6:43 | 2026-05-29 6:46 | MySQL Server: InnoDB storage engine | Open | S3 | 9.7.0 | Any | Any | InnoDB FTS: Off-by-one error in fts_init_index() causes unsynced document to be lost after crash recovery |
| 120562 | 2026-05-28 12:53 | 2026-05-28 12:53 | MySQL Server: InnoDB storage engine | Open | S1 | 9.6.0 | Linux | Any | InnoDB crashes with assertion failure when UPDATE touches a table with many secondary indexes |
| 120561 | 2026-05-28 11:11 | 2026-05-29 4:41 | MySQL Server: DDL | Open (3 days) | S3 | 9.7/8.4/8.0 | Any | Any | tablespace marked missing after rollback of copy-style ALTER |
| 120558 | 2026-05-27 11:21 | 2026-05-27 11:41 | MySQL Server: InnoDB storage engine | Open (4 days) | S3 | 8.4.8 | Any | Any | Redo log archiving started by dead connection cannot be disabled later |
| 120555 | 2026-05-27 8:22 | 2026-05-27 11:39 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.45 | Ubuntu | Any | Equivalent VIEW and CTE queries return different row counts with EXISTS, BINARY ENUM comparison, and LEFT JOIN |
| 120552 | 2026-05-26 11:14 | 2026-05-26 11:16 | MySQL Server: Options | Open | S4 | 8.4, 9.7 | Any | Any | Add force_ddl_execution: give DDL priority under MDL contention |
| 120549 | 2026-05-26 5:29 | 2026-05-26 5:29 | MySQL Server: Replication | Open | S4 | Any | Any | (Contribution) optimizing of binlogging of large transactions | |
| 120544 | 2026-05-25 10:47 | 2026-05-27 12:38 | MySQL Server: Optimizer | Duplicate (4 days) | S3 | 8.4.8 | Any | Any | MySQL `MERGE` vs `TEMPTABLE` view evaluation changes `CROSS JOIN ... ON EXISTS(...)` cardinality |
| 120543 | 2026-05-25 9:57 | 2026-05-27 5:37 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.4.8 | Any | Any | MySQL `MERGE` vs `TEMPTABLE` view evaluation changes `MAX(SET)` result |
| 120540 | 2026-05-25 1:44 | 2026-05-29 5:20 | MySQL Server: Optimizer | Patch pending (4 days) | S2 | 9.7.0 | Ubuntu | x86 | A negated `IS TRUE` guard can still match a DECIMAL row for which the guarded predicate is true |
| 120539 | 2026-05-24 15:26 | 2026-05-24 15:26 | MySQL Server: FULLTEXT search | Open | S2 | 9.6.0 | Linux | Any | Duplicate FULLTEXT index on a column returns wrong MATCH...AGAINST results when combined with a STORED generated column |
| 120538 | 2026-05-24 13:46 | 2026-05-27 13:53 | MySQL Server: Optimizer | Duplicate (4 days) | S2 | 9.7.0 | Ubuntu | x86 | A RIGHT JOIN predicate treats IFNULL(NULL, non-NULL DECIMAL ZEROFILL) as non-matching and drops obvious rows |
| 120535 | 2026-05-24 5:29 | 2026-05-26 12:42 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.45 | Any | Any | Incorrect Query Result: IN and NOT IN return the same row simultaneously (boolean logic violation) |
| 120534 | 2026-05-24 5:19 | 2026-05-26 12:26 | MySQL Server: Optimizer | Verified (5 days) | S3 | 8.0.45 | Any | Any | Wrong Query Result Due to Incorrect Evaluation of GREATEST() with Mixed Types in OR (||) Boolean Context |
| 120533 | 2026-05-23 12:35 | 2026-05-26 8:30 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.45 | Ubuntu | x86 | A LEFT JOIN over DECIMAL ZEROFILL UNIQUE wrongly loses an obvious match |
| Showing 1-30 of 326 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
