You can do a reset master, and it will start the log over at 001 and remove
the old log files that are there.
Eric Gunnett
System Administrator
Zoovy, Inc.
[EMAIL PROTECTED]
>>> Jeff Smelser <[EMAIL PROTECTED]> 06/15/04 11:26AM >>>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I am trying to prune some bin-logs and noticed:
mysql> show master logs;
+------------+
| Log_name |
+------------+
| db-bin.001 |
| db-bin.002 |
| db-bin.003 |
| db-bin.004 |
| db-bin.005 |
| db-bin.006 |
| db-bin.007 |
| db-bin.008 |
| db-bin.009 |
| db-bin.010 |
| db-bin.011 |
| db-bin.012 |
| db-bin.013 |
| db-bin.014 |
| db-bin.015 |
| db-bin.016 |
| db-bin.017 |
| db-bin.018 |
| db-bin.001 |
| db-bin.002 |
| db-bin.003 |
| db-bin.004 |
+------------+
22 rows in set (0.01 sec)
I recently redid the replication and it restarted at 001.. Well the 001-018
doesn't exist on my server. So I get:
mysql> PURGE MASTER LOGS TO 'mysql-bin.004';
ERROR:
Target log not found in binlog index
How do I get rid of the 000-018 files that don't belong there?
Thanks,
Jeff
- --
If you're going to walk on thin ice, you may as well dance.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAzz9tld4MRA3gEwYRAjquAKDYbTb1XHZUhJ/V8KZssZUS3AlrBACgrLUH
mokZhloHPfIMBm9Txu2QmLk=
=CCMg
-----END PGP SIGNATURE-----
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
