| Showing 1-30 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 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. |
| 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. |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 39918 | 2008-10-07 22:59 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | Closed (5412 days) | S2 | 5.0.67, 5.1.30-bzr | Any | Any | memory (heap) engine crashing with b-tree index and DELETE with seg fault |
| 39886 | 2008-10-06 15:12 | 2011-02-16 23:43 | MySQL Server: Memory storage engine | Closed (5552 days) | S3 | 5.0,5.1 | Any | Any | Table full for MEMORY table is not written into error log |
| 30885 | 2007-09-07 7:17 | 2007-10-24 20:03 | MySQL Server: Memory storage engine | Closed (6022 days) | S2 | 5.0.50-bk | Any | Any | MEMORY returns incorrect data if BTREE index is used for NULL lookup |
| 30590 | 2007-08-23 10:26 | 2010-05-12 10:44 | MySQL Server: Memory storage engine | Closed (6024 days) | S1 | 5.0.48,5.1.22 | Any | Any | delete from memory table with composite btree primary key |
| 24985 | 2006-12-12 0:21 | 2007-04-05 19:42 | MySQL Server: Memory storage engine | Closed (6224 days) | S3 | 5.0.27/4.1BK/5.0BK/5.1BK | Windows (Windows 2K/Linux) | Any | UTF8 ENUM primary key on MEMORY using BTREE causes incorrect duplicate entries |
| 26996 | 2007-03-09 12:44 | 2007-03-31 23:11 | MySQL Server: Memory storage engine | Closed (6229 days) | S1 | 5.0.38-BK, 5.0.27 | Linux (Linux) | Any | Update of a Field in a Memory Table ends with wrong result |
| 26080 | 2007-02-05 12:34 | 2007-03-15 13:23 | MySQL Server: Memory storage engine | Closed (6245 days) | S2 | MySQL Server: 5.1.14-beta-community-nt-l | Windows (Windows XP Home Edition, Linux) | Any | Memory Storage engine not working properly |
| 24052 | 2006-11-07 17:25 | 2006-12-18 18:56 | MySQL Server: Memory storage engine | Closed (6332 days) | S1 | 5.0.27/4.1:/5.1 | Windows (Windows 64) | Any | On Win64, MEMORY tables are limited to 4 GB |
| 23764 | 2006-10-30 10:16 | 2006-11-28 12:28 | MySQL Server: Memory storage engine | Closed (6352 days) | S2 | 5.0.26 5.0.27 | Linux (FC5) | Any | BTREE index deletes only 1 item on memory table |
| 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 |
| 12873 | 2005-08-30 10:30 | 2006-06-05 21:43 | MySQL Server: Memory storage engine | Closed (6528 days) | S3 | 4.1.14/5.0 | Linux (linux) | Any | BTREE index on MEMORY table with multiple NULL values doesn't work properly |
| 18160 | 2006-03-12 1:22 | 2006-06-03 13:35 | MySQL Server: Memory storage engine | Closed (6530 days) | S3 | 5.0.18, 4.1,x, 4.0.x | Linux (Debian Linux) | Any | Memory-/HEAP Table endless growing indexes |
| 18233 | 2006-03-14 17:26 | 2006-05-24 18:25 | MySQL Server: Memory storage engine | Closed (6540 days) | S3 | 5.0.18 | Linux (Debian Linux) | Any | Memory tables INDEX USING HASH (a,b) returns 1 row on SELECT WHERE a= AND b= |
| 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 |
| 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 |
| 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 |
| 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 |
| 30090 | 2007-07-27 6:23 | 2012-05-18 20:19 | MySQL Server: Memory storage engine | Duplicate (5981 days) | S3 | 5.0.44 | Any | Any | DELETE from MEMORY table with BTREE primary key extremely slow |
| 31445 | 2007-10-08 12:12 | 2012-05-18 20:19 | MySQL Server: Memory storage engine | Duplicate (6024 days) | S2 | 5.0.45 | Windows (Linux) | Any | Delete only deletes first matching record |
| 19138 | 2006-04-17 12:52 | 2007-05-03 6:02 | MySQL Server: Memory storage engine | Duplicate (6196 days) | S3 | 5.0.20, 5.0.19, 4.1.20 | Linux (Linux) | Any | The table 'foo' is full displayed on HEAP tables which shouldn't be full |
| 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 |
| 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) |
| Showing 1-30 of 61 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
