-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Robson wrote: > 2009/4/1 Jay Pipes <[email protected]> > >> As I was hacking on the new replication code today, I noticed that >> Drizzle (and MySQL 6) is passing through REPAIR, OPTIMIZE, and ANALYZE >> TABLE statements as-is into the binlog and the replication stream. >> >> Should Drizzle replicate any administrative commands at all? >> Personally, I don't see the value in replicating them or storing them in >> a recovery log either...but...input is always welcome! > > I think there are lots of valid use-cases for replicating DDL statements, > especially the likes of ALTER TABLE and DROP TABLE. > > Some users will be programmatically creating, altering, dropping tables on a > regular basis, having these changes happen on the slave is very handy. > > Moreover, during schema migration, if the master is migrated and the slave > doesn't get migrated at exactly the right moment in the binlog, replication > (row-based or otherwise) will immediately break as the schemas won't match.
Hi Mark! I totally agree! However, I was asking about *administrative* commands, not DDL :) By administrative commands, I mean the ones in the subject line, and more. To be exact: OPTIMIZE TABLE ANALYZE TABLE CHECK TABLE REPAIR TABLE FLUSH RELOAD CHECKSUM BACKUP RESTORE RESET LOAD INDEX INTO CACHE KILL CACHE INDEX What about these? - -jay -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknTkh8ACgkQ2upbWsB4UtEEKgCfda3dmpMcJurS4TlmTTHy00kq yeUAnRcE8dOppqZ6FbD6AAD4hb47yKbq =zsBC -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
