-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sehmuz Bayhan wrote: > What is wrong with the current syntax in MySQL that already gives us the > control over what needs to be replicated? REPAIR, OPTIMIZE and ANALYZE have > the [NO_WRITE_TO_BINLOG | *LOCAL*] option that disables replication for > those commands.
A lot is wrong with it. It's a) not generic, b) requires modification to the parser for something that is inherently a plugin's functionality, and c) embeds the word BINLOG and WRITE into the command, which means we tie *implementation specifics* to the *interface*, which is entirely against Drizzle's goals. Now, a solution such as this: SET @replicator.enabled= FALSE; /* do some commands... */ SET @replicator.enabled= TRUE; would be perfectly sensible to me. - -jay > Sehmuz > > On Wed, Apr 1, 2009 at 11:06 AM, Jeremy Zawodny <[email protected]> wrote: > >> On Tue, Mar 31, 2009 at 8:47 PM, Jay Pipes <[email protected]> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> All, >>> >>> 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. >>> >>> Oddly, CHECK TABLE is not replicated. ?. >> >> That doesn't seem odd at all to me. >> >> You use "CHECK TABLE" to see if a "REPAIR" is needed. If you end up >> needing to run the repair on your master, you may or may not want to run it >> on your slaves (and have that control). But I can't see a need to every >> blindly fire off "CHECK TABLE" commands at slaves. >> >> Can anyone else? >> >> >>> Question: Should any of these statements be replicated or sent to a >>> binary log? >> >> REPAIR, OPTIMIZE, and ANALYZE should. If I want to run them on the master >> only, I can use "SET SQL_LOG_BIN=0" to get that (though I wish there was a >> cleaner syntax to disable for ONLY the next command). >> >> >>> 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! >> >> It's very useful to have that option as a sever admin (or someone who tries >> to tell them what to do). >> >> Jeremy >> >> >> _______________________________________________ >> Mailing list: >> https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> >> Post to : [email protected] >> Unsubscribe : >> https://launchpad.net/~drizzle-discuss<https://launchpad.net/%7Edrizzle-discuss> >> More help : https://help.launchpad.net/ListHelp >> >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknTuo4ACgkQ2upbWsB4UtEZTACfTHbwQEFd5uCFJUyIUafCya+7 4swAniA8PrU4X9bVqfyqxq4an+x2wTKV =w1pE -----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
