Re: Replication Stopping at position before it started????

On 10 Oct 2007, at 19:13, Rick James wrote:

> Stopping the master before dumping is important because of un-flushed
> data sitting in various caches. Stopping clients to the master is
> probably not sufficient. FLUSH TABLES WITH READLOCK "should" be as
> good
> as stopping the master, but I don't trust it.

Something I'd like to have confirmed is whether (assuming that everything is in InnoDB) 'mysqldump --single-transaction --master- data' will produce a consistent dump suitable for loading up a slave. If so, it would make things much simpler, and remove the need to lock tables or deny access while extracting the data.

Marcus

-- 
Marcus Bointon
Synchromedia Limited: Creators of 
http://www.smartmessages.net/
UK resellers of info@hand CRM solutions
marcus(at)synchromedia.co.uk | 
http://www.synchromedia.co.uk/



-- 
MySQL Replication Mailing List
For list archives: 
http://lists.mysql.com/replication
To unsubscribe:    
http://lists.mysql.com/replication?unsub=lists@pantek.com