Most likely, binary logs are populating the space.
Read http://dev.mysql.com/doc/mysql/en/PURGE_MASTER_LOGS.html
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ __
/ |/ /_
On Thu, 21 Oct 2004, C.F. Scheidecker Antunes wrote:
> Hello,
>
> On a further inspection and by reading Paul DuBois' I guess m y system
> has to many bin logs. How can I get ride of them?
Assuming you don't need them for replication or point-in-time recovery, you
can use the PURGE command.
http
Unless you're running InnoDB (with lots of data and indexes) I would assume
your trouble has to do with the fact that you are running I am running
4.0.20-Max-log. (Namely the "log" part) How large are the logs
in /var/lib/mysql?
j- k-
On Wednesday 20 October 2004 22:41, C.F. Scheidec
Hello,
On a further inspection and by reading Paul DuBois' I guess m y system
has to many bin logs. How can I get ride of them?
Thanks in advance,
C.F.
C.F. Scheidecker Antunes wrote:
Hello,
I have a server with 18Gb of space. I have ran du to figure out how
the harddrive is being used and I rea
Hello,
I have a server with 18Gb of space. I have ran du to figure out how the
harddrive is being used and I realized that the directory that is taking
the most space is /var/lib/mysql
I know that now I have much less database records than I used to have
and I have the same database structure h
