Hi!
I'm not a fan of embedding the replication control syntax in the
actual command. It makes everything not very modular. You can though
turn it off for a set number of commands (which can be packed into a
single TCP packet).
Cheers,
-Brian
On Apr 1, 2009, at 11:13 AM, 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.
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
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-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
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
