List:General Discussion« Previous MessageNext Message »
From:Jeremy Zawodny Date:May 14 2004 9:25pm
Subject:Re: OPTIMIZE TABLE and mySQL replication
View as plain text  
On Fri, May 14, 2004 at 03:26:28PM -0500, Donny Simonton wrote:
> Actually, if you are using 4.1.1 optimize table does get passed to the
> slave.  This is from the 4.1.1 change log.
> 
> ANALYZE TABLE, OPTIMIZE TABLE, REPAIR TABLE, and FLUSH statements are now
> stored in the binary log and thus replicated to slaves. This logging does
> not occur if the optional NO_WRITE_TO_BINLOG keyword (or its alias LOCAL) is
> given. Exceptions are that FLUSH LOGS, FLUSH MASTER, FLUSH SLAVE, and FLUSH
> TABLES WITH READ LOCK are not logged in any case. For a syntax example, see
> section 14.5.4.2 FLUSH Syntax.

Ugh.  That's the *default*?

Gee, that won't surprise anyone, I'm sure...

:-(
-- 
Jeremy D. Zawodny     |  Perl, Web, MySQL, Linux Magazine, Yahoo!
<Jeremy@stripped>  |  http://jeremy.zawodny.com/

[book] High Performance MySQL -- http://highperformancemysql.com/
Thread
OPTIMIZE TABLE and mySQL replicationJim14 May
  • Re: OPTIMIZE TABLE and mySQL replicationDan Nelson14 May
    • Re: OPTIMIZE TABLE and mySQL replicationDan Nelson14 May
  • Re: OPTIMIZE TABLE and mySQL replicationJeremy Zawodny14 May
    • RE: OPTIMIZE TABLE and mySQL replicationDonny Simonton14 May
    • Re: OPTIMIZE TABLE and mySQL replicationJim14 May
Re: OPTIMIZE TABLE and mySQL replicationJeremy Zawodny14 May
  • Re: OPTIMIZE TABLE and mySQL replicationDan Nelson14 May
    • Re: OPTIMIZE TABLE and mySQL replicationJeremy Zawodny14 May
  • RE: OPTIMIZE TABLE and mySQL replicationDonny Simonton14 May
  • RE: OPTIMIZE TABLE and mySQL replicationDonny Simonton14 May