Showing 1-10 of 356 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
104499 | 2021-07-31 20:35 | 2021-08-27 12:02 | MySQL Server: InnoDB storage engine | Verified (1418 days) | S3 | Any | Any | MySQL auto_inc value changed after a failed insert | |
117809 | 2025-03-27 13:06 | 2025-03-27 20:10 | MySQL Server: Optimizer | Verified (109 days) | S5 | Any | Any | Statistics update failed. | |
56694 | 2010-09-09 15:28 | 2011-02-16 23:44 | MySQL Server | Verified (5411 days) | S3 | Any | Any | mysql.server + large amounts of memory = cannot allocate error | |
111470 | 2023-06-17 13:06 | 2023-06-19 8:50 | MySQL Server: Japanese Documentation | Verified (758 days) | S3 | Any | Any | Mistranslation in 13.7.7.15 SHOW ENGINE ステートメント | |
79477 | 2015-12-01 10:36 | 2016-12-02 14:53 | MySQL Server: InnoDB storage engine | Verified (3146 days) | S3 | Any | Any | Remove sync_arr_wake_threads_if_sema_free hack | |
50225 | 2010-01-11 10:57 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5660 days) | S3 | Any | Any | rpl_backup_shutdown reveals memory issue in backup code | |
53460 | 2010-05-06 8:52 | 2022-12-04 20:45 | MySQL Server: Errors | Verified | S3 | Any | Any | ER_SET_CONSTANTS_ONLY is inaccurate | |
41440 | 2008-12-12 16:00 | 2022-12-04 20:45 | MySQL Server: Errors | Verified (6055 days) | S3 | 4.1.22, 5.1.30, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | Out of memory error "It is possible that mysqld could use" incorrect size |
103318 | 2021-04-14 13:46 | 2025-05-30 9:30 | MySQL Server: Data Types | Verified (1519 days) | S2 | 8.0 | Any | Any | Out of sort memory, consider increasing server sort buffer size for JSON Columns |
56620 | 2010-09-07 15:00 | 2012-05-18 19:36 | MySQL Proxy: Core | Verified (5423 days) | S3 | 0.8.1 | Any | Any | Memory leak near network_mysqld_auth_response_copy |
Showing 1-10 of 356 (Edit, Save, CSV, Feed) | Show Next 10 Entries » |