DVP ---- Dathan Vance Pattishall http://www.friendster.com
> -----Original Message----- > From: Sanjeev Sagar [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 02, 2004 4:04 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: Sanjeev Sagar > Subject: Binlog question in replication setup > > Hello everyone, > > > > I need to know that how MySQL write to binlog file. > It gets written in order of compeltion, so if the table exists on the master and the alter takes 50 seconds to run the commit to the binlog happens on the 50th second. If the table doesn't exist on the slave a slave error get produced and the SQL thread stops while the IO thread keeps running downloading the transaction in a file "queue" waiting for commital. > > > Does it write before or after a successful execution or > commit the statement. Why a syntax error statement need to > hand over to Slave IO thread to relay log. If a syntax error happens on the master it should not show up in the bin log. > > > > Is there any control like any parameter in option file or > anything else in order to control to write only those > statements in binary log which ran successful on master. That's it's default behavior. > > > > Appreciate it. > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
