Sergei, I don't know much about innodb, but myisam doesn't have a 4 gig limit unless you are using a dynamic type of table. If you are using a fixed table which is by using int, char, etc... Not text, varchar, blobs.
As long as you don't use the last ones, you don't have a 4 gig limit. As far as your questions about innodb, can't help you there. Except for in my case when I have switched tables to innodb, I copy them in chunks to speed up the process. That's what it says on the innodb website, so that's what we did. Donny > -----Original Message----- > From: Sergei Skarupo [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 8:36 PM > To: Mysql List (E-mail) > Subject: table conversion problems > > Hi all, > > Started a conversion from MyISAM to InnoDB; it's been almost two days and > the statement is still executing... > > The (MyISAM) data table size is almost 4G. There were two reasons for this > conversion: to start supporting transactions and to avoid the 4G limit of > MyISAM tables; this table has been created without explicitly specifying > MAX_ROWS and AVG_ROW_LENGTH. > > The avg row length is 28 bytes, there's only a primary key comprised of 3 > integers. > > The state of this thread that's performing the conversion is "Copy to tmp > table". > > We need to start updating the table as soon as possible... > > Is there a way to monitor the progress? > Is the tmp table allocated in InnoDB tablespace? > What are the consequences of killing the thread? Will it waste whatever > InnoDB tablespace has been already used for this conversion? > I'm using Mysqlcc. How long may it take to cancel this statement by > pushing "Cancel execution and clear > results" button? Sometimes it takes a while... What does this button > actually do? > > Thanks in advance for your help! > > -- Sergei -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
