Re: innodb replication

[Ed W]

>> How would you put these two things together in the case of a server 
>> using mixed database table types for a clean backup that can be used 
>> to restart synchronisation?
>
>
> You can't. Only InnoDB supports single-transaction, so though it would 
> still generate a dump file for other table types, you'd have no 
> assurance that they are clean because writes could be happening as you 
> do it. This is one of the advantages of using innodb.

Would

mysqldump --master-data --lock-all-tables

work..?  I guess although the read lock doesn't stop innodb writing and 
starting transactions, those transactions will be written after the 
noted commit point in the log files?  I guess the problem is if the dump 
reads uncommitted transaction data or the transaction can commit in some 
way despite the read lock?

> You can of course do separate dumps for other DBs, and because that 
> wouldn't need to include the innodb tables, it would at least reduce 
> the time that your tables are locked.

Sure - although technically then you don't have a consistent dump 
between table types...

> You could also look at maatkit's parallel dump/load scripts.

Will do.  Thanks

Ed W