List:Replication« Previous MessageNext Message »
From:Simon J Mudd Date:December 13 2009 9:03am
Subject:Re: disabling replication and bin logs on MySQL v4
View as plain text  
rjames@stripped ("Rick James") writes:

> If you have no slaves, you don't need to write the binlogs.

That's not entirely true.

If you don't care about db recovery then you don't need the
binlogs. That is if you have a server crash and the db files get
corrupted the normal way to recover if you can't fix the files
yourself is to restore from an older backup and then reapply the
binlogs from that point until the server crash. This will end up
giving you the state of the server when the crash/damage took place.

If you stop using binlogs and have a "busy day" and run something like
"DROP DATABASE XXXX" then without binlogs or application logs to redo
the changes you lose all the data in between.

Whether this is an issue for your situation of course depends
on the usage, but advising that binlogs are not necessary unless
you need replication is not fully correct.

Simon
Thread
disabling replication and bin logs on MySQL v4Madison Kelly11 Dec
  • RE: disabling replication and bin logs on MySQL v4Rick James11 Dec
    • Re: disabling replication and bin logs on MySQL v4Madison Kelly11 Dec
      • Re: disabling replication and bin logs on MySQL v4Andrew Garner11 Dec
        • Re: disabling replication and bin logs on MySQL v4Madison Kelly11 Dec
    • Re: disabling replication and bin logs on MySQL v4Simon J Mudd13 Dec