| Showing 1-90 of 5977 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 120019 | 2026-03-10 12:29 | 2026-03-10 14:40 | MySQL Server: Optimizer | Verified | S2 | 8.0.41 | Any | Any | query result change after removing partitioning |
| 120016 | 2026-03-09 17:41 | 2026-03-10 7:58 | MySQL Server: Documentation | Verified | S2 | 8.0, 8.4, 9.x | Any | Any | Documentation "Exchanging Partitions and Subpartitions with Tables" not mentioning limitation about ALGORITHM=INSTANT. |
| 120015 | 2026-03-09 13:48 | 2026-03-09 14:14 | MySQL Server: Optimizer | Verified (1 day) | S1 | 8.0.45 | Any | Any | Incorrect retention of NULL rows due to CASE evaluation error in WHERE clause. |
| 120011 | 2026-03-09 10:29 | 2026-03-09 11:16 | MySQL Server: Optimizer | Verified (1 day) | S1 | 8.0.44 | Any | Any | The normal query generated a non-optimal query plan with index. |
| 120010 | 2026-03-09 9:56 | 2026-03-09 10:21 | MySQL Server: Optimizer | Verified (1 day) | S1 | 8.0.45 | Any | Any | Incorrect result set when evaluating IS NULL on a derived table containing logical AND expressions |
| 120005 | 2026-03-08 0:14 | 2026-03-10 8:04 | MySQL Server: Optimizer | Verified | S2 | 8.4.7 | Any | Any | Wrong results with subquery with semijoin=on and antijoin optimization |
| 120004 | 2026-03-07 19:38 | 2026-03-09 9:48 | MySQL Server: Optimizer | Verified (1 day) | S2 | 8.0.31 | Any | Any | IndexSkipScanIterator Assertion Failure |
| 120003 | 2026-03-07 12:14 | 2026-03-09 9:41 | MySQL Server: Optimizer | Verified (1 day) | S3 | 8.0.45 | Any | Any | column name unexpectedly change because of '1' as a column |
| 120000 | 2026-03-06 21:55 | 2026-03-08 13:19 | MySQL Server | Open (2 days) | S3 | 8.0.30-22 | Ubuntu (22) | Any | Mysql crash after increase 2% innodb buffer pool |
| 119997 | 2026-03-06 13:12 | 2026-03-07 11:27 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0.40 | Any | Any | Setting innodb_use_native_aio to OFF can lead to severe lock contention. |
| 119996 | 2026-03-06 11:07 | 2026-03-06 11:07 | MySQL Server: Replication | Open | S2 | 9.6 | Any | Any | Row delete from a table with selfreferental FK breaks replication |
| 119995 | 2026-03-06 9:51 | 2026-03-09 9:55 | MySQL Server: Optimizer | Verified (1 day) | S2 | 8.0.45 | Any | Any | Function find_in_set return wrong result |
| 119991 | 2026-03-06 5:56 | 2026-03-06 11:27 | MySQL Server: Optimizer | Verified (4 days) | S2 | 8.0.45 | Linux | x86 | Incorrect result with LEFT/RIGHT JOIN when comparing boolean expression with = 0 in presence of functional index |
| 119986 | 2026-03-05 11:29 | 2026-03-06 5:29 | MySQL Server: InnoDB storage engine | Open (4 days) | S3 | 8.4.7 | Any | Any | Value of sys var temptable_max_mmap not honored unless temptable_use_mmap is ON |
| 119980 | 2026-03-04 11:56 | 2026-03-04 11:56 | MySQL Server: FULLTEXT search | Open | S3 | 8.4.8 | Any | Any | Optimize full text only not working when trying to fix FTS index after tablespace import |
| 119978 | 2026-03-03 16:41 | 2026-03-06 3:48 | MySQL Server: InnoDB storage engine | Open | S3 | 8.0 | SUSE (SLES 15 SP6) | x86 | In-place upgrade of Mysql 5.7.x/8.0.19 to revision after 8.0.23 fails due to undo_00x tablespace ID |
| 119977 | 2026-03-03 13:44 | 2026-03-03 20:55 | MySQL Server: Optimizer | Verified (7 days) | S3 | 8.0.36 | Any (windows 11) | Any | NULL > ALL(subquery) produces NULL but IS NULL / IS UNKNOWN both return FALSE |
| 119974 | 2026-03-03 2:29 | 2026-03-06 6:10 | MySQL Server: InnoDB storage engine | Open (7 days) | S3 | 8.0, 8.4, 9.6 | Any | Any | inplace algorithm dropping multi full text indexes only drops FTS AUX tables of the last index, leading orphaned tables |
| 119973 | 2026-03-02 21:01 | 2026-03-03 8:45 | MySQL Server: Optimizer | Verified (7 days) | S1 | 8.0.45 | Any | Any | Inconsistent results depending on whether the column has a PRIMARY KEY index |
| 119972 | 2026-03-02 19:47 | 2026-03-03 9:47 | MySQL Server: Optimizer | Verified (7 days) | S1 | 8.0.45 | Any | Any | Incorrect Result from IN Subquery with UNIQUE Index |
| 119965 | 2026-03-02 11:56 | 2026-03-02 13:58 | MySQL Server: Partitions | Verified (8 days) | S3 | 8.0.35 | Any | Any | The results of the same query statement are inconsistent when it is executed multiple times. |
| 119963 | 2026-03-02 9:08 | 2026-03-02 13:43 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.45 | Any | Any | Inconsistent Results When Comparing Identical Aggregate Calculations Between Main Query and Correlated Subquery |
| 119959 | 2026-03-01 14:50 | 2026-03-02 13:16 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.45 | Linux (ubuntu 20.04) | x86 | Inconsistent results between direct query and derived table query involving NULLIF and IS NOT UNKNOWN |
| 119958 | 2026-02-28 13:09 | 2026-03-02 13:02 | MySQL Server: Optimizer | Verified (8 days) | S1 | 8.0.45 | Any | Any | EXISTS subquery result behaves inconsistently based on source table |
| 119957 | 2026-02-28 7:28 | 2026-02-28 7:28 | MySQL Server: Replication | Open | S2 | 8.0 | Any | Any | Contribution by Tencent: Replica Crash Due to Stale fts_doc_id in HASH_SCAN Replication Path |
| 119955 | 2026-02-27 5:03 | 2026-03-02 12:46 | MySQL Server: Optimizer | Verified (8 days) | S3 | 8.0.43 (MySQL Community Server - GPL) | Any (Docker container) | Any (x86_64) | Semantically equivalent scalar expressions yield different result sets in WHERE clause involving RPAD() |
| 119954 | 2026-02-26 21:13 | 2026-02-28 17:08 | MySQL Server: Compiling | Open (10 days) | S3 | 8.4.8 | Ubuntu (Ubuntu 24.04.3 LTS) | x86 (n.a.) | libaio1.so loading shared library fails in binary tarball b/c it is renamed to libaio1t64 |
| 119949 | 2026-02-26 14:21 | 2026-03-03 9:28 | MySQL Server: InnoDB storage engine | Open (7 days) | S2 | 9.5.0 | Any | Any | DELETE statement fails to delete the row after blocking is resumed |
| 119947 | 2026-02-26 9:19 | 2026-02-26 9:30 | MySQL Server: Replication | Open | S2 | 8.0.45 | Any | Any | ordered_commit some transactions had flush errors, but committed successfully.resulting in master-slave inconsistency |
| 119945 | 2026-02-26 2:44 | 2026-02-26 2:44 | MySQL Server: Partitions | Open | S3 | 8.0.35 | Any | Any | Inconsistent result set on repeated execution of NATURAL JOIN with expression index and KEY partitioning |
| 119944 | 2026-02-25 22:14 | 2026-02-26 13:13 | MySQL Server: Optimizer | Verified (12 days) | S1 | 8.0, 8.4, 9.X | Any | Any | Feature Request: Extend TIMESTAMP range beyond 2038-01-19 by switching to 64-bit signed storage (Year 2038 Problem) |
| 119943 | 2026-02-25 20:50 | 2026-02-25 22:44 | MySQL Server: Documentation | Open (13 days) | S3 | 8.0, 8.4, 9.x | Any | Any | Documentation for innodb_flush_method is too Vague about its Impact on Data File Reading / Caching. |
| 119938 | 2026-02-25 7:36 | 2026-03-04 3:50 | MySQL Server: Partitions | Verified (6 days) | S2 | 8.0.45, 8.4.8, 9.6.0 | Any | Any | select partition table with virtual column return wong result |
| 119937 | 2026-02-25 4:54 | 2026-02-25 9:25 | MySQL Server: Optimizer | Verified (13 days) | S3 | 8.0 | Any | Any | Result is not correct when using pow function with group by |
| 119927 | 2026-02-20 10:28 | 2026-02-25 8:56 | MySQL Server: Optimizer | Verified (13 days) | S2 | 8.0.45 | Linux | Any | Inconsistent results between direct query and derived table with BIGINT column and FLOAT predicate (IN clause) |
| 119922 | 2026-02-18 16:34 | 2026-02-19 4:45 | MySQL Server: Optimizer | Verified (19 days) | S3 | Any | Any | Contribution: Fix excessive generation of histogram background update erro ... | |
| 119918 | 2026-02-17 8:12 | 2026-02-17 8:31 | MySQL Server: Optimizer | Verified (21 days) | S2 | 9.6.0 | Any | Any | Tree based explain format doesn't work well with MySQL Client or MySQL Shell |
| 119914 | 2026-02-16 13:33 | 2026-02-16 13:33 | MySQL Server: Tests | Open | S3 | 8.0.14+ | Any | Any | MTR --only-big-test incorrectly skips tests that have both big_test.inc and no_valgrind_without_big.inc |
| 119912 | 2026-02-15 4:33 | 2026-02-15 12:09 | MySQL Server: Optimizer | Verified (23 days) | S2 | 8.0.45 | Linux | Any | JOIN query returns different results depending on index visibility |
| 119911 | 2026-02-15 4:25 | 2026-02-20 7:49 | MySQL Server: Documentation | Verified (18 days) | S2 | 8.4 | Any | Any | Documentation is inconsistent |
| 119909 | 2026-02-12 21:31 | 2026-02-12 21:31 | MySQL Server: Optimizer | Open | S2 | 9.5.0 | Any | Any | Wrong result due to unsafe Item_max optimization triggering on homogeneous subqueries but not heterogeneous ones |
| 119908 | 2026-02-12 12:49 | 2026-02-13 7:26 | MySQL Server: Optimizer | Verified (25 days) | S3 | 8.0.34 | Any | Any | GROUP_CONCAT returns corrupted characters when column charset is utf8mb4 and connection charset is gbk |
| 119904 | 2026-02-11 19:27 | 2026-02-17 7:50 | MySQL Server: Parser | Verified (21 days) | S3 | 9.6.0 | Any | Any | In MySQL 9.6.0, Reserved is set 0 for SETS |
| 119881 | 2026-02-10 15:23 | 2026-02-10 15:23 | MySQL Server: Documentation | Open | S3 | 9.6.0 | Any | Any | Outdated URL that points to the internals manual |
| 119877 | 2026-02-10 12:42 | 2026-02-11 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 8.0.42+ | Any | Any | InnoDB Buffer Pool Flush State Mutex Contention (8.0.42-debug) |
| 119861 | 2026-02-09 9:01 | 2026-02-16 8:35 | MySQL Server: Optimizer | Verified (22 days) | S3 | 8.0.44 | Any | Any | Inconsistent query results when using <=> to compare row data with empty set subquery result |
| 119859 | 2026-02-09 7:25 | 2026-02-09 8:06 | MySQL Server: Partitions | Verified (29 days) | S3 | 8.0.35 | Any | Any | Inconsistent Query Results Between Partitioned and Non-Partitioned Tables |
| 119855 | 2026-02-06 18:36 | 2026-02-06 18:38 | MySQL Server: Replication | Open (32 days) | S3 | 8.0 | Any | Any | Relay Log Recovery after mts_recovery_groups failure should be retried |
| 119834 | 2026-02-02 13:44 | 2026-02-03 13:20 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0.44 | Any | Any | Inconsistent query results when selecting different columns with the same JOIN condition involving LIKE (EXISTS(subquery |
| 119832 | 2026-02-02 9:12 | 2026-02-03 12:21 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119831 | 2026-02-02 8:32 | 2026-02-03 12:56 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119825 | 2026-02-01 12:02 | 2026-02-02 3:51 | MySQL Server: Optimizer | Verified (36 days) | S2 | 8.0.45, 8.4.8, 9.6 | Any | Any | Inconsistent results between INNER JOIN and STRAIGHT_JOIN when comparing DOUBLE constant with INT UNIQUE column |
| 119824 | 2026-02-01 11:59 | 2026-02-02 3:57 | MySQL Server: Optimizer | Verified (36 days) | S3 | 8.0.44 | Any | Any | drop index can lead to incorrect results |
| 119823 | 2026-02-01 11:42 | 2026-02-02 3:55 | MySQL Server: Optimizer | Verified (36 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119822 | 2026-01-31 17:35 | 2026-01-31 22:04 | MySQL Server: Optimizer | Verified (38 days) | S2 | 8.0.45 | Any | Any | MySQL and TiDB return different results |
| 119819 | 2026-01-31 10:29 | 2026-01-31 21:41 | MySQL Server: Optimizer | Verified (38 days) | S3 | 8.0.44 | Any | Any | drop index can lead to different results |
| 119818 | 2026-01-31 8:53 | 2026-01-31 21:34 | MySQL Server: Optimizer | Verified (38 days) | S3 | 8.0.44 | Any | Any | A different results occured after inserting a NULL record |
| 119816 | 2026-01-31 7:56 | 2026-01-31 21:19 | MySQL Server: Optimizer | Verified (38 days) | S3 | 8.0.44 | Any | Any | Create index can lead to incorrect results |
| 119815 | 2026-01-31 7:03 | 2026-01-31 21:11 | MySQL Server: Optimizer | Verified (38 days) | S3 | 8.0.44 | Any | Any | An incorrect results after inserting a record |
| 119814 | 2026-01-31 4:11 | 2026-01-31 20:59 | MySQL Server: Optimizer | Verified (38 days) | S3 | 8.0.44 | Any | Any | drop index can lead to incorrect results |
| 119808 | 2026-01-29 14:44 | 2026-01-29 14:44 | MySQL Server: DML | Open | S3 | Any | Any | Error 3569 with HIGH_PRIORITY + VIEW + GROUP BY + FOR UPDATE | |
| 119805 | 2026-01-29 3:21 | 2026-01-29 4:15 | MySQL Server: DML | Verified (40 days) | S2 | 8.0.45 | Any | Any | create_tmp_field assert fail |
| 119802 | 2026-01-28 13:49 | 2026-01-28 15:52 | MySQL Server: Optimizer | Verified (41 days) | S2 | 8.0.42+ | Any | Any | Assertion 'is_nullable()' failed in Item_typecast_signed::val_int() |
| 119801 | 2026-01-28 13:20 | 2026-03-06 11:13 | MySQL Server: InnoDB storage engine | Need Feedback (7 days) | S3 | 8.0.39 | Any | Any | If two transactions concurrently execute updates on the same row, the transaction that performs the update later will fa |
| 119800 | 2026-01-28 8:53 | 2026-01-28 11:54 | MySQL Server: Compiling | Open (41 days) | S1 | 8.4 | Any | Any | An error occurred in ssl.cmake reading version information from opensslv.h, causing HAVE_TLSv13 to fail to compile. |
| 119799 | 2026-01-27 21:40 | 2026-01-28 9:08 | MySQL Server: Optimizer | Verified (41 days) | S3 | 8.0.44 | MacOS | ARM | OR condition incorrectly filters out NULL values in derived table with UNION |
| 119797 | 2026-01-27 20:09 | 2026-02-10 6:48 | MySQL Server: General | Open | S3 | Any | Any | Contribution: Feat: Native Vector Search with HNSW Indexing | |
| 119793 | 2026-01-27 10:32 | 2026-02-04 16:32 | MySQL Server: Prepared statements | Verified (34 days) | S1 | 9.5.0 | Any | Any | Incorrect result of prepared SELECT when running with JDBC |
| 119790 | 2026-01-27 10:14 | 2026-01-27 12:07 | MySQL Server: Optimizer | Verified (42 days) | S1 | 8.0.44 | Any | Any | Unexpected result of expression IN NULL |
| 119784 | 2026-01-27 0:53 | 2026-01-27 1:26 | MySQL Server: Partitions | Open (42 days) | S3 | 8.0.42 and later | Any | Any | Fix partition pruning with non-constant defaults regression |
| 119782 | 2026-01-26 17:22 | 2026-01-27 8:36 | MySQL Server: InnoDB storage engine | Open | S3 | Any | Any | Contribution: Fix partition pruning with non-constant defaults regression | |
| 119780 | 2026-01-26 14:40 | 2026-01-26 15:15 | MySQL Server: Optimizer | Verified (43 days) | S3 | 8.0.44 | Ubuntu (22.04) | Any | UNION ALL + AND + WHERE IS UNKNOWN query results are incorrect |
| 119776 | 2026-01-26 9:31 | 2026-01-26 13:51 | MySQL Server: Optimizer | Verified (43 days) | S3 | 8.0.41 | Any | Any | Semantically identical SQLs yield different result sets. |
| 119775 | 2026-01-26 6:37 | 2026-01-26 6:37 | MySQL Server: MyISAM storage engine | Open | S2 | 9.6.0 | Any | Any | External locking should be removed |
| 119769 | 2026-01-24 14:46 | 2026-03-09 10:48 | MySQL Server: InnoDB storage engine | Open (2 days) | S2 | 9.4.0 | Any | Any | The transaction reads the value inserted by the blocked statement |
| 119767 | 2026-01-24 12:57 | 2026-01-24 12:57 | MySQL Server: Compiling | Open | S2 | 9.6.0 | FreeBSD (15) | x86 | MySQL fails to build on FreeBSD |
| 119766 | 2026-01-23 19:18 | 2026-01-23 19:18 | MySQL Server: Performance Schema | Open | S2 | 8.0.44 | Any | Any | Rows unexpectedly added in performance_schema for failed connections |
| 119759 | 2026-01-22 18:55 | 2026-02-01 20:46 | MySQL Server: InnoDB storage engine | Open (47 days) | S2 | 8.0.42 | Any | Any | InnoDB allow reads on non-durable data, which can be lost after crash(visibility before durability window) |
| 119752 | 2026-01-22 15:08 | 2026-01-22 21:36 | MySQL Server: Optimizer | Verified (47 days) | S3 | 8.0.44 | Any | Any | after changing MINUTE(subq.c1) to MINUTE(subq.c1 + INTERVAL '60' MINUTE),the result become empty. |
| 119744 | 2026-01-22 9:52 | 2026-01-22 9:52 | MySQL Server: InnoDB storage engine | Open | S2 | 9.6.0 | Any | Any | mysqlbackup_page_track_purge_up_to not working |
| 119743 | 2026-01-22 9:16 | 2026-01-22 9:20 | MySQL Server: Packaging | Open (47 days) | S2 | 8.4.8,9.6.0 | Fedora (43) | x86 | Removing mysql-community-server causes issues |
| 119741 | 2026-01-22 7:00 | 2026-01-22 8:35 | MySQL Server: Optimizer | Verified (47 days) | S1 | 8.0.44 | Any | Any | internal_tmp_mem_storage_engine = MEMORY setting makes the DISTINCTROW returns incorrect result on 0 and -0 |
| 119735 | 2026-01-21 14:21 | 2026-01-21 14:21 | MySQL Server: Tests | Open | S3 | 8.4.8 | MacOS (26.2) | ARM | Unhandled error log warning in main.initialize-sha256 |
| 119731 | 2026-01-21 3:10 | 2026-01-21 3:13 | MySQL Server: InnoDB storage engine | Open | S3 | MySQL 8.4 | Any | Any | mysql 8.4 ut_a is invalid |
| 119727 | 2026-01-20 10:11 | 2026-01-27 18:37 | MySQL Server: Data Types | Verified (49 days) | S3 | 8.0.44 | Any | Any | wrong result for 'value between a and null' for certain temporal types |
| 119724 | 2026-01-20 5:55 | 2026-01-20 8:08 | MySQL Server: Optimizer | Verified (49 days) | S3 | 8.0.44 | Any | Any | after changing asin function in group clause,column's value unexpectedly change |
| 119716 | 2026-01-19 1:36 | 2026-01-19 9:16 | MySQL Server: Optimizer | Verified (50 days) | S1 | 8.0.44 | Any | Any | Suboptimal query plan generated by normal query compare to prepared statement |
| 119715 | 2026-01-18 13:14 | 2026-01-18 13:14 | MySQL Server: Documentation | Open | S3 | 8.4, 9.5 | Any | Any | Connection compression for MySQL Classic should include reference to net_buffer_length |
| 119714 | 2026-01-18 12:26 | 2026-01-19 9:01 | MySQL Server: Optimizer | Verified (50 days) | S3 | 8.0.44 | Any | Any | after changing ASIN(hpg31.c1) in group clause,the col_1’s value unexpectedly change. |
| 119713 | 2026-01-18 11:19 | 2026-01-20 9:37 | MySQL Server: Optimizer | Verified (49 days) | S3 | 8.0.39, 8.0.44, 8.4.6 | Any | Any | MySQL has hard time using the right indexes |
| Showing 1-90 of 5977 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
