Showing 1-30 of 272 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
66081 | 2012-07-30 12:12 | 2012-08-31 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4256 days) | S3 | 5.1.61 | Linux (2.6.32) | Any | InnoDB: Warning: purge reached the head of the history list |
69232 | 2013-05-14 16:48 | 2017-09-24 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2406 days) | S4 | 5.7 | Any | Any | buf_dblwr->mutex can be splited into two |
64512 | 2012-03-01 10:48 | 2012-05-17 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4362 days) | S1 | 5.6.4 | Linux | Any | error 56 upon abnormal disconnect when temporary tables exist, crash |
64172 | 2012-01-30 19:24 | 2012-03-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4439 days) | S3 | 5.1.41 | Linux (Ubuntu 10.04) | Any | Mysql crashed once with an “Assertion failure" rem0rec.c line 337 |
39810 | 2008-10-02 13:55 | 2013-08-25 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5631 days) | S1 | mysql-5.1.26-rc-linux-x86_64-glibc23 | Linux (Linux tiara.log-11 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 x86_64 x86_64 GNU/Linux) | Any | `#mysql50#raw_data#P#p20` already exists in InnoDB ... |
26749 | 2007-03-01 14:09 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6234 days) | S3 | 5.0.17 | Windows (win2003) | Any | " Incorrect decimal value: " |
66253 | 2012-08-08 3:45 | 2012-09-10 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4246 days) | S3 | 5.5.20 | Linux (Centos 6.2) | Any | [Warning] Invalid (old?) table or database name '#sqlXXXX_XXX_XXXX' |
29609 | 2007-07-07 8:23 | 2007-08-07 11:46 | MySQL Server: InnoDB storage engine | No Feedback (6106 days) | S2 | 5.0.15-nt-log | Windows (show variables included) | Any | 0 length string update does not work on varchar variables; |
11475 | 2005-06-21 10:06 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6851 days) | S1 | 4.1.9 | Windows (Win 2003 Server) | Any | 1016 error. tables are not accessable and cannot be repaired |
69164 | 2013-05-07 14:41 | 2013-06-08 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3975 days) | S1 | mysql Ver 14.14 Distrib 5.1.57, for unk | Linux (2.6.13.5) | Any | 130507 9:34:33 - mysqld got signal 6 ; |
65468 | 2012-05-30 20:48 | 2013-03-01 1:00 | MySQL Server: InnoDB storage engine | No Feedback (4074 days) | S2 | 5.5.14-enterprise-commercial-advanced-lo | Solaris (innodb) | Any | A couple of rows in tbl had write locks that couldn't be cleared |
740 | 2003-06-27 9:13 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (7117 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 (7392 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 |
33601 | 2007-12-31 17:30 | 2013-03-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5287 days) | S4 | 5.1 | Any | Any | adding a view for information_schema to identify lock waiting relations |
43317 | 2009-03-03 0:31 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5501 days) | S3 | 5.0.45 and 5.0.51a | Linux | Any | addtime() returns different results depending on how the date is formatted |
80969 | 2016-04-06 7:58 | 2017-06-19 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2503 days) | S1 | 5.7.11, 5.7.12 | Any | Any | After exceeding max undo space size the purge will not work(default 1G) |
278 | 2003-04-11 23:03 | 2012-05-18 20:19 | MySQL Server: InnoDB storage engine | No Feedback (7016 days) | S1 | 4.0.12 | Windows (WindowsXP) | Any | After many queries LEFT JOIN returns incorrect results. SHOW INDEXES fixes it |
24250 | 2006-11-13 10:57 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6290 days) | S2 | 5.1.12 | Windows (Win XP SP 2) | Any | ALTER TABLE ADD PRIMARY KEY on InnoDB is so slow as to be unusable |
3502 | 2004-04-19 7:46 | 2004-10-26 14:07 | MySQL Server: InnoDB storage engine | No Feedback (7121 days) | S1 | 4.0 , 4.1 and higher | Any (any) | Any | ANALYZE changes MySQL table locks of other threads |
81112 | 2016-04-17 20:14 | 2016-05-19 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2899 days) | S1 | 5.6.30 | Any (6.7) | Any | Assertion failure |
75915 | 2015-02-16 8:59 | 2015-03-21 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3324 days) | S1 | 5.5.41 | Linux (Ubuntu 12.04 LTS) | Any | Assertion failure in file btr0pcur.c line 428 |
88770 | 2017-12-06 3:14 | 2018-01-12 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2296 days) | S2 | 5.5.28 | CentOS (Linux 3.10.0-693.5.2.el7.x86_64 x86_64) | Any | Assertion failure in file during InnoDB recovery |
2903 | 2004-02-20 6:59 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6734 days) | S2 | 4.0.17-standard-pc-linux-i686 | Linux (Linux - RH9) | Any | Assertion failure in file ha_innodb.cc line 2020 |
44319 | 2009-04-16 12:27 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5296 days) | S3 | 5.1.34 | Solaris | Any | Assertion failure in file ha_innodb.cc line 4018 |
71992 | 2014-03-10 10:27 | 2015-12-08 1:00 | MySQL Server: InnoDB storage engine | No Feedback (3062 days) | S2 | 5.6.16 | Solaris | Any | assertion failure in MySQL server |
76548 | 2015-03-31 16:20 | 2018-06-11 1:00 | MySQL Server: InnoDB storage engine | No Feedback (2146 days) | S2 | 5.6.21 | Windows | Any | Auto-increment value copied from source to destination table when using trigger |
34865 | 2008-02-26 22:14 | 2008-05-02 10:08 | MySQL Server: InnoDB storage engine | No Feedback (5837 days) | S1 | 5.0.27 | Any | Any | Backup with table name 'policy" failed |
48622 | 2009-11-09 7:43 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | No Feedback (5247 days) | S1 | upgrade from 5.0.45 to 5.1.37 | Linux (Red Hat Enterprise Linux Server release 5.1 (Tikanga)) | Any | Binary logging not possible. Transaction level 'READ-UNCOMMITTED' in Innodb |
41407 | 2008-12-11 17:31 | 2011-02-16 23:43 | MySQL Server: InnoDB storage engine | No Feedback (5583 days) | S1 | 5.1.30 | Linux | Any | BUG IN A SELECT WITH/WITHOUT ORDER BY |
22294 | 2006-09-13 5:50 | 2016-01-03 20:45 | MySQL Server: InnoDB storage engine | No Feedback (6404 days) | S3 | 5.0.21-community | Windows (xp) | Any | bug while restoring DB |
Showing 1-30 of 272 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |