Comments on: mysqlbinlog --server-id before MySQL 5.1? awk to the rescue! http://www.pythian.com/news/1299/mysqlbinlog-server-id-before-mysql-51-awk-to-the-rescue/ News and views from Pythian DBAs Fri, 10 Feb 2012 13:01:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Lars Thalmann http://www.pythian.com/news/1299/mysqlbinlog-server-id-before-mysql-51-awk-to-the-rescue/#comment-354925 Lars Thalmann Fri, 17 Apr 2009 00:35:35 +0000 http://www.pythian.com/blogs/1299/mysqlbinlog-server-id-before-mysql-51-awk-to-the-rescue#comment-354925 To solve this problem, we have, in MySQL 6.0, introduced a mechanism to filter by server id in replication. See CHANGE MASTER IGNORE_SERVER_IDS in: http://dev.mysql.com/doc/refman/6.0/en/change-master-to.html To solve this problem, we have, in MySQL 6.0, introduced a mechanism to filter by server id in replication.

See CHANGE MASTER IGNORE_SERVER_IDS in:
http://dev.mysql.com/doc/refman/6.0/en/change-master-to.html

]]> By: Arjen Lentz http://www.pythian.com/news/1299/mysqlbinlog-server-id-before-mysql-51-awk-to-the-rescue/#comment-289554 Arjen Lentz Sun, 12 Oct 2008 19:27:02 +0000 http://www.pythian.com/blogs/1299/mysqlbinlog-server-id-before-mysql-51-awk-to-the-rescue#comment-289554 Yea this goes to show once again that circular replication (master-master with more than 2 servers) only seems like a good idea, until there is a failover situation. And taking out a server-id like you had, that might be the ultimate nuisance ;-) Thanks for that. Yea this goes to show once again that circular replication (master-master with more than 2 servers) only seems like a good idea, until there is a failover situation. And taking out a server-id like you had, that might be the ultimate nuisance ;-)
Thanks for that.

]]>