Showing 1-30 of 443 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |
ID# | Date | Updated | Type | Status | Sev | Version | OS | CPU | Summary |
---|---|---|---|---|---|---|---|---|---|
60334 | 2011-03-04 11:35 | 2011-03-04 11:47 | MySQL Server: Replication | Verified (4774 days) | S3 | Any | Any | LOAD XML INFILE cannot be replicated correctly on SBR. | |
62829 | 2011-10-19 18:58 | 2011-10-20 13:13 | MySQL Server: Replication | Verified (4544 days) | S2 | 5.1.57 | Any | Any | INSERT/SELECT between Blackhole tables loses INSERT_ID |
63677 | 2011-12-08 17:50 | 2011-12-14 10:41 | MySQL Server: Replication | Verified (4494 days) | S2 | 5.5.17, 5.5.19 | Any | Any | Statement is incorrectly tagged as unsafe with triggers and auto increments |
62537 | 2011-09-25 16:58 | 2012-01-09 13:20 | MySQL Server: Replication | Verified (4473 days) | S3 | 5.5.20 | Any | Any | False "unsafe statement" log report |
64041 | 2012-01-16 12:13 | 2012-01-19 11:11 | MySQL Server: Replication | Verified (4456 days) | S3 | 5.1.60, 5.5.20, 5.6.4 | Any | Any | Replication failure on concurrent REMOVE PARTITIONING and OPTIMIZE PARTITION |
64758 | 2012-03-25 15:07 | 2012-03-27 7:31 | MySQL Server: Replication | Verified (4387 days) | S3 | 5.5.20, 5.5.22 | Any | Any | Error 1592 is not selective enough |
64800 | 2012-03-29 14:44 | 2012-03-31 10:12 | MySQL Server: Replication | Verified (4381 days) | S3 | server: 5.5.15, mysqldump: 10.13, 5.6.6 | Linux | Any | mysqldump with --include-master-host-port putting quotes around port number |
50917 | 2010-02-04 15:23 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4865 days) | S3 | 5.1.43,5.5.2-m2 | Any | Any | slave stops with HA_ERR_KEY_NOT_FOUND |
52226 | 2010-03-19 16:27 | 2012-05-18 20:19 | MySQL Server: Replication | Verified | S3 | 5.1.41 | Any | Any | Relay logs rotate inappropriately |
55733 | 2010-08-04 8:47 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4783 days) | S5 | 5.1.37 | Linux (CentOS 5.3) | Any | replication I/O slave is replicating statements that should be ignored |
59561 | 2011-01-17 17:03 | 2012-05-18 20:19 | MySQL Server: Replication | Verified | S3 | 5.5+ | Any | Any | Slave gets out of sync if binlog direct is on and tables share the same name |
16764 | 2006-01-25 1:51 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (6638 days) | S3 | 5.0 | Linux (linux) | Any | SHOW BINLOG EVENTS not showing error_code or exec_time |
28270 | 2007-05-07 0:49 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (6169 days) | S3 | 5.0, 5.1, 4.1 | Any | Any | CHANGE MASTER command does not accept variables |
34586 | 2008-02-15 10:47 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (5887 days) | S3 | 5.0.46-enterprise-gpl-log | Any | Any | Misleading error message on binlog index not writeable |
36922 | 2008-05-23 16:47 | 2012-05-18 20:19 | MySQL Server: Replication | Verified | S3 | 5.0.62 | HP/UX (HP-PA (all versions)) | Any | Synchronization between master and slave (replication) fails |
46731 | 2009-08-14 16:22 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (5265 days) | S3 | 5.0, 5.1, 5.4.4 | Any | Any | Replication aborts on DML statement with concurrent CREATE or RENAME table |
57287 | 2010-10-06 14:42 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4923 days) | S2 | 5.1+ | Any | Any | Slave_SQL_Errno is sometimes zero even when there is an error |
59124 | 2010-12-23 9:56 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4844 days) | S3 | 5.1, 5.6.2 | Any | Any | Queries are binlogged with wrong charset |
55468 | 2010-07-22 5:49 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4999 days) | S3 | 5.1, 5.5+ | Any | Any | Some statements binlogged follow the set of lower_case_table_name, some are not! |
56445 | 2010-09-01 9:57 | 2012-05-18 20:19 | MySQL Server: Replication | Verified (4826 days) | S3 | 5.5+ | Any | Any | The last_master_timestamp can not keep monotone order |
64220 | 2012-02-03 13:32 | 2012-07-08 10:01 | MySQL Server: Replication | Verified (4282 days) | S2 | 5.1.49 | Any | Any | auto_increment_increment should be independently settable for every database |
67840 | 2012-12-07 19:43 | 2013-01-10 19:19 | MySQL Server: Replication | Verified (4096 days) | S3 | 5.1, 5.5, 5.5.30, 5.7.1 | Any | Any | MySQL replication start inefficient at large RTTs |
68074 | 2013-01-13 20:39 | 2013-01-17 20:02 | MySQL Server: Replication | Verified (4089 days) | S3 | 5.5.27 | Linux (Slackware 14.0 64 bit) | Any | Replication fails on the mysql.tables_priv table |
68203 | 2013-01-28 9:39 | 2013-01-30 17:26 | MySQL Server: Replication | Verified (4076 days) | S3 | 5.1.54, 5.0.97, 5.1.69, 5.5.31, 5.7.1 | Linux | Any | slave does not retry connect |
68351 | 2013-02-12 18:44 | 2013-02-13 8:11 | MySQL Server: Replication | Verified (4062 days) | S3 | 5.6.10 | Any | Any | Out of range updates/deletes are not written to binlog |
68542 | 2013-03-01 19:46 | 2013-03-04 14:19 | MySQL Server: Replication | Verified (4043 days) | S3 | 5.5 | Any | Any | Handle duplicated server_id across multiple slaves in a better manner |
68543 | 2013-03-01 19:49 | 2013-03-07 7:17 | MySQL Server: Replication | Verified (4040 days) | S3 | 5.5 | Any | Any | SQL Thread's status variable values are not visible while replication is active |
66363 | 2012-08-13 21:33 | 2013-03-13 22:32 | MySQL Server: Replication | Verified (4034 days) | S2 | 5.1.58, 5.1.67 | Linux (rhel 6.1) | Any | Large transaction writing rbr with sync_binlog hangs entire server on fsync |
69454 | 2013-06-12 18:46 | 2013-06-12 21:07 | MySQL Server: Replication | Verified (3943 days) | S3 | 5.x | Any | Any | there are better ways to sync server clocks than MySQL query |
69491 | 2013-06-17 12:16 | 2013-06-18 7:01 | MySQL Server: Replication | Verified (3937 days) | S2 | 5.1 and 5.5 | Linux (debian) | Any | Breaking replication with update on fulltext |
Showing 1-30 of 443 (Edit, Save, CSV, Feed) | Show Next 30 Entries » |