handling mysql binlog data

[Zbigniew Szalbot]

Hello,




-rw-rw----  1 mysql  mysql    61956466 Apr 16 08:44 mysql-bin.000001
-rw-rw----  1 mysql  mysql   697756219 Apr 17 14:26 mysql-bin.000002
-rw-rw----  1 mysql  mysql        1056 Apr 17 14:29 mysql-bin.000003
-rw-rw----  1 mysql  mysql  1073745860 Apr 24 05:49 mysql-bin.000004
-rw-rw----  1 mysql  mysql   620489997 Apr 27 10:48 mysql-bin.000005
-rw-rw----  1 mysql  mysql   229357379 Apr 28 15:55 mysql-bin.000006
-rw-rw----  1 mysql  mysql   869964294 May  2 14:15 mysql-bin.000007



Many thanks for sharing!
--
Zbigniew Szalbot
www.lc-words.com

Following a recent thread I would like to ask if it is safe to remove old binlog data. From the below I understand that the current binlog is mysql-bin.000007 and the previous ones (from 000001-000006) are not written to any more. I just need confirmation before I take any action. By asking whether it is safe, I only mean if deleting them will not affect mysql operation. I do backups of mysql data anyway. Do I understand correctly that removing mysql-bin.000007 would result in mysql not writing any data to mysql-bin file until the server gets restarted?

smime.p7s
Description: S/MIME Cryptographic Signature