| Showing all 116 (Edit, Save, CSV, Feed) |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 119225 | 2025-10-24 9:11 | 2025-10-24 9:11 | MySQL Server | Open | S3 | 8.0.43 | Any | Any | weedout not work for rematerialized temptable |
| 119223 | 2025-10-24 3:16 | 2025-10-24 3:16 | MySQL Server | Open | S3 | 8.0.30 | Any | Any | The pfs_thread.processlist_id is set to NULL after using Srv_session |
| 119215 | 2025-10-23 9:16 | 2025-10-23 9:36 | MySQL Server | Open (2 days) | S3 | 8.0.30 | Any | Any | pfs_thread.processlist_id will be null after select group_replication_reset_member_actions() |
| 119200 | 2025-10-21 8:19 | 2025-10-21 8:19 | MySQL Server | Open | S3 | 8.4.x | Any | Any | make connection access sorting rule sane and predictable |
| 119174 | 2025-10-16 13:18 | 2025-10-23 12:22 | MySQL Server | Open (2 days) | S3 | 9.4.0 | Any | Any | unexpected value after changing Max to Min |
| 119172 | 2025-10-16 10:00 | 2025-10-16 10:00 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for NOT BETWEEN When Date Interval Arithmetic Produces NULLs |
| 119171 | 2025-10-16 9:34 | 2025-10-16 9:34 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result for BETWEEN NULL AND NULL on a DECIMAL Column |
| 119170 | 2025-10-16 9:23 | 2025-10-16 9:23 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result with string = SOME (DECIMAL) |
| 119169 | 2025-10-16 9:08 | 2025-10-16 9:08 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent Result with DAYNAME() and DECIMAL |
| 119168 | 2025-10-16 8:47 | 2025-10-16 8:47 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Inconsistent results for CHAR IN (subquery returning BIT) |
| 119165 | 2025-10-16 5:46 | 2025-10-16 5:46 | MySQL Server | Open | S3 | 9.4.0 | Any | Any | unexpected value after changing Max to Min |
| 119154 | 2025-10-14 13:24 | 2025-10-14 13:24 | MySQL Server | Open | S1 | 8.4.6 | Any | Any | Incorrect BIT_COUNT value for TEXT column |
| 119147 | 2025-10-13 13:39 | 2025-10-13 13:39 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | >= SOME Operator Returns Incorrect Empty Set for TIMESTAMP Comparison |
| 119146 | 2025-10-13 12:53 | 2025-10-13 12:53 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | WHERE IN with Subquery Incorrectly Matches VARCHAR to DECIMAL via Implicit Casting |
| 119140 | 2025-10-13 8:01 | 2025-10-13 8:01 | MySQL Server | Open | S1 | 9.4.0 | Any | Any | DISTINCT works inconsistently in normal SELECT and prepared statement for 0 and -0 |
| 119139 | 2025-10-13 7:30 | 2025-10-13 7:37 | MySQL Server | Open (12 days) | S1 | 9.4.0 | Any | Any | Unexpected error `Incorrect DECIMAL value: '0' for column '' at row -1` |
| 119138 | 2025-10-13 3:45 | 2025-10-13 3:45 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result with BINARY EXISTS(...) IN (...) on TIMESTAMP column |
| 119137 | 2025-10-13 3:23 | 2025-10-13 3:23 | MySQL Server | Open | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for ADDTIME expression |
| 119136 | 2025-10-13 3:14 | 2025-10-13 3:14 | MySQL Server | Open | S2 | 8.4.6 | Any | Any | Incompatible behavior between integer columns when comparing with datetime |
| 119129 | 2025-10-10 14:13 | 2025-10-10 14:13 | MySQL Server | Open | S1 | 9.4.0 | Any | Any | Unexpected error `BIGINT value is out of range in '--9223372036854775808'` |
| 119114 | 2025-10-08 7:54 | 2025-10-23 12:14 | MySQL Server | Open (2 days) | S3 | 9.4.0 | Any | Any | Column Value change caused by COUNT(column) --->COUNT(DISTINCT column) |
| 119089 | 2025-09-29 1:32 | 2025-10-07 0:58 | MySQL Server | Not a Bug (18 days) | S2 | 8.4.6-10.fc42 | Fedora (42) | Other (amd64) | community-mysql has file conflicts with mariadb-server |
| 119087 | 2025-09-28 5:54 | 2025-10-11 3:24 | MySQL Server | Open (14 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect result for subquery with BIGINT UNSIGNED |
| 119085 | 2025-09-27 15:45 | 2025-09-28 15:54 | MySQL Server | Unsupported (27 days) | S2 | 9.4.0 | Linux | Any | FLUSH PRIVILEGES crashes server after a column is dropped from mysql.servers table. |
| 119055 | 2025-09-22 15:14 | 2025-09-22 17:36 | MySQL Server | Duplicate (33 days) | S3 | 9.4.0 | Any | Any | column value change cased by AVG() changed to SUM()/COUNT() |
| 119054 | 2025-09-22 10:35 | 2025-09-22 17:39 | MySQL Server | Unsupported (33 days) | S3 | 9.4.0 8.4.6 | Any | Any | Incorrect SOUNDS LIKE result in WHERE clause with complex function arguments and type casting |
| 119047 | 2025-09-20 7:31 | 2025-09-22 17:48 | MySQL Server | Duplicate (33 days) | S3 | 9.4.0 | Any | Any | column value change cased by Union ALL |
| 119039 | 2025-09-19 6:23 | 2025-09-22 17:02 | MySQL Server | Unsupported (33 days) | S2 | 5.7 | Any | Any | Inconsistent GROUP BY results between MySQL 5.5 and 5.7 for complex CASE expression in derived table |
| 119005 | 2025-09-15 7:56 | 2025-10-11 3:23 | MySQL Server | Open (14 days) | S3 | localhost3306 | Any | Any | wizard import bug |
| 119004 | 2025-09-12 16:07 | 2025-10-11 3:23 | MySQL Server | Open (14 days) | S2 | 8.0+ | Any | Any | UNREACHABLE member is not expelled after the group_replication_member_expel_timeout delay |
| 118967 | 2025-09-09 8:28 | 2025-09-09 11:58 | MySQL Server | Duplicate (46 days) | S2 | 8.4.4 | Any | Any | Bug Report: DECIMAL(22,2) Column Comparison with >= -0.001 Excludes 0.00 Row |
| 118956 | 2025-09-08 11:41 | 2025-10-10 1:00 | MySQL Server | No Feedback (16 days) | S2 | 8.0.32+ | Any | Any | Incorrect result when condition use concat function |
| 118936 | 2025-09-03 21:56 | 2025-10-05 1:00 | MySQL Server | No Feedback (21 days) | S3 | 8.0.34 | Windows (Windows 10) | x86 (Can not set root password) | Root password |
| 118920 | 2025-09-01 11:29 | 2025-09-04 1:34 | MySQL Server | Not a Bug (51 days) | S3 | 8.0.43 | Any | Any | Optimize: change CHAR column charset from utf8mb3 to utf8mb4 can Inplace |
| 118879 | 2025-08-22 7:05 | 2025-08-23 9:47 | MySQL Server | Not a Bug (63 days) | S3 | 8.0 | Windows | Any | facing bug issue |
| 118841 | 2025-08-14 6:20 | 2025-09-26 1:00 | MySQL Server | No Feedback (30 days) | S2 | 9.2.0 | Any | Any | MYSQL 9.2.0, Facing issue while doing Manual HA promote to source |
| 118826 | 2025-08-13 16:39 | 2025-08-19 10:07 | MySQL Server | Not a Bug (67 days) | S3 | 9.4 | Windows (11) | x86 | msql.connector.connect does not exist using mysql.connector.python |
| 118787 | 2025-08-06 9:00 | 2025-08-06 18:01 | MySQL Server | Can't repeat (80 days) | S1 | 8.0.32 | Windows | Any | MySQL server crashed |
| 118772 | 2025-08-02 15:23 | 2025-08-04 12:14 | MySQL Server | Can't repeat (82 days) | S3 | 8.0 ce | Any (bug) | Any (bug ) | report a bug |
| 118722 | 2025-07-26 11:08 | 2025-09-21 20:45 | MySQL Server | Analyzing (88 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 '=' |
| 118664 | 2025-07-15 14:00 | 2025-09-21 20:45 | MySQL Server | No Feedback (70 days) | S3 | 8.0.42 | MacOS (macOS 14.x Sonoma x86_64) | Any | app crashes |
| 118654 | 2025-07-14 7:22 | 2025-08-05 14:20 | MySQL Server | Can't repeat (81 days) | S2 | 8.0.30 | Red Hat (7.9) | x86 (48 core) | Assertion failure: page0cur.cc:1206 thread 139804775790336 |
| 118538 | 2025-06-27 4:56 | 2025-08-02 1:00 | MySQL Server | No Feedback (85 days) | S3 | 8.0.30 | Linux (Amazon Linux 2) | x86 | Undo Logs Not Shrinking Despite No Active Long Transactions or Open Snapshots |
| 118521 | 2025-06-25 2:54 | 2025-07-17 12:12 | MySQL Server | Not a Bug (100 days) | S3 | Any | Any | cast(double as char) result is incorrect | |
| 118506 | 2025-06-23 15:03 | 2025-07-01 11:29 | MySQL Server | Not a Bug (116 days) | S1 | 8.0.26 | Linux | Any | innodb data files increased to max storage due to autoextend param provided in conf file |
| 118453 | 2025-06-16 8:50 | 2025-08-05 13:02 | MySQL Server | Not a Bug (81 days) | S3 | 8.0.41 | Any | Any | select datetime field returns wrong result after update |
| 118415 | 2025-06-11 11:36 | 2025-07-12 1:00 | MySQL Server | No Feedback (106 days) | S3 | 8.0 | Any | Any | [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid |
| 118414 | 2025-06-11 11:30 | 2025-06-11 16:13 | MySQL Server | Duplicate (136 days) | S3 | 8.0 | Any | Any | [MY-013129] [MY-011809] [MY-011153] |
| 118366 | 2025-06-05 6:46 | 2025-06-05 9:58 | MySQL Server | Unsupported (142 days) | S3 | 5.7.38-log | CentOS | x86 | using the myisam engine and am having trouble with swap memory usage even though there is available system memory |
| 118333 | 2025-06-03 3:44 | 2025-08-04 13:20 | MySQL Server | Duplicate (82 days) | S3 | 8.0.41，all | Linux | x86 | The collation_connection value of the session connection does not match the expected value. |
| 118318 | 2025-05-30 14:10 | 2025-06-04 8:34 | MySQL Server | Unsupported (143 days) | S1 | Linux (OpenSUSE) | x86 | Compiler errors on openSUSE | |
| 118314 | 2025-05-30 11:08 | 2025-05-31 13:41 | MySQL Server | Not a Bug (147 days) | S3 | 8.0.41 | Any | Any | TRUNCATE TABLE does not reset AUTO_INCREMENT in MySQL 8.0.41 |
| 118189 | 2025-05-14 8:50 | 2025-05-14 9:03 | MySQL Server | Not a Bug (164 days) | S3 | Any | Any | show engine innodb status SEMAPHORES lost some wait information？ | |
| 118157 | 2025-05-09 12:35 | 2025-06-19 10:42 | MySQL Server | Can't repeat (128 days) | S3 | 8.4.5 | Any | Any | Depricated warning bug "Setting user variables within expressions is deprecated" |
| 118148 | 2025-05-09 3:47 | 2025-06-10 13:21 | MySQL Server | Not a Bug (137 days) | S3 | 9.2.0 | Linux | x86 | Error When Deleting from MERGE Table with Subquery Condition |
| 118147 | 2025-05-09 3:18 | 2025-06-09 13:10 | MySQL Server | Not a Bug (138 days) | S3 | 9.2.0 | Linux | x86 | Error When Reopening Temporary Table |
| 118145 | 2025-05-09 3:09 | 2025-05-12 7:01 | MySQL Server | Duplicate (166 days) | S3 | 9.2.0 | Ubuntu | x86 | Error Creating Index on EmployeeArchive Table |
| 118122 | 2025-05-06 16:07 | 2025-05-07 12:13 | MySQL Server | Closed (171 days) | S3 | 8.0.41 | Windows (Windows 11) | x86 | Exception Loading keyring_file.dll on Windows in v8.0.41 |
| 118106 | 2025-05-02 12:13 | 2025-05-05 11:30 | MySQL Server | Can't repeat (173 days) | S1 | 8.0.41 | Ubuntu | Any | Assertion failure |
| 118084 | 2025-04-29 9:52 | 2025-09-21 20:45 | MySQL Server | No Feedback (55 days) | S3 | 5.7.35, 8.0.37 | Any | Any | varchar NULL after alter json not null,value is null |
| 118062 | 2025-04-26 16:39 | 2025-04-27 7:32 | MySQL Server | Not a Bug (181 days) | S3 | Windows | Any | it is not opening the network connection and showing the report bug | |
| 118060 | 2025-04-25 16:53 | 2025-09-21 20:45 | MySQL Server | Analyzing (180 days) | S2 | 8.0.40 | Any | Any | After an error occurs when importing data containing NULL fields, insert can not be executed normally. |
| 118051 | 2025-04-24 10:51 | 2025-05-05 11:35 | MySQL Server | Not a Bug (173 days) | S3 | 8.0 | Any | Any | Semi-Sync Replication Relay Log Flushing Discrepancy |
| 117989 | 2025-04-15 14:58 | 2025-04-17 6:06 | MySQL Server | Closed (191 days) | S1 | 8.4.5 | Any (AlmaLinux/CloudLinux/Rocky Linux) | x86 | After upgrading to version 8.4.5 MySQL will throw database connection error in all sites |
| 117929 | 2025-04-10 6:54 | 2025-07-29 14:49 | MySQL Server | Can't repeat (166 days) | S1 | 8.0.41 | Ubuntu (Ubuntu - 22.04) | ARM (Azure VM) | MySQL - 8.0.41 consuming more CPU |
| 117906 | 2025-04-08 7:11 | 2025-04-15 4:23 | MySQL Server | Verified (193 days) | S3 | 8.0, 8.4 | Any | Any | User Defined Functions (UDF) have documented char *is_null, *error, however defined as unsigned char * |
| 117881 | 2025-04-04 2:01 | 2025-04-04 11:58 | MySQL Server | Duplicate (204 days) | S3 | 8.4.4 | Linux (Rocky Linux 8.8) | x86 (4.18.0-477.21.1.el8_8.x86_64) | MY-013935 error message occurs frequently |
| 117859 | 2025-04-02 9:51 | 2025-04-03 10:38 | MySQL Server | Can't repeat (205 days) | S2 | Any | Any | dict_stats_thread crash on fseg_inode_get | |
| 117833 | 2025-03-30 15:29 | 2025-04-01 10:34 | MySQL Server | Not a Bug (207 days) | S2 | 9.2.0 | Ubuntu | Any | Incorrect parse the query |
| 117829 | 2025-03-29 1:02 | 2025-04-01 4:43 | MySQL Server | Can't repeat (207 days) | S2 | Any | Any | crash on rec_get_status | |
| 117795 | 2025-03-25 16:25 | 2025-03-31 13:24 | MySQL Server | Can't repeat (208 days) | S3 | 8.0.40 | Red Hat | Any | relay-bin is not removed after 'flush log' in primary node under innodb replicaset |
| 117758 | 2025-03-20 11:06 | 2025-03-21 8:11 | MySQL Server | Can't repeat (218 days) | S2 | 8.0.37 | Other (gentoo linux) | x86 (Intel(R) Xeon(R) Gold 6250 CPU) | assert in rtr_page_copy_rec_list_end_no_locks |
| 117693 | 2025-03-12 23:59 | 2025-03-22 2:21 | MySQL Server | Not a Bug (218 days) | S1 | 8.0.41 | Windows (Server 2019 HyperV) | Any | 'aio write' returned OS error 0. / Assertion failure: os0file.cc:6809:slot->is_reserved thread |
| 117678 | 2025-03-12 9:51 | 2025-03-12 14:34 | MySQL Server | Duplicate (227 days) | S3 | 8.4.2 | Windows | Any | MySQL 8.4.2 MY-013935 IO-layer timeout before wait_timeout was reached. |
| 117657 | 2025-03-10 16:47 | 2025-10-15 17:00 | MySQL Server | Not a Bug (227 days) | S3 | 8.4.4 | Other (Rocky Linux 8) | x86 (x86_64 / CPU 2) | [ERROR] [MY-013935] [Server] IO-layer timeout before wait_timeout was reached |
| 117644 | 2025-03-08 3:10 | 2025-03-12 14:30 | MySQL Server | Duplicate (227 days) | S2 | 8.0.37 | Any | Any | Lock contention due to FLUSH PRIVILEGES |
| 117527 | 2025-02-20 7:44 | 2025-02-20 12:23 | MySQL Server | Not a Bug (247 days) | S3 | 9.2.0, 9.1.0 | Ubuntu (22.04) | x86 | Left-join produce wrong result |
| 117487 | 2025-02-17 8:43 | 2025-02-25 12:01 | MySQL Server | Not a Bug (242 days) | S3 | 9.2.0 | Any (22.04) | Any | Serializable Isolation Violation (Write Skew) under Specific Concurrent Transactions |
| 117471 | 2025-02-14 13:25 | 2025-02-17 15:09 | MySQL Server | Not a Bug (250 days) | S3 | 8.4.4 | Any | Any | Documentation regarding the caching_sha2_password algorithm and testvectors is missing. |
| 117468 | 2025-02-14 12:43 | 2025-02-18 6:45 | MySQL Server | Not a Bug (249 days) | S3 | 8.4.4 | Windows (11) | x86 | Logical upgrade path: a dump containing 0000-00-00 should error when NO_ZERO_DATE is active |
| 117445 | 2025-02-12 3:44 | 2025-02-12 14:01 | MySQL Server | Unsupported (255 days) | S2 | 5.7.27 | Linux | x86 | mysql hang |
| 117421 | 2025-02-10 8:57 | 2025-02-12 0:29 | MySQL Server | Not a Bug (255 days) | S5 | 8.0.32 | Any | Any | Redundant row-level locking for using order DESC |
| 117418 | 2025-02-09 22:22 | 2025-02-10 13:35 | MySQL Server | Can't repeat (257 days) | S3 | 8.0.40 | Any | Any | MYSQL stopped running |
| 117404 | 2025-02-06 17:31 | 2025-03-08 1:00 | MySQL Server | No Feedback (232 days) | S2 | 8.0.40 | Any | Any | NotSupportedException: All objects in the EntitySet must have unique primary keys. |
| 117341 | 2025-01-30 14:16 | 2025-01-31 13:30 | MySQL Server | Closed (267 days) | S3 | >=8.4 | MacOS | ARM | Cannot drop index '<unknown key name>' when altering table in any way |
| 117311 | 2025-01-28 8:55 | 2025-01-28 20:43 | MySQL Server | Not a Bug (270 days) | S3 | 8.0.41 | Windows (Windows 11) | x86 | Offline keyring migration from plugin to component fails on Windows |
| 117212 | 2025-01-15 15:58 | 2025-01-15 17:00 | MySQL Server | Unsupported (283 days) | S3 | 5.5.30 | Windows (windows 11 enterprise) | Other (AMD Ryzen 5 PRO 5650U) | mysql-server-5.5-winx64's change state request failed. |
| 117137 | 2025-01-08 14:21 | 2025-01-09 16:27 | MySQL Server | Can't repeat (289 days) | S2 | 8.0.31 | Ubuntu | x86 | MySQL crashed due to assertion failure on block state |
| 117104 | 2025-01-03 13:30 | 2025-02-03 11:56 | MySQL Server | Not a Bug (265 days) | S3 | 8.4.3 | Ubuntu | x86 | MySQL 8.4 - High memory consumption |
| 117090 | 2025-01-01 14:05 | 2025-01-09 14:39 | MySQL Server | Can't repeat (289 days) | S3 | 8.0.40 | Any | x86 | mysqld got exception 0xc0000005 |
| 117054 | 2024-12-27 8:37 | 2025-01-09 14:51 | MySQL Server | Duplicate (289 days) | S3 | 8.0.20 8.0.40 | Any | Any | performance_schema tables are not accurate |
| 117038 | 2024-12-24 7:52 | 2024-12-27 8:47 | MySQL Server | Can't repeat (302 days) | S2 | 8.0.40 | Any (any) | Any (any) | i uninstalled old version of mysql and installed new version.this leads to this bug |
| 117037 | 2024-12-23 8:48 | 2025-02-11 12:25 | MySQL Server | Can't repeat (289 days) | S3 | 8.0 | Any | Any | index dive estimate wrong |
| 117034 | 2024-12-23 3:31 | 2025-01-09 11:34 | MySQL Server | Unsupported (289 days) | S3 | 5.7.26 | Any | Any | During testing of our production system, we discovered a potential issue with MySQL's Index Merge locking strategy. When |
| 117004 | 2024-12-18 6:29 | 2024-12-18 10:49 | MySQL Server | Unsupported (311 days) | S3 | 8.0.22 | Any | Any | mysql 8.0.22 query wrong results |
| 117002 | 2024-12-17 13:22 | 2024-12-17 13:30 | MySQL Server | Can't repeat (312 days) | S3 | 8.0.20 | Oracle Linux | Any | Mysql memory increasing without limits and restart every 2 days |
| 117000 | 2024-12-17 12:09 | 2024-12-17 12:15 | MySQL Server | Can't repeat (312 days) | S3 | 8.0CE | Windows | Any | in schema of employee in this when find other table then it's report bug |
| 116965 | 2024-12-13 8:33 | 2024-12-13 11:19 | MySQL Server | Can't repeat (316 days) | S3 | 8.0.18-baidu-rds-1.0.0.1 | Any | Any | ORDER BY count ASC LIMIT 0,20 在查询时缺少数据 |
| 116891 | 2024-12-06 7:56 | 2024-12-06 11:30 | MySQL Server | Duplicate (323 days) | S3 | 9.0 | Any | Any | Inconsistent Results Between Materialized Table and View with DAYNAME |
| 116864 | 2024-12-04 7:43 | 2025-01-05 1:00 | MySQL Server | No Feedback (294 days) | S3 | 8.0.35 | Any | Any | Index corruption |
| 116843 | 2024-12-02 14:25 | 2024-12-03 11:23 | MySQL Server | Not a Bug (326 days) | S3 | 8.4.1 | Red Hat (Linux 3.10.0-1160.102.1.el7.x86_64 ) | x86 (x86_64) | The logical error of the INET_NTOA function in the NOT IN operation. |
| 116796 | 2024-11-27 6:23 | 2024-11-29 10:31 | MySQL Server | Duplicate (331 days) | S5 | 8.0.32 | Any | Any | get_oldest_view cost too much and block other oprator |
| 116795 | 2024-11-27 5:02 | 2024-11-27 11:07 | MySQL Server | Closed (332 days) | S3 | 8.0.32 | Any | Any | get_oldest_view cost too much and block other oprator |
| 116787 | 2024-11-26 17:25 | 2024-11-26 19:01 | MySQL Server | Can't repeat (333 days) | S5 | Server version: 8.0.40-0ubuntu0.24.04.1 | Ubuntu | Any | erro en funciones mysql |
| 116717 | 2024-11-19 23:56 | 2024-11-20 11:08 | MySQL Server | Can't repeat (339 days) | S3 | Any | Any | after writing a code a got a bug notification | |
| 116705 | 2024-11-19 8:50 | 2024-11-19 18:02 | MySQL Server | Not a Bug (340 days) | S3 | Any | Any | MYSQL 8.0 add some reserved keyword which is not compatible | |
| 116667 | 2024-11-14 14:28 | 2024-11-15 10:48 | MySQL Server | Not a Bug (345 days) | S3 | 8.0.39 | Any | Any | New connection default collation_connection is inconsistent |
| 116634 | 2024-11-12 14:58 | 2024-11-13 10:39 | MySQL Server | Not a Bug (346 days) | S3 | 9.0 | Any | Any | Inconsistent Comparison Behavior with JSON and Boolean Expressions |
| 116582 | 2024-11-07 10:08 | 2024-11-07 10:26 | MySQL Server | Unsupported (352 days) | S3 | 8.0.24 | Linux | x86 (x86 or arm) | to_char+concat+to_date+time_format, time format conversion trigger crash |
| 116556 | 2024-11-05 11:04 | 2024-11-05 12:15 | MySQL Server | Not a Bug (354 days) | S3 | 9.0 | Any | Any | Inconsistent Results with IN Clause for Binary Data |
| 116552 | 2024-11-05 10:33 | 2024-11-05 11:46 | MySQL Server | Can't repeat (354 days) | S3 | 8.0.37 | CentOS | Any | InnoDB Deadlock and Assertion Failure Leading to MySQL Crash |
| 116539 | 2024-11-04 14:15 | 2024-11-06 11:07 | MySQL Server | Not a Bug (353 days) | S3 | 8.0, 8.4 | Red Hat (RHEL9) | x86 (Any) | MySQL 8.0/8.4 performs worse on RHEL9 than on RHEL8 |
| 116537 | 2024-11-04 13:40 | 2024-11-04 13:57 | MySQL Server | Can't repeat (355 days) | S3 | 8.0.36 | Ubuntu | x86 | mysqld crashing with signal 8 in Item_func_mul::real_op()+0x77 |
| 116525 | 2024-11-01 10:13 | 2024-11-05 10:10 | MySQL Server | Can't repeat (354 days) | S3 | Any | Any | basename_prefix_find may cause memory access to go out of bounds | |
| 116521 | 2024-11-01 1:37 | 2024-11-04 12:41 | MySQL Server | Can't repeat (355 days) | S3 | 9.0.1 | Ubuntu (22.04) | x86 | Write skew exception at serializable isolation level |
| 116503 | 2024-10-30 6:55 | 2024-10-31 14:25 | MySQL Server | Not a Bug (359 days) | S3 | 8.0 | Any | Any | duplicate-key error will hold gap lock when there are multi unique keys |
| Showing all 116 (Edit, Save, CSV, Feed) |
