Mark Leith wrote:
Juan Eduardo Moreno wrote:
Hi,

I'm experience using expire_log_days and don't work. I set this parameters in the CNF and when the time of ( for example 5 days) is in, don't delete
anything.

On my expirience, this parameters don't work ( 5.0.27).

I am testing this now (on 5.0.40) and will see how it works out.

OK initial testing of this has shown no problems with the rolling over that happens when the server starts/stops:

medusa:/usr/local/mysql/data root# ls -l
total 41024
-rw-rw----    1 mysql  wheel   5242880 May  5 22:34 ib_logfile0
-rw-rw----    1 mysql  wheel   5242880 May  2 22:27 ib_logfile1
-rw-rw----    1 mysql  wheel  10485760 May  5 22:34 ibdata1
-rw-rw----    1 mysql  wheel       117 May  5 22:33 medusa-bin.000002
-rw-rw----    1 mysql  wheel       117 May  5 22:34 medusa-bin.000003
-rw-rw----    1 mysql  wheel       117 May  5 22:34 medusa-bin.000004
-rw-rw----    1 mysql  wheel        98 May  5 22:34 medusa-bin.000005
-rw-rw----    1 mysql  wheel       160 May  5 22:34 medusa-bin.index
-rw-rw----    1 mysql  wheel      6051 May  5 22:34 medusa.err
-rw-rw----    1 mysql  wheel         5 May  5 22:34 medusa.pid
drwxr-x---   53 mysql  wheel      1802 May  2 22:26 mysql
drwxr-x---    2 mysql  wheel        68 Apr 21 06:09 test
medusa:/usr/local/mysql/data root# mysqladmin -u root shutdown
medusa:/usr/local/mysql/data root# date
Sat May  5 22:35:07 BST 2007
medusa:/usr/local/mysql/data root# date
Wed May  9 22:35:24 BST 2007
medusa:/usr/local/mysql/data root# ../bin/mysqld --user=mysql &
[1] 1867
medusa:/usr/local/mysql/data root# 070509 22:35:53 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql-enterprise-gpl-5.0.40-osx10.4-i686/data/ is case insensitive 070509 22:35:53 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=/usr/local/mysql-enterprise-gpl-5.0.40-osx10.4-i686/data/medusa-bin' to avoid this problem.
070509 22:35:53  InnoDB: Started; log sequence number 0 43655
070509 22:35:54 [Note] ../bin/mysqld: ready for connections.
Version: '5.0.40-enterprise-gpl-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Enterprise Server (GPL)

medusa:/usr/local/mysql/data root# ls -l
total 41000
-rw-rw----    1 mysql  wheel   5242880 May  9 22:35 ib_logfile0
-rw-rw----    1 mysql  wheel   5242880 May  2 22:27 ib_logfile1
-rw-rw----    1 mysql  wheel  10485760 May  5 22:35 ibdata1
-rw-rw----    1 mysql  wheel        98 May  9 22:35 medusa-bin.000006
-rw-rw----    1 mysql  wheel        75 May  9 22:35 medusa-bin.index
-rw-rw----    1 mysql  wheel      6341 May  5 22:35 medusa.err
-rw-rw----    1 mysql  wheel         5 May  9 22:35 medusa.pid
drwxr-x---   53 mysql  wheel      1802 May  2 22:26 mysql
drwxr-x---    2 mysql  wheel        68 Apr 21 06:09 test

The only other one to test now is test that this also happens when a binary log rolls over.

Do keep in mind that expire_logs_days only gets triggered at a) server start up b) the time a binary log has to roll over.

If your binary logs do not roll over for quite a period of time (i.e are lower load systems) that still stay up for long periods - you might not see a log expired for some period.

Anyway, I'll still check out binary log rollover as well..

Cheers,

Mark

--
Mark Leith, Support Engineer
MySQL AB, Worcester, England, www.mysql.com
Are you MySQL certified?  www.mysql.com/certification


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to