| Showing 1-30 of 250 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 113768 | 2024-01-26 2:40 | 2024-01-26 8:53 | MySQL Server: DML | Verified (90 days) | S3 | 8.0.35 | Linux | Any | return error with cast |
| 113769 | 2024-01-26 2:42 | 2024-03-01 1:00 | MySQL Server: Replication | No Feedback (56 days) | S3 | 5.7.44 | Any | Any | Generated column json binary format is incorrent |
| 113771 | 2024-01-26 7:35 | 2024-01-26 12:19 | MySQL Server: InnoDB storage engine | Verified (90 days) | S3 | 8.0.32 | Any | Any | optimize for row_parse_int_from_field |
| 113776 | 2024-01-26 12:20 | 2024-01-26 13:26 | MySQL Server: InnoDB storage engine | Verified (90 days) | S5 | 8.0.32 | Any | Any | optimize for btr_insert_into_right_sibling |
| 113777 | 2024-01-26 14:24 | 2024-02-02 15:52 | MySQL Server: Security: Encryption | Not a Bug (83 days) | S3 | 8.0.36 | Windows | Any | Replication with SSL certificates fails after upgrade to MySQL 8 |
| 113778 | 2024-01-26 15:40 | 2024-01-29 13:45 | MySQL Server: XML functions | Verified (87 days) | S3 | 8.0 | Any | Any | Encoding problem in xpath comparision |
| 113783 | 2024-01-28 12:50 | 2024-01-30 10:58 | MySQL Server: Optimizer | Not a Bug (86 days) | S4 | 8.0 | Any | Any | only_full_group_by option does not take effect |
| 113789 | 2024-01-29 9:35 | 2024-01-30 13:38 | MySQL Server: Information schema | Verified (87 days) | S3 | 8.0 | Any | Any | information_schema tables not accessible via Table Access Service |
| 113811 | 2024-01-30 23:42 | 2024-02-01 11:35 | MySQL Server: FULLTEXT search | Not a Bug (84 days) | S3 | 8.0.27 5.7.28 | Any | Any | Get incorrect result when searching for consecutive uppercase letters |
| 113813 | 2024-01-31 2:26 | 2024-02-07 8:24 | MySQL Server: Replication | Verified (85 days) | S3 | MySQL8.0,8.0.36 | Any | Any | Semisync will abort due to wrong transaction binlog postion comparison |
| 113814 | 2024-01-31 2:42 | 2024-01-31 13:16 | MySQL Server: Replication | Verified (85 days) | S3 | MySQL8.0,5.7 | Any | Any | The Rpl_semi_sync_master_yes_tx and Rpl_semi_sync_master_no_tx are inaccurate |
| 113815 | 2024-01-31 3:35 | 2024-01-31 12:22 | MySQL Server: InnoDB storage engine | Verified (85 days) | S3 | 8.0 | Any | Any | MySQL auto increment ID will skip 4294967294 |
| 113818 | 2024-01-31 7:04 | 2024-01-31 7:20 | MySQL Server: InnoDB storage engine | Verified (85 days) | S5 | 8.0.32 | Any | Any | optimize for buf_read_page_low |
| 113819 | 2024-01-31 7:20 | 2024-02-09 19:57 | MySQL Server: InnoDB storage engine | Closed (76 days) | S3 | 8.0.34, 8.0.33 | Linux (CentOS Linux release 7.6.1810 (Core) ) | Any | when use show engine innodb cannot show correct information |
| 113831 | 2024-01-31 11:28 | 2024-01-31 13:17 | MySQL Server: Command-line Clients | Can't repeat (85 days) | S3 | 8.0.35 | Windows (windows server 2016) | Any | mysql crashes ramdonally during backup |
| 113842 | 2024-02-01 2:12 | 2024-02-01 23:38 | MySQL Server: Documentation | Closed (84 days) | S3 | 8.0 | Any | Any | COMPACT Row Format Section seems have clerical error |
| 113843 | 2024-02-01 2:49 | 2024-02-01 8:09 | MySQL Server: Prepared statements | Verified (84 days) | S3 | 8.0.32, 8.0.36 | Any | Any | prepared json query can not use index |
| 113844 | 2024-02-01 3:30 | 2024-02-02 11:15 | MySQL Server | Can't repeat (83 days) | S5 | 8.0.16 | Ubuntu | Any | The execution time of queries and written statements took a long time |
| 113846 | 2024-02-01 8:11 | 2024-04-02 10:16 | MySQL Server: FULLTEXT search | Verified (83 days) | S3 | 8.0 | Any | Any | Fulltext Index has Missing Rows If They are from Concurrent Inserts |
| 113849 | 2024-02-01 10:50 | 2024-02-09 7:29 | MySQL Server: DML | Not a Bug (76 days) | S3 | 8.0 | Any | Any | Incorrect results when case ... when used in update statement |
| 113851 | 2024-02-01 12:13 | 2024-02-19 12:38 | MySQL Server: DML | Not a Bug (67 days) | S3 | 8.3.0 | Any | Any | float type data query error |
| 113862 | 2024-02-02 6:22 | 2024-02-02 12:11 | MySQL Server: InnoDB storage engine | Can't repeat (83 days) | S3 | Any | Any | problem with btree latch acquisition when updating histogram | |
| 113863 | 2024-02-02 8:16 | 2024-02-02 12:16 | MySQL Server | Unsupported (83 days) | S3 | 5.7.42-0ubuntu0.18.04.1 | Ubuntu (18.04.1) | Any | Assertion failure in thread 139984153384704 in file fsp0fsp.cc line 3976 |
| 113864 | 2024-02-02 9:41 | 2024-02-05 11:42 | MySQL Server: Charsets | Not a Bug (81 days) | S3 | 8.0.36 | Any (rhel-7.4) | Any (x86-64) | select statements with convert function report error for specified usage |
| 113868 | 2024-02-02 12:03 | 2024-02-05 13:03 | MySQL Server: Optimizer | Verified (80 days) | S4 | 8.0 | Any | Any | Unreasonable warning "Cannot use range access on index" |
| 113879 | 2024-02-03 10:26 | 2024-02-06 12:09 | MySQL Server: DML | Not a Bug (80 days) | S3 | 8.0.35 | Any | Any | An error is reported when the user variable character set is used in the stored |
| 113887 | 2024-02-04 2:12 | 2024-02-05 13:07 | MySQL Server: Parser | Verified (80 days) | S3 | 8.0 | Any | Any | MySQL fails to execute query if a subquery refer to a column of parent table |
| 113889 | 2024-02-04 6:17 | 2024-02-05 11:08 | MySQL Server: Locking | Can't repeat (80 days) | S3 | Any | Any | Lock is not released when thread is killed | |
| 113891 | 2024-02-05 3:23 | 2024-02-28 22:42 | MySQL Server: InnoDB storage engine | Verified (80 days) | S3 | 8.0.36 | Any | Any | The value range of innodb_io_capacity_max is changed. |
| 113892 | 2024-02-05 10:39 | 2024-02-05 14:13 | MySQL Server: Optimizer | Verified (80 days) | S3 | 8.0 | Any | Any | FORCE INDEX reports wrong number of rows |
| Showing 1-30 of 250 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
