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? Regards, Jigal. - 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 From: 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/ib data4:10M:autoextend Can you change this into: = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib data4:2000M;/ibdata/ibdata5:10M:autoexten or = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib 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]
Re: modifying InnoDB storage
Jigal, - Alkuperinen viesti - Lhettj: Jigal van Hemert [EMAIL PROTECTED] Vastaanottaja: mysql@lists.mysql.com Kopio: Gleb Paharenko [EMAIL PROTECTED]; Heikki Tuuri [EMAIL PROTECTED] Lhetetty: 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 From: 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/ib data4:10M:autoextend Can you change this into: = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib data4:2000M;/ibdata/ibdata5:10M:autoexten or = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib 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]
Re: Fw: modifying InnoDB storage
Hello. According to this: If your last data file was defined with the keyword autoextend, the procedure to edit my.cnf must take into account the size to which the last data file has grown. You have to look at the size of the data file, round the size downward to the closest multiple of 1024 * 1024 bytes (= 1MB), and specify the rounded size explicitly in innodb_data_file_path. Then you can add another data file. I think you can. Jigal van Hemert [EMAIL PROTECTED] wrote: Unfortunately no response from the list anymore :-( Can we ever get rid of the autoexpanding ibdata file without completely rebuilding the databases? Regards, Jigal. - Original Message --- -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
modifying InnoDB storage
Hi list, If you have the InnoDB tablespace files defined as two files of 2GB and an autoextend file, is there any way to add extra tablespace files in this case? Regards, Jigal. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: modifying InnoDB storage
Hello. See: http://dev.mysql.com/doc/mysql/en/adding-and-removing.html Think also about per-table tablespaces. See: http://dev.mysql.com/doc/mysql/en/multiple-tablespaces.html Jigal van Hemert [EMAIL PROTECTED] wrote: Hi list, If you have the InnoDB tablespace files defined as two files of 2GB and an autoextend file, is there any way to add extra tablespace files in this case? Regards, Jigal. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: modifying InnoDB storage
From: 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/ib data4:10M:autoextend Can you change this into: = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib data4:2000M;/ibdata/ibdata5:10M:autoexten or = /ibdata/ibdata1:2000M;/ibdata/ibdata2:2000M;/ibdata/ibdata3:2000M;/ibdata/ib 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]
