Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
57335 | 2010-10-08 6:35 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4632 days) | S3 | 3.5.2 | Any | Any | abnormal termination of the backup process could leave the global lock active |
59090 | 2010-12-21 15:25 | 2011-04-27 17:38 | MySQL Enterprise Backup | Closed (4543 days) | S3 | 3.5.2 | Any | Any | mysqlbackup fails for incremental backup with large lsn value |
43988 | 2009-03-31 16:30 | 2011-02-16 23:43 | MySQL Server: Partitions | Duplicate (5143 days) | S3 | 5.1/6.0 | Any | Any | AUTO_INCREMENT errors with partitioned InnoDB tables in 5.1.31 |
57122 | 2010-09-30 7:46 | 2011-02-16 23:44 | MySQL Enterprise Backup | Closed (4689 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 (4689 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 (4632 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 (4315 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 (4632 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 (4632 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 (4689 days) | S3 | 3.5 | Any | Any | Table mysql.backup_history - some issues |
59126 | 2010-12-23 12:01 | 2011-04-27 17:31 | MySQL Enterprise Backup | Closed (4543 days) | S3 | 3.5.2 | Any | Any | ibbackup crash during incremental backup apply-log phase due to buffer overflow |
57345 | 2010-10-08 20:42 | 2011-02-16 23:44 | MySQL Server: InnoDB storage engine | Closed (4677 days) | S3 | 5.1.52 | Any | Any | btr_pcur_store_position abort for load with concurrent lock/unlock tables |
57441 | 2010-10-13 17:47 | 2012-03-20 2:53 | MySQL Enterprise Backup | Closed (4215 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 (4619 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 (4685 days) | S3 | 3.5 | Any | Any | Accuracy of reported binlog position when doing backup |
58147 | 2010-11-11 20:00 | 2011-02-16 23:44 | MySQL Server: Partitions | Closed (4673 days) | S3 | 5.5.7-rc | Any | Any | ALTER TABLE w/ TRUNCATE PARTITION fails - but the statement is written to binlog |
58489 | 2010-11-25 12:42 | 2013-03-05 14:18 | MySQL Server: Locking | Won't fix (3865 days) | S3 | 5.5 | Any | Any | FLUSH TABLES WITH READ LOCK - issue with concurrent load |
58640 | 2010-12-01 21:26 | 2011-06-22 14:30 | MySQL Enterprise Backup | Closed (4487 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 (4543 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 (4297 days) | S3 | 3.5.2 | Any | Any | ibbackup problem if datadir path in my.cnf has multiple trailing path separators |
49620 | 2009-12-11 12:21 | 2011-02-16 23:44 | MySQL Server: Replication | Can't repeat (5035 days) | S3 | 5.1.43, 5.1, next-mr bzr | Any | Any | Repl diff with concurrent transactions with trigger+savepoint+lock wait timeout |
59130 | 2010-12-23 13:41 | 2012-04-09 22:39 | MySQL Enterprise Backup | Closed (4195 days) | S3 | 3.5.2 | Any | Any | backup directory name as timestamp string may prefix hour with _ instead of 0 |
44581 | 2009-04-30 16:44 | 2011-02-16 23:43 | MySQL Server: Replication | Closed (5200 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 (4717 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 (5037 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 (5131 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 (4959 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 (4779 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 (4943 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 (4964 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 |
Showing 1-30 of 42 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |