http://guogoul.com Fri, 29 Oct 2010 00:24:37 +0000 http://wordpress.org/?v=2.8.4 en hourly 1 http://guogoul.com/2010/01/30/storage_requirements_for_string_types/ http://guogoul.com/2010/01/30/storage_requirements_for_string_types/#comments Sat, 30 Jan 2010 12:41:14 +0000 shanfeng http://guogoul.com/?p=245 http://guogoul.com/2010/01/30/storage_requirements_for_string_types/feed/ 1 http://guogoul.com/2009/12/10/mysql-index-limi/ http://guogoul.com/2009/12/10/mysql-index-limi/#comments Thu, 10 Dec 2009 14:51:23 +0000 shanfeng http://guogoul.com/?p=228 http://guogoul.com/2009/12/10/mysql-index-limi/feed/ 0 http://guogoul.com/2009/07/29/share_percona_pdf/ http://guogoul.com/2009/07/29/share_percona_pdf/#comments Wed, 29 Jul 2009 01:13:39 +0000 shanfeng http://guogoul.com/?p=191 http://guogoul.com/2009/07/29/share_percona_pdf/feed/ 0 http://guogoul.com/2009/07/13/logs-slave-updates/ http://guogoul.com/2009/07/13/logs-slave-updates/#comments Mon, 13 Jul 2009 14:06:07 +0000 shanfeng http://guogoul.com/?p=184 B -> C 也就是说，A为从服务器B的主服务器，B为从服务器C的主服务器。为了能工作，B必须既为主服务器又为从服务器。你必须用--logs-bin启动A和B以启用二进制日志，并且用--logs-slave-updates选项启动B。 以上是摘自mysql对于logs-slave-updates启动选项的描述。 当然logs-slave-upates也可以写入my.cnf : ////////////////// log_slave_updates=1 ////////////////// 当然在这种机制下可能有的同学会存在这么个问题： 如果a->b b->a 这样的双master架构下，a,b都打开log_slave_updates选项会不会出现无限循环的状态。 mysql已经考滤到了这个问题，每条bin-log都会记录执行语句的源server_id.当slave读到语句的server_id等于本身的ID的时候，不会忽略执行，所以我们不用担心a,b会不会无限循环下去。 基于以上这种情况，mysql的replication集群将更加灵活，你如果需要可以做成各种各样的链式复制。比如 a->b b->a b中设置log_slave_updates后还可以b->c. 这样a,c中的数据也是一致的。 测试部分my.cnf 26 [mysqld2] 27 pid-file = /home/shanfeng/mysql/data2/mysqld2.pid 28 socket = /home/shanfeng/mysql/data2/mysqld2.sock [...]]]> http://guogoul.com/2009/07/13/logs-slave-updates/feed/ 1 http://guogoul.com/2009/06/18/db_filesys/ http://guogoul.com/2009/06/18/db_filesys/#comments Thu, 18 Jun 2009 15:42:06 +0000 john http://john.renren.in/?p=118 http://guogoul.com/2009/06/18/db_filesys/feed/ 0 http://guogoul.com/2009/06/10/innodb_log_file_size/ http://guogoul.com/2009/06/10/innodb_log_file_size/#comments Wed, 10 Jun 2009 15:13:08 +0000 john http://john.renren.in/?p=122 http://guogoul.com/2009/06/10/innodb_log_file_size/feed/ 0 http://guogoul.com/2009/06/09/mysqlreport/ http://guogoul.com/2009/06/09/mysqlreport/#comments Mon, 08 Jun 2009 16:07:14 +0000 john http://john.renren.in/?p=113 http://guogoul.com/2009/06/09/mysqlreport/feed/ 0 http://guogoul.com/2009/06/04/mysqldumpslow/ http://guogoul.com/2009/06/04/mysqldumpslow/#comments Thu, 04 Jun 2009 11:29:15 +0000 john http://john.renren.in/?p=117 http://guogoul.com/2009/06/04/mysqldumpslow/feed/ 0 http://guogoul.com/2009/06/01/storage_engin/ http://guogoul.com/2009/06/01/storage_engin/#comments Mon, 01 Jun 2009 15:16:33 +0000 john http://john.renren.in/?p=121 http://guogoul.com/2009/06/01/storage_engin/feed/ 0 http://guogoul.com/2008/11/02/mysql_4_index/ http://guogoul.com/2008/11/02/mysql_4_index/#comments Sun, 02 Nov 2008 00:50:17 +0000 john http://www.guogoul.com/2008/11/02/mysql_4_index/ http://guogoul.com/2008/11/02/mysql_4_index/feed/ 13