Showing 1-30 of 265 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
25577 | 2007-01-12 11:21 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6271 days) | S3 | Windows (Windows) | Any | incompatibility with JPA | |
26717 | 2007-02-28 11:51 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6180 days) | S1 | Windows (Windows) | Any | InnoDB crashes and unable to recover - Failing assertion | |
64172 | 2012-01-30 19:24 | 2012-03-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4433 days) | S3 | 5.1.41 | Linux (Ubuntu 10.04) | Any | Mysql crashed once with an “Assertion failure" rem0rec.c line 337 |
3502 | 2004-04-19 7:46 | 2004-10-26 14:07 | MySQL Server: InnoDB storage engine | No Feedback (7115 days) | S1 | 4.0 , 4.1 and higher | Any (any) | Any | ANALYZE changes MySQL table locks of other threads |
278 | 2003-04-11 23:03 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | No Feedback (7010 days) | S1 | 4.0.12 | Windows (WindowsXP) | Any | After many queries LEFT JOIN returns incorrect results. SHOW INDEXES fixes it |
1703 | 2003-10-29 10:12 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7111 days) | S3 | 4.0.12 | Linux (Slackware linux) | Any | SELECT DISTINCT not showing a distinct row |
740 | 2003-06-27 9:13 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7111 days) | S1 | 4.0.13 | Windows (Windows XP Pro) | Any | A table called 'address' can be created in 4.0.12 but not 4.0.13 |
870 | 2003-07-18 3:41 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7386 days) | S2 | 4.0.13 | Linux (Linux 2.4.19) | Any | abnormal innodb data growth after upgrading from 3.23.56 to 4.0.13 |
1583 | 2003-10-17 3:10 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | No Feedback (7209 days) | S2 | 4.0.14+ | Windows (WinNT) | Any | Unusable ORDER BY performance |
2903 | 2004-02-20 6:59 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6728 days) | S2 | 4.0.17-standard-pc-linux-i686 | Linux (Linux - RH9) | Any | Assertion failure in file ha_innodb.cc line 2020 |
4478 | 2004-07-08 23:28 | 2018-02-11 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7109 days) | S1 | 4.0.18 | Linux (Redhat Kernel 2.4.20) | Any | Wrong use of indices for InnoDB tables |
34344 | 2008-02-06 10:42 | 2008-04-18 15:36 | MySQL Server: InnoDB storage engine | No Feedback (5845 days) | S1 | 4.0.18 | Linux | Any | InnoDB: Assertion failure in thread 16384 in file fil0fil.c line 1204 |
34998 | 2008-03-03 12:35 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5860 days) | S3 | 4.0.20-a | Linux | Any | database crashes constantly when performing DELETE query |
4979 | 2004-08-10 16:10 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7111 days) | S1 | 4.0.20-Max | Linux (Linux Redhat 9.0) | Any | INNODB SHOW TABLES hangs causes a long semaphore wait |
10449 | 2005-05-08 15:31 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6578 days) | S2 | 4.0.20a | Windows (Windows 2003 5.2, x86) | Any | Foreign key On Delete directives disappear |
7357 | 2004-12-16 18:55 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7006 days) | S2 | 4.0.22 | Linux (Linux / Debian) | Any | ERROR 1205 in InnoDB with double unique key on same column |
8187 | 2005-01-28 19:57 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | No Feedback (6990 days) | S1 | 4.0.23 | Windows (Win2k) | Any | table lock for myisam within transaction |
14206 | 2005-10-21 10:13 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6706 days) | S2 | 4.0.24 | Linux (Linux Debian 3.0) | Any | leaking of InnoDB table space |
21270 | 2006-07-25 10:58 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6447 days) | S2 | 4.1 | Windows (Windows 2003 Server) | Any | database corrupted |
6904 | 2004-12-01 4:51 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6032 days) | S2 | 4.1, 5.0.27 | Linux (Red Hat ES 3) | Any | Innodb data file grows uncontrollably |
10492 | 2005-05-09 19:23 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6897 days) | S3 | 4.1.10 | Windows (XP and Max OSX) | Any | Timestamp field does not change on a SQL update in INNODB tables |
20957 | 2006-07-11 3:27 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6461 days) | S2 | 4.1.13 | Linux (Suse 10) | Any | Innodb warning: purge reached the head of the history list |
14012 | 2005-10-13 18:14 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6342 days) | S2 | 4.1.14 | Linux (Linux amd64) | Any | InnoDB crash |
18410 | 2006-03-22 2:39 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6565 days) | S1 | 4.1.18 | Linux (Linux) | Any | InnoDB: Assertion failure in thread 1517779888 in file btr0cur.c line 3568 |
19539 | 2006-05-04 15:57 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6276 days) | S2 | 4.1.18, 4.0.26 | Linux (Suse Enterprise 9) | Any | Crash on InnoDB-only MySQL server |
29175 | 2007-06-18 11:44 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6120 days) | S3 | 4.1.20 | Linux (Linux 2.6.9-42.0.8.ELsmp #1 SMP Tue Jan 30 12:33:47 EST 2007 i686 i686 i386 GNU/Linux) | Any | InnoDB cannot allocate memory anymore after mysql crash |
36900 | 2008-05-22 23:52 | 2008-06-23 4:25 | MySQL Server: InnoDB storage engine | No Feedback (5779 days) | S2 | 4.1.20 | Linux (RHEL 4) | Any | Mysql Crash |
21451 | 2006-08-04 14:54 | 2013-08-25 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5720 days) | S2 | 4.1.20, 5.0.37, 5.0.38, 5.0.46 | Linux (SLES10 2.6.16.21-0.8-smp) | Any | InnoDB: error: return value 16 when calling InnoDB: pthread_mutex_destroy(). |
24641 | 2006-11-28 2:22 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6287 days) | S3 | 4.1.21 | Linux (RHEL4) | Any | mysql crashes with the following error message |
5203 | 2004-08-25 11:44 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7080 days) | S3 | 4.1.3b | Windows (Windows XP) | Any | mysql returns unterminated unicode strings |
Showing 1-30 of 265 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |