Showing 1-90 of 5715 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
119004 | 2025-09-12 16:07 | 2025-09-12 16:07 | MySQL Server | Open | S2 | 8.0+ | Any | Any | UNREACHABLE member is not expelled after the group_replication_member_expel_timeout delay |
118999 | 2025-09-12 10:03 | 2025-09-12 10:04 | MySQL Server | Open (3 days) | S3 | 8.4.6 | Linux | Any | Unexpected background histogram update warnings(MY-015116) |
118987 | 2025-09-10 14:53 | 2025-09-11 13:01 | MySQL Server: General | Verified (4 days) | S3 | Any | Any | Contribution: docs: typo unrwapped -> unwrapped | |
118984 | 2025-09-10 7:05 | 2025-09-12 14:13 | MySQL Server: InnoDB storage engine | Verified (3 days) | S3 | 9.4.0 | Any | Any | fts_optimize_read_deleted_doc_id_snapshot reads BEING_DELETED table twice |
118983 | 2025-09-10 6:59 | 2025-09-11 13:03 | MySQL Server: InnoDB storage engine | Verified (4 days) | S3 | 8.0.43 | Any | Any | PCursor::move_to_next_block is not functioning as expected |
118982 | 2025-09-10 6:55 | 2025-09-11 12:57 | MySQL Server: Optimizer | Analyzing (4 days) | S1 | 9.4.0 | Linux | Any | Unexpected result of IN operator |
118981 | 2025-09-10 3:41 | 2025-09-11 12:57 | MySQL Server: DML | Analyzing (4 days) | S3 | 8.0.41 | Any | Any | adding DEFAULT FUNCTION in the where clause, the query returns a wrong result caused by the cached value. |
118980 | 2025-09-10 2:52 | 2025-09-11 13:04 | MySQL Server: Optimizer | Verified (4 days) | S2 | MySQL8.0.41 | Any | Any | queries have different results using and without index |
118960 | 2025-09-09 2:57 | 2025-09-09 7:12 | MySQL Server: Optimizer | Verified (6 days) | S5 | 9.2, 8.0, 8.4 | Any | Any | Sort optimization fails as primary key info in secondary index is not considered after hint-enforced secondary index |
118956 | 2025-09-08 11:41 | 2025-09-09 23:48 | MySQL Server | Need Feedback (6 days) | S2 | 8.0.32+ | Any | Any | Incorrect result when condition use concat function |
118949 | 2025-09-05 13:57 | 2025-09-10 0:42 | MySQL Server: Optimizer | Verified (7 days) | S2 | 9.2.0 | Linux (ubuntu 20.04) | Any | MySQL 9.2.0: Complex CASE in JOIN makes INNER vs INTERSECT yield different rows |
118941 | 2025-09-05 8:19 | 2025-09-10 14:45 | MySQL Server: Optimizer | Verified (5 days) | S2 | 8.0.x, 8.4.x | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with -0.001 Excludes 0.00 Row |
118937 | 2025-09-04 4:36 | 2025-09-10 0:43 | MySQL Server: Optimizer | Verified (6 days) | S2 | 9.4.0 | Any | Any | LEFT JOIN with constant functions returns incorrect results when condition is ON FALSE |
118936 | 2025-09-03 21:56 | 2025-09-04 2:13 | MySQL Server | Need Feedback (11 days) | S3 | 8.0.34 | Windows (Windows 10) | x86 (Can not set root password) | Root password |
118927 | 2025-09-02 21:41 | 2025-09-03 10:12 | MySQL Server: Parser | Need Feedback (12 days) | S3 | 9.4 | Any | ARM (arm64) | Incorrect Binary Library Hex Representation Due to Sign Extension in SHOW CREATE LIBRARY |
118923 | 2025-09-02 7:49 | 2025-09-04 11:46 | MySQL Server: InnoDB storage engine | Verified (12 days) | S2 | 8.4, 8.0.22, 9.4.0 | Any | Any | Abnormal read phenomena are observed under MySQL's Read Committed isolation level |
118918 | 2025-09-01 7:30 | 2025-09-04 11:47 | MySQL Server: Optimizer | Verified (12 days) | S2 | 9.4.0 | Any | Any | Inconsistent NULL handling in CTE LEFT JOIN results |
118913 | 2025-08-29 3:40 | 2025-09-01 10:19 | MySQL Server: Optimizer | Verified (14 days) | S2 | 8.0.41, 9.4.0 | Any | Any | queries have different results for non primary key table and table with primary key |
118912 | 2025-08-28 16:24 | 2025-09-04 11:48 | MySQL Server: Optimizer | Verified (14 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Mismatch in Column values with SUM of IFNULL vs IFNULL of SUM |
118909 | 2025-08-28 11:04 | 2025-09-04 11:49 | MySQL Server: Optimizer | Verified (12 days) | S3 | 8.0.41, 9.4.0 | Linux | x86 | Inconsistent evaluation of WHERE predicate between table-scan and covering-index paths; result set changes with projecti |
118904 | 2025-08-28 3:20 | 2025-09-04 11:46 | MySQL Server: Optimizer | Verified (14 days) | S2 | 8.0.41+ | Any | Any | Incorrect results could be returned when using index condition pushdown and Range checked for each record |
118903 | 2025-08-28 2:20 | 2025-09-01 9:10 | MySQL Server: Optimizer | Need Feedback (14 days) | S3 | Any | Any | Incorrect results could be returned when using index condition pushdown | |
118893 | 2025-08-26 8:31 | 2025-09-04 11:53 | MySQL Server: Optimizer | Verified (14 days) | S3 | 9.4.0-1.el9 | Linux | Any | "SELECT AUTO_INCREMENT FROM information_schema.TABLES" reports a value that is reduced by one |
118890 | 2025-08-25 12:32 | 2025-09-04 11:52 | MySQL Server: Documentation | Verified (14 days) | S3 | 8.0, 8.4, 9.2 | Any | Any | wrong supported ranges in the manual |
118888 | 2025-08-25 7:19 | 2025-08-29 11:13 | MySQL Server: DDL | Verified (21 days) | S2 | 8.0.43/8.4.6 | Any | Any | DDL operation fills the entire disk space and eventually fails |
118887 | 2025-08-25 2:49 | 2025-08-29 11:06 | MySQL Server: Optimizer | Verified (21 days) | S3 | 9.4.0 | CentOS | Any | Zero '0000-00-00 00:00:00' datetime returned when SQL_BUFFER_RESULT is used |
118885 | 2025-08-24 12:05 | 2025-08-29 11:10 | MySQL Server: Compiling | Verified (21 days) | S2 | 8.4.6 | MacOS | Any | mysql8 @8.4.6: ld: unknown option: -no_warn_duplicate_libraries |
118876 | 2025-08-21 13:22 | 2025-08-25 12:00 | MySQL Server: Documentation | Verified (25 days) | S3 | 9.4 | Any | Any | Contribution: docs: update protocol description |
118875 | 2025-08-21 12:42 | 2025-08-21 13:16 | MySQL Server: DML | Verified (25 days) | S3 | 8.0.41, 8.0.43 | Any | Any | set optimizer_switch='block_nested_loop=off/on', result is different. |
118872 | 2025-08-21 5:01 | 2025-08-21 6:31 | MySQL Server: InnoDB storage engine | Verified (25 days) | S3 | 8.0.40 | Any | Any | Innodb_data_written lacks statistics for double-write files |
118871 | 2025-08-21 2:37 | 2025-08-29 11:12 | MySQL Server: Optimizer | Verified (21 days) | S3 | 8.0.43 MySQL Community Server - GPL | Linux (Linux (Rocky Linux release 8.8 (Green Obsidian))) | Any | Constant conditions in SQL with derived views are not passed.new |
118867 | 2025-08-20 18:35 | 2025-09-01 11:12 | MySQL Server: InnoDB storage engine | Verified (25 days) | S3 | 9.4 | Any | Any | Contribution: Optimize NUMA Scheduling |
118866 | 2025-08-20 18:17 | 2025-08-21 6:22 | MySQL Server: InnoDB storage engine | Verified (25 days) | S3 | 9.4 | Any | Any | Contribution: Optimize hash_table_locks |
118865 | 2025-08-20 18:17 | 2025-08-21 6:21 | MySQL Server: Performance Schema | Verified (25 days) | S3 | 9.4 | Any | Any | Contribution: Optimize process of thread counter |
118864 | 2025-08-20 18:17 | 2025-08-21 6:20 | MySQL Server: InnoDB storage engine | Verified (25 days) | S3 | 9.4 | Any | Any | Contribution: Optimize undo spaces lock |
118863 | 2025-08-20 14:23 | 2025-08-21 6:30 | MySQL Server: Optimizer | Verified (25 days) | S2 | 8.4.x, 8.4.6 | Any | Any | Complex collection query incorrectly missing '0' |
118862 | 2025-08-20 14:05 | 2025-08-21 6:28 | MySQL Server: Optimizer | Verified (25 days) | S3 | 8.0.x, 8.4.x, 8.0.43 | Any | Any | MySQL Returns Incorrect Results for Complex Query with Set Operations |
118858 | 2025-08-20 8:51 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (26 days) | S3 | 9.2.0 | Linux | Any | Inconsistency between the results returned by MySQL and other vendors' database systems was found during differentiation |
118857 | 2025-08-20 8:39 | 2025-08-20 10:19 | MySQL Server: Optimizer | Verified (26 days) | S2 | 9.2.0 | Linux | Any | Bug Summary: MySQL Returns Incorrect Results for Complex Query with Set Operations |
118849 | 2025-08-18 12:14 | 2025-08-18 23:50 | MySQL Server: Optimizer | Verified (28 days) | S3 | 8.0.41 | Any | Any | after add HINT:JOIN_ORDER, the result is wrong. |
118848 | 2025-08-15 21:07 | 2025-08-18 8:55 | MySQL Server: Errors | Need Feedback (28 days) | S3 | 8.0.43 | Windows (Microsoft Windows 11 Home) | Any | My screen is black when i try to open an EER diagram |
118846 | 2025-08-15 8:50 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (27 days) | S3 | 9.3.0 | Ubuntu | Any | column name change cased by where |
118844 | 2025-08-14 23:06 | 2025-08-16 5:57 | MySQL Server: Information schema | Verified (30 days) | S3 | 9.4.0 | Any | Any | In MySQL 9.4.0, Reserved is set 0 in information schema for one of the new keyword out of 2 |
118842 | 2025-08-14 8:50 | 2025-09-11 2:28 | MySQL Server: InnoDB storage engine | Verified (4 days) | S1 | 8.4.6 | Red Hat (9.4) | x86 | Transactions get stuck in stage/sql/waiting for handler commit until mysqld restart (MySQL 8.4.3), heavy concurrent DML |
118841 | 2025-08-14 6:20 | 2025-08-25 9:10 | MySQL Server | Need Feedback (21 days) | S2 | 9.2.0 | Any | Any | MYSQL 9.2.0, Facing issue while doing Manual HA promote to source |
118839 | 2025-08-14 3:13 | 2025-08-18 23:50 | MySQL Server: DML | Verified (28 days) | S3 | 8.0.41 | Any | Any | a query including the having subclause that returns NULL, return a wrong nonempty result. |
118837 | 2025-08-14 3:05 | 2025-08-18 23:51 | MySQL Server: Optimizer | Verified (28 days) | S3 | 8.0.41 | Any | Any | After having(col) in the query statement is changed to having min(col), the returned result is incorrect. |
118836 | 2025-08-14 3:01 | 2025-08-18 23:56 | MySQL Server: Optimizer | Verified (28 days) | S3 | 8.0.41 | Any | Any | adding a having clause that return 1/TRUE, the query returns a different and wrong empty result. |
118835 | 2025-08-14 2:56 | 2025-08-19 0:17 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41 | Any | Any | A query statement that returns 0/FALSE in the having clause, the returned result is not null. |
118833 | 2025-08-14 2:43 | 2025-08-19 0:36 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41 | Any | Any | Two queries that use the where clause with opposite semantics return the same result. |
118832 | 2025-08-14 2:39 | 2025-08-19 7:34 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41, 9.4.0 | Any | Any | using the return value replacing the IFNUILL function , the query returns different value; |
118831 | 2025-08-14 2:33 | 2025-08-19 10:51 | MySQL Server: Optimizer | Verified (27 days) | S3 | 8.0.41, 9.4.0 | Any | Any | !(expression1 or expression2) return a different result from !(expression1), while expression2 is 0. |
118830 | 2025-08-14 2:26 | 2025-08-19 10:51 | MySQL Server: DML | Verified (27 days) | S3 | 8.0.41, 9.4.0 | Any | Any | After a constant value is replaced by a LEAST function returnning the same value, the sql returns different result; |
118820 | 2025-08-13 7:39 | 2025-08-20 6:01 | MySQL Server: InnoDB storage engine | Verified (27 days) | S2 | 8.0.41 | Any | Any | AHI results the mysqld hung and assertion failure: btr0sea.cc:295:sleep_counter < 60000 |
118819 | 2025-08-13 5:53 | 2025-08-13 21:29 | MySQL Server: Command-line Clients | Verified (33 days) | S2 | 9.4.0 | Any | Any | Vertical (\G) doesn't work in MySQL 9.4.0 |
118818 | 2025-08-13 3:44 | 2025-08-18 12:16 | MySQL Server: InnoDB storage engine | Verified (28 days) | S2 | 8.0.41, 8.0.43 | Any | Any | Assertion failure row0pread.h:306:active >= n_threads happens when create thread fail for parallel scan |
118817 | 2025-08-12 11:35 | 2025-08-13 7:23 | MySQL Server: DDL | Verified (33 days) | S3 | 8.0 | Any | Any | Code Comment Error for row_import::m_n_instant_cols in storage/innobase/row/row0import.cc |
118811 | 2025-08-11 3:31 | 2025-08-11 12:02 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0.43 | Linux | x86 | When hints are added, different execution plans are used for query. The query result are different. |
118810 | 2025-08-11 3:19 | 2025-08-11 10:35 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0.41, 8.0.43, 8.4.6 | Linux | x86 | he query result are inconsistent,when select difference indexes |
118808 | 2025-08-10 11:26 | 2025-08-11 7:00 | MySQL Server: Optimizer | Verified (35 days) | S2 | 9.4.0, 8.4.3, 8.4.6 | Any | Any | Different result with range scan and table scan in sql with subquery |
118806 | 2025-08-09 13:00 | 2025-08-11 5:39 | MySQL Server: Optimizer | Verified (35 days) | S3 | 8.0,9.0, 8.0.43, 8.4.6, 9.4.0 | Ubuntu | x86 | NULLIF with VARCHAR omits rows unexpectedly |
118805 | 2025-08-09 12:04 | 2025-08-19 8:34 | MySQL Server: Pluggable Authentication | Verified (27 days) | S2 | 8.0.30, 8.0.43, 8.4.6 | Windows (11 Pro) | x86 (64 bit) | mysqld fails to start |
118804 | 2025-08-08 23:48 | 2025-08-11 4:58 | MySQL Server: Packaging | Verified (35 days) | S3 | 8.4 | Any | Any | Contribution: Replace ps|grep with pgrep for MySQL process detection (8.4) |
118803 | 2025-08-08 23:48 | 2025-08-11 4:56 | MySQL Server: Packaging | Verified (35 days) | S3 | 9.4 | Any | Any | Contribution: Replace ps|grep with pgrep for MySQL process detection (trunk) |
118798 | 2025-08-07 9:22 | 2025-08-08 7:36 | MySQL Server: Replication | Verified (38 days) | S1 | 8.0.40 | Ubuntu | Any | Replication Break in 8.0.40 salve when from 8.0.33 Master |
118797 | 2025-08-07 2:08 | 2025-08-07 9:17 | MySQL Server: Replication | Verified (39 days) | S2 | 8.4, 8.4.6, 9.4.0 | Any | Any | Contribution by Tencent: previous gtids may loss xa commit/rollback gtids |
118796 | 2025-08-06 22:31 | 2025-09-01 15:27 | MySQL Server: Compiling | Verified (14 days) | S3 | 9.4.0 / 8.4.6 | Oracle Linux (10) | x86 | RPM spec files are missing some buildrequires |
118788 | 2025-08-06 9:33 | 2025-08-21 8:59 | MySQL Server: Optimizer | Verified (40 days) | S3 | 8.0.41, 8.0.43 | Linux | x86 | When two tables are joined, the execution results are different in different join order. |
118768 | 2025-08-01 10:29 | 2025-08-04 5:29 | MySQL Server: Storage Engines | Verified (42 days) | S3 | 8.0 | Any | Any | Link_buf may not advance the tail correctly |
118765 | 2025-08-01 2:56 | 2025-08-01 5:26 | MySQL Server: DML | Verified (45 days) | S3 | 8.0, 9.0, 8.4.6, 8.0.43 | Any | Any | Substring_index with negative index returns inconsistent results across different character sets |
118750 | 2025-07-30 3:33 | 2025-07-30 5:51 | MySQL Server: Prepared statements | Analyzing (47 days) | S3 | 9.3.0 | Any | Any | binary comparison has different results in prepared statement and normal SELECT query |
118729 | 2025-07-28 13:17 | 2025-07-29 6:37 | MySQL Server: Optimizer | Verified (48 days) | S3 | 8.4.4 (Any), 8.0.43, 8.4.6, 9.4.0 | Any | Any | Select Query is showing wrong column name alias from sub-query |
118724 | 2025-07-26 12:08 | 2025-08-11 12:06 | MySQL Server: Performance Schema | Verified (35 days) | S5 | 8.0.42 | Any | Any | optimzie for performance_schema |
118723 | 2025-07-26 11:54 | 2025-07-28 4:29 | MySQL Server: InnoDB storage engine | Verified (49 days) | S5 | 8.0.42 | Any | Any | optimize for innodb insert |
118722 | 2025-07-26 11:08 | 2025-07-29 4:09 | MySQL Server | Analyzing (48 days) | S3 | 8.0.41 | Linux | ARM | ERROR 1267 (HY000): Illegal mix of collations (latin1_bin,IMPLICIT) and (utf8mb4_0900_ai_ci,COERCIBLE) for operation '=' |
118710 | 2025-07-23 12:08 | 2025-07-23 12:42 | MySQL Server: Optimizer | Verified (54 days) | S1 | 8.0.36, 8.0.42, 8.0.43, 8.4.6 | Windows | Any | Optimizer incorrectly simplifies negative float/decimal comparison in JOIN condition, leading to wrong results |
118705 | 2025-07-23 8:06 | 2025-08-13 11:06 | MySQL Server: InnoDB storage engine | Verified (52 days) | S2 | 8.0 | Any | Any | when call que_eval_sql, may crash. |
118695 | 2025-07-22 7:11 | 2025-07-23 7:33 | MySQL Server: InnoDB storage engine | Verified (54 days) | S3 | 8.0 | Any | Any | This if condition seems to be useless in btr0cur.cc:1398 |
118694 | 2025-07-22 7:03 | 2025-07-22 11:45 | MySQL Server: DML | Verified (55 days) | S3 | 8.0.41 5.7, 8.0.42 | Any | Any | Item_func_between deal with decimel different from other methods |
118693 | 2025-07-22 5:52 | 2025-07-22 6:34 | MySQL Server: InnoDB storage engine | Verified (55 days) | S3 | 8.0.42 | Any | Any | Increasing length of varchar field should be inplace. |
118684 | 2025-07-18 14:54 | 2025-07-21 6:07 | MySQL Server: Optimizer | Verified (56 days) | S2 | 9.2.0, 8.0.42, 8.4.5 | Linux | Any | Inconsistent rows are returned |
118682 | 2025-07-18 3:52 | 2025-07-24 6:33 | MySQL Server: Options | Verified (53 days) | S2 | 8.0, 8.0.42 | Any | Any | connection_memory_limit and global_connection_memory_limit don't work |
118681 | 2025-07-18 2:54 | 2025-07-18 5:22 | MySQL Server: InnoDB storage engine | Verified (59 days) | S5 | 8.0.42 | Any | Any | Reduce the locking scope of dict_sys_mutex in dict_stats_drop_table |
118669 | 2025-07-16 5:22 | 2025-07-16 6:46 | MySQL Server: Optimizer | Verified (61 days) | S1 | 8 and above, 8.0.42, 8.4.5, 9.3.0 | Any | Any | Issue in applying limit on aggregated data |
118658 | 2025-07-15 6:11 | 2025-07-15 6:16 | MySQL Server: Data Types | Verified (62 days) | S3 | 9.2.0, 8.0, 8.0.42 | Any | Any | Issue with NULL Detection for DATE-Type Columns in Derived Tables After Derived Merge |
118653 | 2025-07-14 3:35 | 2025-07-14 5:09 | MySQL Server: XA transactions | Verified (63 days) | S3 | 8.0.35, 9.3.0 | Any | Any | The threads waiting for the MDL lock and the threads holding the lock are the same |
118624 | 2025-07-10 2:47 | 2025-07-10 8:15 | MySQL Server: InnoDB storage engine | Verified (67 days) | S1 | 8.3.0, 8.0.42, 8.3.0, 8.4.5, 9.3.0 | Any | Any | Wrong result when icp(push a 'like condition' into engine) |
118621 | 2025-07-09 12:39 | 2025-07-09 14:19 | MySQL Server: Optimizer | Verified (68 days) | S3 | 9.3.0, 8.0.42 | Any | Any | subquery_to_derived optimizer makes query produce incorrect result |
118611 | 2025-07-09 4:40 | 2025-07-09 8:27 | MySQL Server: DDL | Verified (68 days) | S3 | 8.4, 8.0.42 | Linux | Any | Creating an InnoDB table with a CONNECTION clause should not be allowed |
118594 | 2025-07-07 14:16 | 2025-07-07 14:58 | MySQL Server: InnoDB storage engine | Verified (70 days) | S2 | 8.0.42 | Any | Any | In-place ALTER TABLE ... ADD FOREIGN KEY can sometimes fails with unwarranted error or even crashes |
Showing 1-90 of 5715 (Edit, Save, CSV, Feed) | Show Next 90 Entries » |