| Showing 1-30 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 68086 | 2013-01-15 8:41 | 2013-01-15 19:28 | MySQL Server: Memory storage engine | Verified (4112 days) | S3 | 5.5.29, 5.5.30, 5.7.1 | Any | Any | Heap tables don't use index for group by |
| 9719 | 2005-04-07 14:00 | 2006-08-04 3:41 | MySQL Server: Memory storage engine | Closed (6468 days) | S3 | 4.1.11 (RPM) | Any (*) | Any | DELETE with WHERE on HEAP table just deletes first row of matched set |
| 44771 | 2009-05-11 2:27 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | Closed (4874 days) | S2 | 5.1.34, 4.1, 5.0, 5.1, 6.0 bzr | Any | Any | Unique Hash index in memory engine will give wrong query result for NULL value |
| 45137 | 2009-05-27 15:24 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | No Feedback (5410 days) | S2 | 5.1.32 | Solaris | Any | unable to limit total memory consumption |
| 47704 | 2009-09-29 9:13 | 2012-03-06 1:23 | MySQL Server: Memory storage engine | Closed (4427 days) | S2 | 5.0.86, 5.1.39 | Linux | Any | hash index on VARCHAR prefix not working correctly |
| 48196 | 2009-10-21 3:47 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | No Feedback (5263 days) | S3 | 5.0.84 | Linux (SUSE SLES10.2) | Any | Got error 134 when reading table(ENGINE=MEMORY) |
| 51763 | 2010-03-05 10:11 | 2012-12-10 19:07 | MySQL Server: Memory storage engine | Closed (4148 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 |
| 52924 | 2010-04-18 4:26 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | Can't repeat (5019 days) | S2 | 5.0.18 | Any | Any | Memory leak in MySQL version 5.0.18 |
| 53723 | 2010-05-18 0:44 | 2011-02-16 23:44 | MySQL Server: Memory storage engine | Closed (5084 days) | S2 | 5.1.40 | MacOS (10.6.3 Server & Client) | Any | MEMORY table rows randomly disappear |
| 55559 | 2010-07-26 14:15 | 2013-03-03 20:45 | MySQL Server: Memory storage engine | Duplicate (5015 days) | S2 | 5.1, trunk | Any | Any | MAX_HEAP_TABLE_SIZE does not work as specified |
| 57725 | 2010-10-26 4:20 | 2010-11-11 0:13 | MySQL Server: Memory storage engine | Not a Bug (4908 days) | S2 | 5.1.51 | Any | Any | Memory Storage Engine not to keep the auto_increment value of table option |
| 61238 | 2011-05-20 4:17 | 2011-05-25 10:19 | MySQL Server: Memory storage engine | Verified (4718 days) | S3 | 5.1.58, 5.5 | MacOS | Any | Hash indexes with a prefix length do not work |
| 62548 | 2011-09-27 10:22 | 2015-05-16 14:26 | MySQL Server: Memory storage engine | Verified (4588 days) | S2 | 5.1.49, 5.1.58 | Linux (Ubuntu) | Any | Different result from memory and myisam table |
| 64940 | 2012-04-11 9:25 | 2012-04-11 12:25 | MySQL Server: Memory storage engine | Closed (4391 days) | S2 | 5.5.19 | Windows (2003 server (32bit)) | Any | Memory table no longer falls back to MyISAM when full |
| 67978 | 2012-12-27 6:13 | 2012-12-29 16:21 | MySQL Server: Memory storage engine | Verified (4129 days) | S3 | 5.1, 5.5, 5.6 | Any | Any | Signed zero is handled incorrectly by HASH indexes and GROUP BY |
| 44138 | 2009-04-07 22:48 | 2016-06-09 7:33 | MySQL Server: Memory storage engine | Verified (3794 days) | S2 | 5.1.57, 5.6.14, 5.6.30 | Linux (x86_64 rhel5 version from download page) | Any | Memory engine table full at much less than max_heap_table_size with btree index |
| 69066 | 2013-04-25 9:38 | 2013-05-07 18:11 | MySQL Server: Memory storage engine | Duplicate (4000 days) | S3 | 5.6.11 | Any | Any | Memory leak slave_parallel_workers |
| 69075 | 2013-04-26 3:07 | 2014-02-19 10:39 | MySQL Server: Memory storage engine | Duplicate (3712 days) | S3 | 5.6.11, 5.6.15 | Any | Any | Memory leak slave_parallel_workers |
| 69301 | 2013-05-22 9:19 | 2013-06-25 8:07 | MySQL Server: Memory storage engine | Can't repeat (3951 days) | S5 | mysql-enterprise-5.0.66a-win32 | Windows | Any | MySQL does not free memory when Application stops executing queries. |
| 69831 | 2013-07-24 16:50 | 2015-03-10 15:43 | MySQL Server: Memory storage engine | Won't fix (3328 days) | S3 | 5.5 | Any | Any | Replication fails on updating a MEMORY table with an index using btree |
| 71545 | 2014-01-31 16:22 | 2014-08-25 1:00 | MySQL Server: Memory storage engine | No Feedback (3526 days) | S1 | 5.5.35 | Linux (Ubuntu 12.04 LTS) | Any | High max_heap_table_size causes mysql to crash |
| 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 |
| 73777 | 2014-08-31 11:00 | 2015-08-24 13:24 | MySQL Server: Memory storage engine | Verified (3518 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 |
| 74198 | 2014-10-03 0:07 | 2014-10-12 17:45 | MySQL Server: Memory storage engine | Verified (3477 days) | S3 | 5.7.5 | Any | Any | Get full table scan after FORCE INDEX for HEAP |
| 81781 | 2016-06-08 20:40 | 2016-06-09 13:32 | MySQL Server: Memory storage engine | Duplicate (2871 days) | S3 | 5.6.30 | Ubuntu | Any | Memory table with massive compound b-tree primary key |
| 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 |
| 86516 | 2017-05-31 7:10 | 2017-07-05 11:16 | MySQL Server: Memory storage engine | Can't repeat (2480 days) | S3 | mysql-5.6.23 | CentOS (6.5) | Any | no begin/commit binlog event with memory engine table. |
| 94646 | 2019-03-14 2:47 | 2019-03-15 2:12 | MySQL Server: Memory storage engine | Not a Bug (1862 days) | S3 | 5.7.23 & 8.0.13 | Linux | Any | An alteration of the system variable "max_heap_table_size" does not take effect? |
| 94647 | 2019-03-14 4:45 | 2019-03-28 5:31 | MySQL Server: Memory storage engine | Not a Bug (1862 days) | S3 | 5.7 | Debian | Any | Memory leak in MEMORY table by glibc |
| 107952 | 2022-07-23 8:31 | 2022-07-26 11:49 | MySQL Server: Memory storage engine | Unsupported (633 days) | S3 | Any | Any | there is no need to core dump the memory that temptable engine mmap from disk |
| Showing 1-30 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
