> 1. Extra slave tables messes with replication? (Rob Marscher) > > > > Hey everyone... > > I had replication stop on a slave server on which I had added a few > extra summary tables. The error that caused replication to stop > didn't mention any of these new tables... but my sysadmin is > suspicious that the change in db structure could have been part of the > reason replication broke. It's my understanding that it's ok to add > extra tables on a slave... that mysql replication isn't smart enough > to care about that... it basically just replays queries from the > master's binary log. I've been searching the internet and mysql > online documentation and haven't been able to find a statement > supporting either argument. > > Can anyone help me clear this up? > Thanks, > Rob
Does this help? http://www.xaprb.com/blog/2007/01/20/how-to-make-mysql-replication-reliable/ "2.2 Prevent changes to slave data If you don't keep users and processes from changing data and tables on the slave, you're guaranteed to get out of sync. If someone updates, deletes or inserts rows on the slave, the data is automatically out of sync, and the errors accumulate over time. Likewise, if someone changes a table structure, alters a column's data type, or makes any other schema change, things will break. The most straightforward way to avoid this is revoke all write privileges on slaves. (By the way, your schema and privileges ought to be in version control<http://www.xaprb.com/blog/2006/07/09/so-you-think-your-code-is-in-version-control/> )."
_______________________________________________ New York PHP Community MySQL SIG http://lists.nyphp.org/mailman/listinfo/mysql NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
