On Fri, 2007-04-27 at 09:19 -0500, [EMAIL PROTECTED] wrote:
So if one is doing a full mysqldump every night, all bin-logs can be
deleted after this?
On the slave - Yes. In fact I would highly recommend it before
starting the slave processes again. This will reset the bin log's
'position'
So if one is doing a full mysqldump every night, all bin-logs can be
deleted after this?
If bin-logging is disabled, will master/slave syncing still occur?
David
Issuing a 'reset master' will purge all of the logs as well. I wouldn't
just rm them, as they are being tracked in the index
Running mysql 4, just poked into data and see I have gigs and gigs of
hostname-bin.xxx log files.
How does one maintain these, can someone point me to relevant data on what
to do about drive space being lost to these?
thanks
--
-
Scott
Hi,
Scott Haneda wrote:
Running mysql 4, just poked into data and see I have gigs and gigs of
hostname-bin.xxx log files.
How does one maintain these, can someone point me to relevant data on what
to do about drive space being lost to these?
thanks
See attached message I just sent to
In the short term, see the manual page for PURGE MASTER LOGS. In the
long term, write a cron job.
innotop (http://sourceforge.net/projects/innotop) also has a new
feature, unreleased because I just wrote it a few hours ago, which will
help you figure out which binlogs can be purged safely
Hi Scott,
Scott Haneda wrote:
In the short term, see the manual page for PURGE MASTER LOGS. In the
long term, write a cron job.
innotop (http://sourceforge.net/projects/innotop) also has a new
feature, unreleased because I just wrote it a few hours ago, which will
help you figure out which
Yes -- sorry for being so general. You can use the binlogs for a)
replication b) replaying changes since your last backup so you get
point-in-time recovery. If you have no replication slaves, just delete
everything older than your latest backup. You can just use 'rm'. If
you use PURGE
Issuing a 'reset master' will purge all of the logs as well. I wouldn't
just rm them, as they are being tracked in the index file.
If you aren't running a slave, then these files are only good for data
recovery purposes. Say a DBA goes crazy and deletes all of the databases
mid-day (too much
So, I take it since I do not have a slave at all, I could safely just
disable this feature altogether?
If I do not need point in time recovery, and the once every 12 hour dump I
do across all databases is ok with me, I suppose I can just disable said
feature? Heck, some of these boogers are a
