| Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 109260 | 2022-12-01 12:20 | 2023-01-03 12:51 | MySQL Server: InnoDB storage engine | Can't repeat (78 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
| 107806 | 2022-07-08 3:22 | 2022-08-12 11:40 | MySQL Server: InnoDB storage engine | Can't repeat (222 days) | S5 | 8.0.19 | Any | Any | AIO systerm optimize |
| 110216 | 2023-02-27 6:04 | 2023-03-03 22:49 | MySQL Server: Compiling | Closed (19 days) | S3 | 8.0.32 | Debian | Any | failed to compile in static mode |
| 106952 | 2022-04-08 6:01 | 2022-08-16 18:25 | MySQL Server: InnoDB storage engine | Closed (218 days) | S3 | 8.0.28 | Any | Any | it is better to clear upd_t in trx_undo_prev_version_build |
| 109981 | 2023-02-08 9:15 | 2023-03-10 13:29 | MySQL Server: InnoDB storage engine | Not a Bug (12 days) | S5 | 8.0.31 | Any | Any | optimize for innodb recovery |
| 110218 | 2023-02-27 6:30 | 2023-03-01 9:37 | MySQL Server: mysqlpump Command-line Client | Not a Bug (21 days) | S3 | 8.0.32 | Debian | Any | can not link jemalloc or tcmalloc in debian 11.5 |
| 109012 | 2022-11-05 14:13 | 2022-11-07 13:26 | MySQL Server: InnoDB storage engine | Not a Bug (135 days) | S5 | 8.0.31 | Any | Any | it is better to delete the recv_addr_t::space_id to save some memory |
| 108218 | 2022-08-22 9:39 | 2022-08-22 13:07 | MySQL Server: InnoDB storage engine | Not a Bug (212 days) | S5 | 8.0.30 | Any | Any | optimize for code |
| 107807 | 2022-07-08 4:39 | 2022-08-12 11:39 | MySQL Server: InnoDB storage engine | Not a Bug (222 days) | S5 | 8.0.19 | Any | Any | transaction rollback optimize |
| 107892 | 2022-07-15 8:41 | 2022-07-15 13:03 | MySQL Server: InnoDB storage engine | Not a Bug (250 days) | S3 | 8.0.29 | Any | Any | optimize for innodb recovery |
| 107857 | 2022-07-13 6:58 | 2022-07-13 12:18 | MySQL Server: InnoDB storage engine | Not a Bug (252 days) | S5 | 8.0.19 | Any | Any | only one LOG_CHECKPOINT block needed |
| 107827 | 2022-07-11 3:28 | 2022-07-11 12:09 | MySQL Server: InnoDB storage engine | Not a Bug (254 days) | S5 | 8.0.19 | Any | Any | optimize for simulated-AIO |
| 107288 | 2022-05-13 11:27 | 2022-05-16 12:24 | MySQL Server | Not a Bug (310 days) | S3 | 8.0.29 | Any | Any | mysqld crash when innodb_log_recent_written_size were incorrectly configured |
| 107231 | 2022-05-06 14:27 | 2022-05-11 2:51 | MySQL Server: InnoDB storage engine | Not a Bug (315 days) | S5 | 8.0.19 | Any | Any | for rollback transactions, it is better to set del_marks to false |
| 104787 | 2021-09-01 8:57 | 2021-09-03 11:45 | MySQL Server: InnoDB storage engine | Not a Bug (565 days) | S3 | Any | Any | need wait buf_fix_count =0 in buf_read_page_handle_error | |
| 110217 | 2023-02-27 6:16 | 2023-02-28 17:01 | MySQL Server: Compiling | Verified (22 days) | S3 | 8.0.32 | Debian | Any | failed to compile in mysql_release mode |
| 110091 | 2023-02-16 5:27 | 2023-02-20 13:58 | MySQL Server: InnoDB storage engine | Verified (30 days) | S5 | 8.0.32 | Any | Any | optimize for innodb recovery |
| 110078 | 2023-02-15 11:52 | 2023-02-15 12:39 | MySQL Server: InnoDB storage engine | Verified (35 days) | S5 | 8.0.32 | Any | Any | optimize for innodb recovery |
| 110068 | 2023-02-15 5:13 | 2023-02-15 6:05 | MySQL Server: InnoDB storage engine | Verified (35 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 (49 days) | S5 | 8.0.32 | Any | Any | no need to maintain err in buf_page_init_for_read |
| 108986 | 2022-11-03 13:13 | 2022-11-04 5:51 | MySQL Server: InnoDB storage engine | Verified (139 days) | S5 | 8.0.31 | Any | Any | no need to define mem_log_recv_page_hash_key in log0recv.cc |
| 108731 | 2022-10-11 5:07 | 2022-10-11 5:37 | MySQL Server: InnoDB storage engine | Verified (162 days) | S5 | 8.0.30 | Any | Any | just need to maintain FIL_PAGE_LSN once during recvory |
| 107900 | 2022-07-18 7:07 | 2022-07-18 12:44 | MySQL Server: InnoDB storage engine | Verified (247 days) | S5 | 8.0 | Any | Any | InnoDB crash recovery optimize |
| 106941 | 2022-04-07 9:21 | 2022-04-07 10:11 | MySQL Server: InnoDB storage engine | Verified (349 days) | S5 | 8.0.28 | Any | Any | apply_batch_on looks like redundant variables |
| 106768 | 2022-03-18 7:40 | 2022-03-18 10:11 | MySQL Server: InnoDB storage engine | Verified (369 days) | S5 | 8.0.19 | Any | Any | dummy index optimize: it is better to reuse the index object |
| 106755 | 2022-03-17 7:35 | 2022-03-17 8:27 | MySQL Server: InnoDB storage engine | Verified (370 days) | S4 | 8.0.19 | Any | Any | add feature:kill thread all |
| 106756 | 2022-03-17 8:31 | 2022-03-17 9:17 | MySQL Server: InnoDB storage engine | Verified (370 days) | S5 | 8.0.28 | Any | Any | it is better to change recv_sys->n_addrs to atomic |
| 106720 | 2022-03-13 13:55 | 2022-03-14 5:37 | MySQL Server: InnoDB storage engine | Verified (373 days) | S5 | 8.0.26 | Any | Any | it is better to make a conditional judgment before entering the while loop |
| 106249 | 2022-01-23 3:58 | 2022-01-23 9:54 | MySQL Server: InnoDB storage engine | Verified (423 days) | S5 | 8.0 | Any | Any | it is better to use trx_undo_get_next_rec_from_next_page |
| 106233 | 2022-01-21 8:57 | 2022-01-21 9:47 | MySQL Server: InnoDB storage engine | Verified (425 days) | S5 | 8.0.28 | Any | Any | it is better to create TrxUndoRsegs after the if judgment |
| Showing 1-30 of 41 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
