>> The options for handling this are: >> #1 causes concurrency issues on the master. MySQL suffers >> from this same problem, and they note it in the documentation >> as a disadvantage of using the RBR format: >> >> http://dev.mysql.com/doc/refman/5.1/en/replication-sbr-rbr.html >> >> #2 does not suffer from the concurrency issue of #1, but it does >> mean marginally more work for TransactionApplier implementers >> to buffer GBP messages until the end Transaction message is >> read.
#2. It seems to me that the amount of time the TransactionAppliers implementers would spend on this is radically smaller then users would spend battling the issues #1 brings along. I wonder though what the risk is of those TA implementers to do their implementation wrong/suboptimal? Disclaimer: I'm no expert on this topic by any means. Just going on what seems to make sense from the info in this topic and some good ol' common sense :) cheers, -- Walter Heck -- Checkout my new startup: Server Monitoring as a Service @ http://tribily.com _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
