Hi.
As Shawn Green said: "I read through every TODO listed in the manual and didn't see it there. I also queried the Bugs list looking for any other issue or feature requests that were similar but didn't find any others. So, I assume that the problem is still in the analysis phase (or is still waiting to be analyzed) and once that is finished, the development team will make a choice of whether or not to implement the suggestion. When that decision occurs, there could be a note added to the Bug (feature request) explaining the decision (especially if the decision was "no")." Also he pointed me to http://bugs.mysql.com/bug.php?id=6256. Thanks to Shawn for good advices. Arvind Gangal <[EMAIL PROTECTED]> wrote: > Hello, > I understand that the slave executes the sqls from binlog in sequence, but > are there any plans to make it multi-threaded so that it executes multiple > sqls from binlog. > Thanks > Arvind. > > -----Original Message----- > From: Gleb Paharenko [mailto:[EMAIL PROTECTED] > Sent: 08 November 2004 13:02 > To: [EMAIL PROTECTED] > Subject: Re: Sequencial Replication > > Hello. > > MySQL slave receives all updates, but executes them in queue. > More about implementation of replication you can read at: > http://dev.mysql.com/doc/mysql/en/Replication_Implementation_Details.html > > > Arvind Gangal <[EMAIL PROTECTED]> wrote: >> Hi Gurus, >> >> As I understand the slave replicates with the master reading one query >> at a time from the binlog files. >> >> And at times the slave comes across a long update query and unless >> this has completed it will not pick up the next sql even though the >> other sql is on other table or may be another database. >> >> Is there a mechanism of running multiple sql slave threads in order to >> keep slave in sync to the master to the max. >> >> I reckon this would mean remembering multiple positions on the binlog. >> >> TIA >> Arvind Gangal >> http://www.lastminute.com >> >> >> >> >> >> ********************************************************************** >> This email and any files transmitted with it are confidential and >> intended solely for the use of the individual or entity to whom they >> are addressed. If you have received this email in error please notify >> the system manager. >> >> This footnote also confirms that this email message has been swept by >> MIMEsweeper for the presence of computer viruses. >> >> www.mimesweeper.com >> ********************************************************************** >> >> >> ______________________________________________________________________ >> __ This e-mail has been scanned for all viruses by Star. The service >> is powered by MessageLabs. For more information on a proactive >> anti-virus service working around the clock, around the globe, visit: >> http://www.star.net.uk >> ______________________________________________________________________ >> __ >> > > > -- > For technical support contracts, goto https://order.mysql.com/?ref=ensita > This email is sponsored by Ensita.NET http://www.ensita.net/ > __ ___ ___ ____ __ > / |/ /_ __/ __/ __ \/ / Gleb Paharenko > / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] > /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET > <___/ www.mysql.com > > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
