Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
Saving space disk (innodb)

Saving space disk (innodb)

2007-10-10       - By Dan Rogart

 Back
OPTIMIZE TABLE should reclaim that space, but be aware that it could
take a while to run (locking your table all the while) since it just
maps to an ALTER TABLE statement which creates a new copy of the table.
Depends on how big your tables are.

Doc:  http://dev.mysql.com/doc/refman/4.1/en/optimize-table.html


-Dan

-- --Original Message-- --
From: Tiago Cruz [mailto:tiagocruz@(protected)]
Sent: Wednesday, October 10, 2007 2:14 PM
To: mysql@(protected)
Subject: Saving space disk (innodb)

Hello guys,

I have one monster database running on MySQL 4.0.17, using InnoDB:

270GB Oct 10 14:35 ibdata1


I've deleted a lot of register of then, and I've expected that the size
can be decreased if 50% (135 GB) but the ibdata was the same value than
before "clean"...

How can I force to save this space?


set-variable    = innodb_buffer_pool_sizeP0M
set-variable    = innodb_additional_mem_pool_size0M
set-variable    = innodb_log_files_in_group=5
set-variable    = innodb_log_file_size0M
set-variable    = innodb_log_buffer_size=8M
set-variable    = innodb_flush_log_at_trx_commit=1
set-variable    = innodb_lock_wait_timeout=5

set-variable    = innodb_data_home_dir=/dbms/mysql/bin-4 (See http://bin-4.ora-code.com).0.17/var
set-variable    = innodb_data_file_path=ibdata1:1000M:autoextend
set-variable    = innodb_log_group_home_dir=/dbms/mysql/bin-4 (See http://bin-4.ora-code.com).0.17/var

Thanks!


--
Tiago Cruz
http://everlinux.com
Linux User #282636



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub?n.rogart@(protected)



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@(protected)