Re: InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
At 11:34 AM +1100 12/4/06, Daniel Kasak wrote: Paul DuBois wrote: At 10:57 AM +1100 12/4/06, Daniel Kasak wrote: Carlos Proal wrote: Daniel, innodb data files keep growing as needed, it even be of 20Gb or more. I was under the impression that you should avoid files > 2GB on 32 bit systems, which have to do some dodgy stuff to support files bigger than 2GB. Does this advice apply? If you want several data files (mainly because performance) you need to add them in the my.cnf following the instructions in: 14.2.7. Adding and Removing InnoDB Data and Log Files http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html Yeah I've been reading that. It says that if we have an autoextend file ( which we do ), then it's current size ( around 500MB now ) will be the limit for all subsequent autoextend files. I'd like to be able to set a limit of 1 That's not how I read it. How did you draw this conclusion? OK. Upon 2nd reading, it seems like I was wrong. The size of the current autoextend file only affects the final size of *that* ibdata file; not Yes, that's right. subsequent ones. So therefore I can do something like: innodb_data_file_path = ibdata1:512M;ibdata2:1024M;ibdata3:1024M;ibdata4:1024M ... all the way to 30 of them :) Yes, if you like. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
Paul DuBois wrote: At 10:57 AM +1100 12/4/06, Daniel Kasak wrote: Carlos Proal wrote: Daniel, innodb data files keep growing as needed, it even be of 20Gb or more. I was under the impression that you should avoid files > 2GB on 32 bit systems, which have to do some dodgy stuff to support files bigger than 2GB. Does this advice apply? If you want several data files (mainly because performance) you need to add them in the my.cnf following the instructions in: 14.2.7. Adding and Removing InnoDB Data and Log Files http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html Yeah I've been reading that. It says that if we have an autoextend file ( which we do ), then it's current size ( around 500MB now ) will be the limit for all subsequent autoextend files. I'd like to be able to set a limit of 1 That's not how I read it. How did you draw this conclusion? OK. Upon 2nd reading, it seems like I was wrong. The size of the current autoextend file only affects the final size of *that* ibdata file; not subsequent ones. So therefore I can do something like: innodb_data_file_path = ibdata1:512M;ibdata2:1024M;ibdata3:1024M;ibdata4:1024M ... all the way to 30 of them :) Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
At 10:57 AM +1100 12/4/06, Daniel Kasak wrote: Carlos Proal wrote: Daniel, innodb data files keep growing as needed, it even be of 20Gb or more. I was under the impression that you should avoid files > 2GB on 32 bit systems, which have to do some dodgy stuff to support files bigger than 2GB. Does this advice apply? If you want several data files (mainly because performance) you need to add them in the my.cnf following the instructions in: 14.2.7. Adding and Removing InnoDB Data and Log Files http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html Yeah I've been reading that. It says that if we have an autoextend file ( which we do ), then it's current size ( around 500MB now ) will be the limit for all subsequent autoextend files. I'd like to be able to set a limit of 1 That's not how I read it. How did you draw this conclusion? or 2 GB, instead of 500MB, for each file. Maybe I'm being a bit nit-picky, but it would be nice. The only thing I can think of at the moment is to import stuff in lots of little bits and pieces, and when my ibdata1 file gets to around 1GB, I shut down MySQL, define a whole heap of other ibdata files in /etc/mysql/my.cnf, delete the log files, and the restart MySQL. -- Paul DuBois, MySQL Documentation Team Madison, Wisconsin, USA MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
Carlos Proal wrote: Daniel, innodb data files keep growing as needed, it even be of 20Gb or more. I was under the impression that you should avoid files > 2GB on 32 bit systems, which have to do some dodgy stuff to support files bigger than 2GB. Does this advice apply? If you want several data files (mainly because performance) you need to add them in the my.cnf following the instructions in: 14.2.7. Adding and Removing InnoDB Data and Log Files http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html Yeah I've been reading that. It says that if we have an autoextend file ( which we do ), then it's current size ( around 500MB now ) will be the limit for all subsequent autoextend files. I'd like to be able to set a limit of 1 or 2 GB, instead of 500MB, for each file. Maybe I'm being a bit nit-picky, but it would be nice. The only thing I can think of at the moment is to import stuff in lots of little bits and pieces, and when my ibdata1 file gets to around 1GB, I shut down MySQL, define a whole heap of other ibdata files in /etc/mysql/my.cnf, delete the log files, and the restart MySQL. Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
Daniel, innodb data files keep growing as needed, it even be of 20Gb or more. If you want several data files (mainly because performance) you need to add them in the my.cnf following the instructions in: 14.2.7. Adding and Removing InnoDB Data and Log Files http://dev.mysql.com/doc/refman/5.0/en/adding-and-removing.html Hopes this help. Carlos On 12/3/06, Daniel Kasak <[EMAIL PROTECTED]> wrote: Hi all. I'm about to import a LOT of data ( 20 GB ) into some InnoDB tables. At the moment, I have: innodb_data_file_path = ibdata1:10M:autoextend in my /etc/mysql/my.cnf The ibdata1 file is 499MB at the moment. What happens when this goes past 2GB? Do I automatically get allocated another, ibdata2, or something, or do I have to manually add one by shutting down MySQL, adding the extra file to the line above, and restarting? Dan -- 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]
InnoDB: What happens when a single AUTOEXTEND file goes past 2GB?
Hi all. I'm about to import a LOT of data ( 20 GB ) into some InnoDB tables. At the moment, I have: innodb_data_file_path = ibdata1:10M:autoextend in my /etc/mysql/my.cnf The ibdata1 file is 499MB at the moment. What happens when this goes past 2GB? Do I automatically get allocated another, ibdata2, or something, or do I have to manually add one by shutting down MySQL, adding the extra file to the line above, and restarting? Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
