| Showing 1-30 of 328 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
| ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
|---|---|---|---|---|---|---|---|---|---|
| 59651 | 2011-01-21 10:31 | 2011-04-26 15:43 | MySQL Server: Optimizer | Closed (4739 days) | S1 | 5.6.2-debug | Any | Any | Assertion `table_ref->has_record' failed with join_cache_level=3 |
| 12692 | 2005-08-19 22:32 | 2005-11-22 15:09 | MySQL Server: Replication | Closed (6720 days) | S3 | 5.0-wl1012 | Linux (Linux) | Any | TRUNCATE TABLE mysqltest1.t7 is not being replicated using rbr. |
| 59432 | 2011-01-11 21:55 | 2011-02-16 23:44 | MySQL Server: Options | Closed (4826 days) | S3 | 5.5 | Any | Any | --autocommit=on does not work (@@global.autocommit is 0) |
| 7236 | 2004-12-13 14:16 | 2005-01-10 10:11 | MySQL Server: Replication | Closed (7036 days) | S3 | 4.1 | Any (all) | Any | --expire_logs_days does not apply if all statements happen in transactions |
| 2428 | 2004-01-16 9:23 | 2004-01-18 8:40 | MySQL Server: Replication | Closed (7394 days) | S3 | 4.0.17 | Linux (Debian GNU Linux (Woody)) | Any | --old-rpl-compat is broken |
| 2757 | 2004-02-12 14:14 | 2004-02-28 14:39 | MySQL Server | Closed (7353 days) | S3 | 4.0.17 | Windows (Windows 2000) | Any | --read-only gives weird error on update |
| 2758 | 2004-02-12 14:23 | 2004-03-20 7:55 | MySQL Server: Documentation | Closed (7332 days) | S3 | 5.0 | Any (All) | Any | --read-only option seems undocumented |
| 12424 | 2005-08-07 23:22 | 2005-09-29 8:21 | MySQL Server: Replication | Closed (6774 days) | S2 | 5.0-wl1012 | Linux (Linux) | Any | --replicate-rewrite-db is not working with rbr |
| 5460 | 2004-09-08 6:29 | 2004-09-21 14:52 | MySQL Server: Replication | Closed (7147 days) | S2 | 4.0.20 | Linux (Linux 2.4.20-30.9smp) | Any | "create database" not replicated |
| 3204 | 2004-03-17 9:48 | 2004-03-18 9:34 | MySQL Server: Replication | Closed (7334 days) | S3 | 4.0 | Any (all) | Any | "mysqlbinlog --read-from-remote-server this_binlog.001" prints all binlogs |
| 3015 | 2004-02-29 15:16 | 2004-03-01 6:19 | MySQL Server: Replication | Closed (7351 days) | S3 | 4.0, 4.1, 5.0 | Any (all) | Any | (binlog, position) stored by InnoDB for a replication slave can be wrong |
| 254 | 2003-04-08 15:04 | 2003-06-06 7:52 | MySQL Server: Replication | Closed (7620 days) | S2 | Any (all) | Any | 3.23 master, 4.0 slave. Slave loss temp tables everytime FLUSH LOGS on master | |
| 52 | 2003-01-31 22:53 | 2003-03-06 8:49 | MySQL Server: Replication | Closed (7712 days) | S3 | 4.0, 4.1 | Any (all) | Any | 4.0 If only transactions are run on the master then the slave shows wrong info |
| 69 | 2003-02-13 8:22 | 2003-03-03 6:45 | MySQL Server: Replication | Closed (7715 days) | S3 | 4.0 | Windows (Windows) | Any | 4.0.9 Windows slave hangs on STOP SLAVE |
| 52636 | 2010-04-06 21:22 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4893 days) | S3 | 6.0-codebase-bugfixing | Any | Any | 6.0 allowing JOINs on NULL values w/ optimizer_join_cache_level = 5-8 |
| 3247 | 2004-03-21 5:46 | 2005-04-04 8:28 | MySQL Server: Replication | Closed (6952 days) | S2 | 4.0 | Any (all) | Any | a partially completed LOAD DATA INFILE is not executed at all on the slave |
| 36 | 2003-01-24 0:25 | 2003-01-28 16:49 | MySQL Server | Closed (7749 days) | S3 | 3.23 and 4.x | Any | A query using both auto_increment and LAST_INSERT_ID() breaks binlog | |
| 490 | 2003-05-24 7:09 | 2003-07-01 6:14 | MySQL Server: Replication | Closed (7595 days) | S2 | 4.0.13 | Any (all) | Any | Accidental introduction of a bug with auto_increment and INSERT SELECT |
| 763 | 2003-06-30 8:43 | 2003-07-02 13:40 | MySQL Server: Replication | Closed (7594 days) | S3 | 4.0 | Any (all) | Any | After RESET SLAVE, Relay_log_space in SHOW SLAVE STATUS is too much by 4 bytes |
| 2333 | 2004-01-09 6:43 | 2004-01-12 12:07 | MySQL Server | Closed (7400 days) | S3 | 4.1 | Any (all) | Any | ALTER DATABASE on inexistent database hangs the client |
| 3871 | 2004-05-24 12:55 | 2004-05-24 18:51 | MySQL Server | Closed (7267 days) | S2 | 4.0.18 | FreeBSD (freebsd (maybe any)) | Any | ANALYZE not in binlog => replication failure on max_join_size |
| 12003 | 2005-07-18 12:12 | 2005-07-18 13:14 | MySQL Server | Closed (6847 days) | S1 | 4.1 | Linux (linux) | Any | assertion failure in testsuite (double lock of LOCK_thread_count) |
| 56254 | 2010-08-25 14:16 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4894 days) | S1 | bzr_mysql-next-mr-opt-team | Any | Any | Assertion tab->ref.use_count fails in join_read_key_unlock_row() on 4-way JOIN |
| 34106 | 2008-01-28 15:18 | 2008-01-31 1:11 | MySQL Server: Maria storage engine | Closed (5920 days) | S2 | 5.1.23-maria-alpha | Linux | Any | auto_increment is reset to 1 when table is recovered from crash |
| 20524 | 2006-06-18 20:00 | 2006-08-01 3:19 | MySQL Server: General | Closed (6468 days) | S3 | 5.0 | Linux (Linux) | Any | auto_increment_* not observed when inserting a too large value |
| 46743 | 2009-08-15 17:14 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4893 days) | S3 | 5.4/6.0 | Any | Any | Azalea processing correlated, aggregate SELECT subqueries incorrectly |
| 51018 | 2010-02-09 9:19 | 2011-02-16 23:44 | MySQL Server: Optimizer | Closed (4893 days) | S3 | 6.0-codebase-bugfixing | Any | Any | Batched key access gives wrong results for SELECT with semijoin and NULL |
| 985 | 2003-08-03 13:35 | 2009-12-17 22:04 | MySQL Server: Replication | Closed (7561 days) | S3 | 4.0 | Any (all) | Any | Between RESET SLAVE and START SLAVE, SHOW SLAVE STATUS is wrong |
| 239 | 2003-04-06 22:15 | 2005-05-19 14:24 | MySQL Server | Closed (6907 days) | S2 | 4.0.12 | Linux (linux glibc6) | Any | bin-log not working |
| 1381 | 2003-09-23 9:10 | 2003-10-01 9:45 | MySQL Server: Replication | Closed (7503 days) | S2 | 4.0.15 | HP/UX (HP-UX) | Any | Bug in replication on HP-UX 64 bit binaries? |
| Showing 1-30 of 328 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
