Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
43988 | 2009-03-31 16:30 | 2011-02-16 23:43 | MySQL Server: Partitions | Duplicate (5492 days) | S3 | 5.1/6.0 | Any | Any | AUTO_INCREMENT errors with partitioned InnoDB tables in 5.1.31 |
44319 | 2009-04-16 12:27 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5441 days) | S3 | 5.1.34 | Solaris | Any | Assertion failure in file ha_innodb.cc line 4018 |
44581 | 2009-04-30 16:44 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5549 days) | S2 | 5.1.34 and 5.4.0 | Any | Any | Slave stops when transaction with non-transactional table gets lock wait timeout |
45677 | 2009-06-23 13:08 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5066 days) | S2 | 5.1.35 and 5.4.0 | Any | Any | Slave stops with Duplicate entry for key PRIMARY when using trigger |
45823 | 2009-06-29 13:38 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (5386 days) | S1 | 5.1.31, 5.1.31sp1, 5.1.34, 5.1.34sp1, 5.1.37 | Any | Any | Assertion failure in file row/row0mysql.c line 1386 |
46864 | 2009-08-22 7:05 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5480 days) | S3 | 5.1.38, 5.0, 5.1, next bzr | Any | Any | Incorrect update of InnoDB table on slave when using trigger with myisam table |
47879 | 2009-10-06 22:12 | 2010-03-07 19:52 | MySQL Server: Backup | Closed (5308 days) | S3 | 5.4.4,6.0 | Any | Any | Backup of partitioned tables with subpartitions can crash server |
48666 | 2009-11-10 12:15 | 2012-05-18 20:19 | MySQL Server: Replication | Duplicate (5128 days) | S3 | 5.0.88-bzr, 5.1.41, 5.1.42-bzr | Any | Any | Memory tables + max_heap_table_size can cause replication problems |
49353 | 2009-12-02 15:13 | 2010-03-23 15:56 | MySQL Server: Backup | Closed (5292 days) | S3 | 6.0-backup, 6.0.14 | Any | Any | Memory tables + max_heap_table_size can cause backup/restore problems |
49414 | 2009-12-03 19:34 | 2010-03-02 1:28 | MySQL Server: Backup | Closed (5313 days) | S3 | 6.0-backup, 6.0.14 | Any | Any | Innodb tbl w/blob and text column with NULL no longer NULL after backup/restore |
49620 | 2009-12-11 12:21 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (5384 days) | S3 | 5.1.43, 5.1, next-mr bzr | Any | Any | Repl diff with concurrent transactions with trigger+savepoint+lock wait timeout |
49652 | 2009-12-14 0:32 | 2016-10-16 20:45 | MySQL Server: Replication | Duplicate (5391 days) | S3 | 6.0-backup, 6.0.14 | Any | Any | LOAD DATA - missing schema name in binlog can break replication |
50357 | 2010-01-15 9:15 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5314 days) | S3 | 6.0-backup | Any | Any | Innodb blob+text columns: empty strings become NULL after restore |
50429 | 2010-01-18 23:08 | 2011-02-16 23:44 | MySQL Server: Replication | No Feedback (5324 days) | S3 | 5.1.43 | Any | Any | ASCII function in WHERE clause is causing incorrect updates/deletes on slave |
51226 | 2010-02-16 23:18 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5202 days) | S3 | 5.1.44, 6.0-backup | Any | Any | mysqlbinlog replay: ERROR 1146 when using temp tables + failing statements |
51716 | 2010-03-04 11:36 | 2011-02-16 23:44 | MySQL Server: Replication | Closed (5291 days) | S3 | 5.5.99-m3 (Celosia) | Any | Any | Char column with utf16 character set gives wrong padding on slave |
52360 | 2010-03-25 12:38 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5204 days) | S3 | 5.1 | Any | Any | Innodb assertion wait_lock in lock/lock0lock.c on UPDATE |
53297 | 2010-04-29 20:57 | 2011-02-16 23:44 | MySQL Enterprise Backup | Unsupported (4963 days) | S3 | 3.1 | Any | Any | innobackup timeout while waiting to get readlock |
53675 | 2010-05-15 19:54 | 2012-05-18 20:19 | MySQL Server: Security: Privileges | Duplicate (5237 days) | S3 | 5.1.46, 5.1.47 | Any | Any | Missing a table level privilege after upgrade |
54470 | 2010-06-13 17:11 | 2012-04-09 22:41 | MySQL Enterprise Backup | Closed (4544 days) | S3 | 3.1, 3.5 | Windows | Any | MEB 3.1 VPAT/508 Compliance issues |
56821 | 2010-09-16 16:03 | 2011-02-16 23:44 | MySQL Server | Closed (5057 days) | S3 | 5.1.51, 5.5.7, 5.6.1 | Windows (Any) | Any | Failure to start the MySQL Service |
56851 | 2010-09-18 15:30 | 2012-10-04 6:59 | MySQL Server: Config Wizard | Duplicate (4366 days) | S3 | 5.1.x | Windows | Any | Default innodb_log_file_size in my.ini can cause MySQL service startup to fail |
57122 | 2010-09-30 7:46 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (5038 days) | S3 | 3.5 | Any | Any | mysqlbackup (innobackup C port) unlocks tables too early |
57211 | 2010-10-04 9:31 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (5038 days) | S3 | 3.5 | Any | Any | mysqlbackup (innobackup C port) may fail to free some memory |
57222 | 2010-10-04 17:19 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4981 days) | S3 | 3.5.2 | Any | Any | apply-log of incremental backup fails when iteration goes beyond end of array |
57246 | 2010-10-05 12:31 | 2011-12-11 7:15 | MySQL Enterprise Backup | Closed (4664 days) | S3 | 3.5 | Any | Any | --apply-log is not atomic - if it fails it might corrupt the backup image |
57260 | 2010-10-05 19:32 | 2011-01-28 18:18 | MySQL Enterprise Backup | Not a Bug (4981 days) | S3 | 3.5 | Any | Any | Using both --incremental and --backup-and-apply-log should not be allowed |
57286 | 2010-10-06 14:24 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4981 days) | S3 | 3.5 | Any | Any | --apply-log is not updating binlog/lsn info files in full backup dir |
57308 | 2010-10-07 11:19 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (5038 days) | S3 | 3.5 | Any | Any | Table mysql.backup_history - some issues |
57335 | 2010-10-08 6:35 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4981 days) | S3 | 3.5.2 | Any | Any | abnormal termination of the backup process could leave the global lock active |
Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |