| Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 59130 | 2010-12-23 13:41 | 2012-04-09 22:39 | MySQL Enterprise Backup | Closed (4393 days) | S3 | 3.5.2 | Any | Any | backup directory name as timestamp string may prefix hour with _ instead of 0 |
| 57222 | 2010-10-04 17:19 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4830 days) | S3 | 3.5.2 | Any | Any | apply-log of incremental backup fails when iteration goes beyond end of array |
| 57211 | 2010-10-04 9:31 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4887 days) | S3 | 3.5 | Any | Any | mysqlbackup (innobackup C port) may fail to free some memory |
| 57122 | 2010-09-30 7:46 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4887 days) | S3 | 3.5 | Any | Any | mysqlbackup (innobackup C port) unlocks tables too early |
| 57246 | 2010-10-05 12:31 | 2011-12-11 7:15 | MySQL Enterprise Backup | Closed (4513 days) | S3 | 3.5 | Any | Any | --apply-log is not atomic - if it fails it might corrupt the backup image |
| 54470 | 2010-06-13 17:11 | 2012-04-09 22:41 | MySQL Enterprise Backup | Closed (4393 days) | S3 | 3.1, 3.5 | Windows | Any | MEB 3.1 VPAT/508 Compliance issues |
| 57260 | 2010-10-05 19:32 | 2011-01-28 18:18 | MySQL Enterprise Backup | Not a Bug (4830 days) | S3 | 3.5 | Any | Any | Using both --incremental and --backup-and-apply-log should not be allowed |
| 53297 | 2010-04-29 20:57 | 2011-02-16 23:44 | MySQL Enterprise Backup | Unsupported (4812 days) | S3 | 3.1 | Any | Any | innobackup timeout while waiting to get readlock |
| 57286 | 2010-10-06 14:24 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4830 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 (4887 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 (4830 days) | S3 | 3.5.2 | Any | Any | abnormal termination of the backup process could leave the global lock active |
| 57441 | 2010-10-13 17:47 | 2012-03-20 2:53 | MySQL Enterprise Backup | Closed (4413 days) | S3 | 3.5 | Any | Any | backup of data after reported binlog pos when using non-tx table in transaction |
| 57527 | 2010-10-18 14:37 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4817 days) | S3 | 3.5 | Any | Any | ibbackup can fail when using ALTER TABLE with options ROW_FORMAT, KEY_BLOCK_SIZE |
| 57803 | 2010-10-28 11:37 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4883 days) | S3 | 3.5 | Any | Any | Accuracy of reported binlog position when doing backup |
| 58640 | 2010-12-01 21:26 | 2011-06-22 14:30 | MySQL Enterprise Backup | Closed (4685 days) | S3 | 3.5.2 | Any | Any | mysqlbackup may abort when views are present |
| 58734 | 2010-12-04 22:05 | 2011-04-27 17:28 | MySQL Enterprise Backup | Closed (4741 days) | S3 | 3.5.2 | Any | Any | Incremental backup with per-table tablespaces failing on Windows |
| 58968 | 2010-12-16 10:06 | 2011-12-29 20:04 | MySQL Enterprise Backup | Closed (4495 days) | S3 | 3.5.2 | Any | Any | ibbackup problem if datadir path in my.cnf has multiple trailing path separators |
| 59090 | 2010-12-21 15:25 | 2011-04-27 17:38 | MySQL Enterprise Backup | Closed (4741 days) | S3 | 3.5.2 | Any | Any | mysqlbackup fails for incremental backup with large lsn value |
| 59126 | 2010-12-23 12:01 | 2011-04-27 17:31 | MySQL Enterprise Backup | Closed (4741 days) | S3 | 3.5.2 | Any | Any | ibbackup crash during incremental backup apply-log phase due to buffer overflow |
| 56821 | 2010-09-16 16:03 | 2011-02-16 23:44 | MySQL Server | Closed (4906 days) | S3 | 5.1.51, 5.5.7, 5.6.1 | Windows (Any) | Any | Failure to start the MySQL Service |
| 50357 | 2010-01-15 9:15 | 2012-05-18 20:19 | MySQL Server: Backup | Patch queued (5163 days) | S3 | 6.0-backup | Any | Any | Innodb blob+text columns: empty strings become NULL after restore |
| 49414 | 2009-12-03 19:34 | 2010-03-02 1:28 | MySQL Server: Backup | Closed (5162 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 |
| 49353 | 2009-12-02 15:13 | 2010-03-23 15:56 | MySQL Server: Backup | Closed (5141 days) | S3 | 6.0-backup, 6.0.14 | Any | Any | Memory tables + max_heap_table_size can cause backup/restore problems |
| 47879 | 2009-10-06 22:12 | 2010-03-07 19:52 | MySQL Server: Backup | Closed (5157 days) | S3 | 5.4.4,6.0 | Any | Any | Backup of partitioned tables with subpartitions can crash server |
| 56851 | 2010-09-18 15:30 | 2012-10-04 6:59 | MySQL Server: Config Wizard | Duplicate (4215 days) | S3 | 5.1.x | Windows | Any | Default innodb_log_file_size in my.ini can cause MySQL service startup to fail |
| 44319 | 2009-04-16 12:27 | 2018-09-23 20:45 | MySQL Server: InnoDB storage engine | No Feedback (5290 days) | S3 | 5.1.34 | Solaris | Any | Assertion failure in file ha_innodb.cc line 4018 |
| 57345 | 2010-10-08 20:42 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4875 days) | S3 | 5.1.52 | Any | Any | btr_pcur_store_position abort for load with concurrent lock/unlock tables |
| 52360 | 2010-03-25 12:38 | 2011-02-16 23:44 | MySQL Server: InnoDB Plugin storage engine | Closed (5053 days) | S3 | 5.1 | Any | Any | Innodb assertion wait_lock in lock/lock0lock.c on UPDATE |
| 58489 | 2010-11-25 12:42 | 2013-03-05 14:18 | MySQL Server: Locking | Won't fix (4063 days) | S3 | 5.5 | Any | Any | FLUSH TABLES WITH READ LOCK - issue with concurrent load |
| 43988 | 2009-03-31 16:30 | 2011-02-16 23:43 | MySQL Server: Partitions | Duplicate (5341 days) | S3 | 5.1/6.0 | Any | Any | AUTO_INCREMENT errors with partitioned InnoDB tables in 5.1.31 |
| Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
