As far I know, it would help to leave it set. All the queries executed by the slave to follow the master have the master's server id associated with them. The one's which don't have that id will be replicated by the new slave(old master), there by making the process easier and faster.
Regards, Bhavin. ----- Original Message ----- From: "Vicky Gonzalez" <[EMAIL PROTECTED]> To: "Bhavin Vyas" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, September 03, 2002 6:16 PM Subject: RE: changing a slave to a master in mysql replication Bhavin Vyas wrote Tuesday, September 03, 2002 9:02 PM in response to: >>To: Vicky Gonzalez; [EMAIL PROTECTED] >>Subject: Re: changing a slave to a master in mysql replication >>bin-log in 'needed' for a server to act as a master. This will make the server log all it's queries for the slave to follow. Don't know of a faster way.>> Thanks for the prompt reply, I understand why bin-log is needed for a master, but I was questioning the usefulness of having the bin-log setting for a slave while it's running as a slave. When the slave becomes a master, doesn't it need a new my.cnf (which would have the bin-log set) or can it become a master with its slave my.cnf? If it can become a master using the slave my.cnf (which has the bin-log set) what commands would I need to call to make it a master now, and no longer a slave to its old master? Thanks again! ~Vicky --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
