Hi,
I found the same thing running v4.1.9. To make it work I first had to
issue:
PURGE MASTER LOGS TO 'logfilename'
...only then was I was able to use the 'BEFORE' variant i.e.
PURGE MASTER LOGS BEFORE DATE_SUB(NOW(), INTERVAL 10 DAY);
The first one must resync some sort of log index file or
Hello.
> Absolutely nothing happens
It works for me in 4.1.13. See:
[EMAIL PROTECTED] mysql-debug-4.1.13-pc-linux-gnu-i686]$ ls -l ../logs/log_r
total 12
-rw-rw 1 gleb gleb 1095 Aug 12 00:04 log_r.02
-rw-rw 1 gleb gleb 79 Aug 17 17:19 log_r.03
-rw-rw 1 gle
SHOW MASTER STATUS will show you where you currently are on the master.
You should connect to each slave, and do a SHOW SLAVE STATUS to find where
the slaves are, and delete the logs lower than the lowest one in use by
the slaves.
Luis Mediero wrote:
Hi,
I'm looking for an automatic method to
I found the problem ! The command is case sensitive also on WINDOWS . I
wrote the command as upcase and all is ok.
- Original Message -
From: "Massimo Petrini" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 29, 2002 12:33 PM
Subject: PURGE MASTER LOGS
>
>
> > In my
