Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
110218 | 2023-02-27 6:30 | 2023-03-01 9:37 | MySQL Server: mysqlpump Command-line Client | Not a Bug (29 days) | S3 | 8.0.32 | Debian | Any | can not link jemalloc or tcmalloc in debian 11.5 |
107288 | 2022-05-13 11:27 | 2022-05-16 12:24 | MySQL Server | Not a Bug (318 days) | S3 | 8.0.29 | Any | Any | mysqld crash when innodb_log_recent_written_size were incorrectly configured |
110216 | 2023-02-27 6:04 | 2023-03-03 22:49 | MySQL Server: Compiling | Closed (27 days) | S3 | 8.0.32 | Debian | Any | failed to compile in static mode |
110217 | 2023-02-27 6:16 | 2023-02-28 17:01 | MySQL Server: Compiling | Verified (30 days) | S3 | 8.0.32 | Debian | Any | failed to compile in mysql_release mode |
107231 | 2022-05-06 14:27 | 2022-05-11 2:51 | MySQL Server: InnoDB storage engine | Not a Bug (323 days) | S5 | 8.0.19 | Any | Any | for rollback transactions, it is better to set del_marks to false |
107806 | 2022-07-08 3:22 | 2022-08-12 11:40 | MySQL Server: InnoDB storage engine | Can't repeat (230 days) | S5 | 8.0.19 | Any | Any | AIO systerm optimize |
107807 | 2022-07-08 4:39 | 2022-08-12 11:39 | MySQL Server: InnoDB storage engine | Not a Bug (230 days) | S5 | 8.0.19 | Any | Any | transaction rollback optimize |
107827 | 2022-07-11 3:28 | 2022-07-11 12:09 | MySQL Server: InnoDB storage engine | Not a Bug (262 days) | S5 | 8.0.19 | Any | Any | optimize for simulated-AIO |
107857 | 2022-07-13 6:58 | 2022-07-13 12:18 | MySQL Server: InnoDB storage engine | Not a Bug (260 days) | S5 | 8.0.19 | Any | Any | only one LOG_CHECKPOINT block needed |
107892 | 2022-07-15 8:41 | 2022-07-15 13:03 | MySQL Server: InnoDB storage engine | Not a Bug (258 days) | S3 | 8.0.29 | Any | Any | optimize for innodb recovery |
107900 | 2022-07-18 7:07 | 2022-07-18 12:44 | MySQL Server: InnoDB storage engine | Verified (255 days) | S5 | 8.0 | Any | Any | InnoDB crash recovery optimize |
108218 | 2022-08-22 9:39 | 2022-08-22 13:07 | MySQL Server: InnoDB storage engine | Not a Bug (220 days) | S5 | 8.0.30 | Any | Any | optimize for code |
108731 | 2022-10-11 5:07 | 2022-10-11 5:37 | MySQL Server: InnoDB storage engine | Verified (170 days) | S5 | 8.0.30 | Any | Any | just need to maintain FIL_PAGE_LSN once during recvory |
108986 | 2022-11-03 13:13 | 2022-11-04 5:51 | MySQL Server: InnoDB storage engine | Verified (147 days) | S5 | 8.0.31 | Any | Any | no need to define mem_log_recv_page_hash_key in log0recv.cc |
109012 | 2022-11-05 14:13 | 2022-11-07 13:26 | MySQL Server: InnoDB storage engine | Not a Bug (143 days) | S5 | 8.0.31 | Any | Any | it is better to delete the recv_addr_t::space_id to save some memory |
109260 | 2022-12-01 12:20 | 2023-01-03 12:51 | MySQL Server: InnoDB storage engine | Can't repeat (86 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
109873 | 2023-02-01 12:01 | 2023-02-01 12:35 | MySQL Server: InnoDB storage engine | Verified (57 days) | S5 | 8.0.32 | Any | Any | no need to maintain err in buf_page_init_for_read |
109981 | 2023-02-08 9:15 | 2023-03-10 13:29 | MySQL Server: InnoDB storage engine | Not a Bug (20 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
110068 | 2023-02-15 5:13 | 2023-02-15 6:05 | MySQL Server: InnoDB storage engine | Verified (43 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
110078 | 2023-02-15 11:52 | 2023-02-15 12:39 | MySQL Server: InnoDB storage engine | Verified (43 days) | S5 | 8.0.32 | Any | Any | optimize for innodb recovery |
110091 | 2023-02-16 5:27 | 2023-02-20 13:58 | MySQL Server: InnoDB storage engine | Verified (38 days) | S5 | 8.0.32 | Any | Any | optimize for innodb recovery |
106952 | 2022-04-08 6:01 | 2022-08-16 18:25 | MySQL Server: InnoDB storage engine | Closed (226 days) | S3 | 8.0.28 | Any | Any | it is better to clear upd_t in trx_undo_prev_version_build |
104594 | 2021-08-11 10:54 | 2022-04-27 13:22 | MySQL Server: InnoDB storage engine | Verified (595 days) | S5 | 8.0 | Any | Any | no need to maintain young and old area of LRU list |
104630 | 2021-08-16 3:47 | 2021-08-17 14:26 | MySQL Server: InnoDB storage engine | Verified (590 days) | S5 | 8.0 | Any | Any | no need to make two conditional judgments |
104779 | 2021-08-31 9:38 | 2021-08-31 10:02 | MySQL Server: InnoDB storage engine | Verified (576 days) | S5 | 8.0.19 | Any | Any | no need to own sx-latch during the period of page flusing for BUF_FLUSH_LRU |
104787 | 2021-09-01 8:57 | 2021-09-03 11:45 | MySQL Server: InnoDB storage engine | Not a Bug (573 days) | S3 | Any | Any | need wait buf_fix_count =0 in buf_read_page_handle_error | |
105028 | 2021-09-24 4:45 | 2021-09-24 5:29 | MySQL Server: InnoDB storage engine | Verified (552 days) | S3 | 8.0.26 | Any | Any | memory leak caused by recv_sys->saved_recs during recovery |
105043 | 2021-09-26 14:32 | 2021-09-27 12:56 | MySQL Server: InnoDB storage engine | Verified (549 days) | S5 | 8.0 | Any | Any | no need to maintain max_size for some scenarios in btr_insert_into_right_sibling |
105044 | 2021-09-26 15:32 | 2021-09-27 12:59 | MySQL Server: InnoDB storage engine | Verified (549 days) | S5 | 8.0 | Any | Any | Added page szie judgment logic like btr_cur_optimistic_insert in btr_insert_into |
105245 | 2021-10-18 6:41 | 2021-10-18 7:43 | MySQL Server: InnoDB storage engine | Verified (528 days) | S5 | 8.0.26 | Any | Any | no need to create recv_sys when mysqld initialize |
Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |