Jigal,
----- Alkuperäinen viesti ----- Lähettäjä: "Jigal van Hemert" <[EMAIL PROTECTED]>
Vastaanottaja: <mysql@lists.mysql.com>
Kopio: "Gleb Paharenko" <[EMAIL PROTECTED]>; "Heikki Tuuri" <[EMAIL PROTECTED]>
Lähetetty: Tuesday, April 26, 2005 2:09 PM
Aihe: Fw: modifying InnoDB storage
Unfortunately no response from the list anymore :-(
Can we ever get rid of the autoexpanding ibdata file without completely rebuilding the databases?
unfortunately no. ibdata files cannot be removed or truncated.
You should consider using
innodb_file_per_table
if disk space is sparse.
Regards, Jigal.
Best regards,
Heikki
Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
Order MySQL Network from http://www.mysql.com/network/
----- Original Message ----- From: "Jigal van Hemert" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Wednesday, April 20, 2005 12:31 PM
Subject: Re: modifying InnoDB storage
/ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ibFrom: "Gleb Paharenko"
Hi Gleb,
Thanks for your response.
> http://dev.mysql.com/doc/mysql/en/adding-and-removing.html
If it currently reads: innodb_data_file_path =
/ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ibdata4:10M:autoextend
Can you change this into: =
/ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ibdata4:2000M;/ibdata/ibdata5:10M:autoexten or =
data5:2000M;/ibdata/ibdata4:10M:autoexten ???
> Think also about per-table tablespaces. See:
Sorry, it's still 4.0.x that our sysadmin wants...
Regards, Jigal.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]