Showing 1–30 of 65
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 121321 | 2026-09-19 18:59 | 2026-09-19 18:59 | MySQL Server: Memory storage engine | Open | S2 | 26.10.0 (trunk), 9.7.2 (LTS), 8.4.11 (LT | Any | Any | ERROR 1062 '<group_key>' on DISTINCT over a DOUBLE column containing both -0e0 and 0e0 |
| 120273 | 2026-04-15 15:39 | 2026-10-13 9:32 | MySQL Server: Memory storage engine | Duplicate (24 days) | S2 | 8.0.45 | Ubuntu (22.04) | x86 | Incorrect COUNT result when "SET SESSION internal_tmp_mem_storage_engine = MEMORY" is used |
| 119651 | 2026-01-09 2:19 | 2026-01-09 7:39 | MySQL Server: Memory storage engine | Unsupported (301 days) | S2 | 5.7 | Any | Any | A core dump occurred during heap scan. |
| 117455 | 2025-02-13 2:13 | 2025-02-13 6:30 | MySQL Server: Memory storage engine | Verified (631 days) | S2 | 8.4.1 9.1.0, 8.4.4, 8.0.41 | Windows (windows 11) | x86 (x86_64) | MEMORY engine CHAR type comparison results differ from expectations. |
| 107952 | 2022-07-23 8:31 | 2022-07-26 11:49 | MySQL Server: Memory storage engine | Unsupported (1564 days) | S3 | Any | Any | there is no need to core dump the memory that temptable engine mmap from disk | |
| 95964 | 2019-06-24 22:23 | 2020-03-30 15:38 | MySQL Server: Memory storage engine | Verified (2412 days) | S3 | 8.0.16, 5.7.26, 5.6.44 | Ubuntu | x86 | Compare that uses UNSIGNED cast and function malfunctions in the MEMORY engine |
| 95866 | 2019-06-18 21:47 | 2019-06-19 5:49 | MySQL Server: Memory storage engine | Verified (2697 days) | S3 | 8.0.16, 5.7.26 | Ubuntu | x86 | "Can't find record" error in SELECT statement |
| 94647 | 2019-03-14 4:45 | 2019-03-28 5:31 | MySQL Server: Memory storage engine | Not a Bug (2793 days) | S3 | 5.7 | Debian | Any | Memory leak in MEMORY table by glibc |
| 94646 | 2019-03-14 2:47 | 2019-03-15 2:12 | MySQL Server: Memory storage engine | Not a Bug (2793 days) | S3 | 5.7.23 & 8.0.13 | Linux | Any | An alteration of the system variable "max_heap_table_size" does not take effect? |
| 86516 | 2017-05-31 7:10 | 2017-07-05 11:16 | MySQL Server: Memory storage engine | Can't repeat (3411 days) | S3 | mysql-5.6.23 | CentOS (6.5) | Any | no begin/commit binlog event with memory engine table. |
| 85291 | 2017-03-03 11:41 | 2017-03-03 11:42 | MySQL Server: Memory storage engine | Verified | S3 | 5.1+ | Any | Any | missing break for case HA_EXTRA_RESET_STATE in function heap_extra |
| 81781 | 2016-06-08 20:40 | 2016-06-09 13:32 | MySQL Server: Memory storage engine | Duplicate (3802 days) | S3 | 5.6.30 | Ubuntu | Any | Memory table with massive compound b-tree primary key |
| 74198 | 2014-10-03 0:07 | 2014-10-12 17:45 | MySQL Server: Memory storage engine | Verified (4408 days) | S3 | 5.7.5 | Any | Any | Get full table scan after FORCE INDEX for HEAP |
| 73777 | 2014-08-31 11:00 | 2015-08-24 13:24 | MySQL Server: Memory storage engine | Verified (4449 days) | S3 | 5.6, 5.6.21, 5.5.40 | Linux | Any | DELETE query takes a long time and examines more rows than exist in the table |
| 71559 | 2014-02-02 12:29 | 2014-02-02 13:27 | MySQL Server: Memory storage engine | Verified | S3 | 5.0.96 | Windows | Any | Max_data_length has integer overflow on some memory tables |
| 71545 | 2014-01-31 16:22 | 2014-08-25 1:00 | MySQL Server: Memory storage engine | No Feedback (4457 days) | S1 | 5.5.35 | Linux (Ubuntu 12.04 LTS) | Any | High max_heap_table_size causes mysql to crash |
| 69831 | 2013-07-24 16:50 | 2015-03-10 15:43 | MySQL Server: Memory storage engine | Won't fix (4259 days) | S3 | 5.5 | Any | Any | Replication fails on updating a MEMORY table with an index using btree |
| 69301 | 2013-05-22 9:19 | 2013-06-25 8:07 | MySQL Server: Memory storage engine | Can't repeat (4882 days) | S5 | mysql-enterprise-5.0.66a-win32 | Windows | Any | MySQL does not free memory when Application stops executing queries. |
| 69075 | 2013-04-26 3:07 | 2014-02-19 10:39 | MySQL Server: Memory storage engine | Duplicate (4643 days) | S3 | 5.6.11, 5.6.15 | Any | Any | Memory leak slave_parallel_workers |
| 69066 | 2013-04-25 9:38 | 2013-05-07 18:11 | MySQL Server: Memory storage engine | Duplicate (4931 days) | S3 | 5.6.11 | Any | Any | Memory leak slave_parallel_workers |
| 68086 | 2013-01-15 8:41 | 2013-01-15 19:28 | MySQL Server: Memory storage engine | Verified (5043 days) | S3 | 5.5.29, 5.5.30, 5.7.1 | Any | Any | Heap tables don't use index for group by |
| 67978 | 2012-12-27 6:13 | 2026-10-26 21:48 | MySQL Server: Memory storage engine | Documenting (5060 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Signed zero is handled incorrectly by HASH indexes and GROUP BY |
| 64940 | 2012-04-11 9:25 | 2012-04-11 12:25 | MySQL Server: Memory storage engine | Closed (5322 days) | S2 | 5.5.19 | Windows (2003 server (32bit)) | Any | Memory table no longer falls back to MyISAM when full |
| 62548 | 2011-09-27 10:22 | 2015-05-16 14:26 | MySQL Server: Memory storage engine | Verified (5519 days) | S2 | 5.1.49, 5.1.58 | Linux (Ubuntu) | Any | Different result from memory and myisam table |
| 61238 | 2011-05-20 4:17 | 2011-05-25 10:19 | MySQL Server: Memory storage engine | Verified (5649 days) | S3 | 5.1.58, 5.5 | MacOS | Any | Hash indexes with a prefix length do not work |
| 57725 | 2010-10-26 4:20 | 2010-11-11 0:13 | MySQL Server: Memory storage engine | Not a Bug (5839 days) | S2 | 5.1.51 | Any | Any | Memory Storage Engine not to keep the auto_increment value of table option |
| 55559 | 2010-07-26 14:15 | 2013-03-03 20:45 | MySQL Server: Memory storage engine | Duplicate (5946 days) | S2 | 5.1, trunk | Any | Any | MAX_HEAP_TABLE_SIZE does not work as specified |
| 53723 | 2010-05-18 0:44 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | Closed (6015 days) | S2 | 5.1.40 | MacOS (10.6.3 Server & Client) | Any | MEMORY table rows randomly disappear |
| 52924 | 2010-04-18 4:26 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | Can't repeat (5950 days) | S2 | 5.0.18 | Any | Any | Memory leak in MySQL version 5.0.18 |
| 51763 | 2010-03-05 10:11 | 2012-12-10 19:07 | MySQL Server: Memory storage engine | Closed (5079 days) | S2 | 5.1.31, 5.1.32, 5.1.37-2-log, 5.1.43, 5.1.45-bzr, 5.5.26 | Linux (Debian, Fedora) | Any | Can't delete rows from MEMORY table with HASH key |
Showing 1–30 of 65
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.008 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.