Hello. According to: http://dev.mysql.com/doc/refman/5.0/en/innodb-locks-set.html
INSERT ... SELECT set a non-next-key lock on each row. So in most cases you should be able to insert the record into Y. Please, provide the CREATE statement for table Y and the output of 'show variables' statement. In my opinion, the problem could be in keys, if they're present in the table. Include the output of SHOW PROCESSLIST and SHOW INNODB STATUS as well. Ady Wicaksono wrote: > I use MySQL 5.0.15 > > I have about 5 billion rows in table X, i create another table Y with > the same stucture with X > CREATE TABLE Y LIKE X; > > Both X and Y is the InnoDB table, since i believe that both work on the > "row locking" models > > I try to initiate 2 session > > First session try to INSERT all of data from X to Y like this > > INSERT INTO Y SELECT * FROM X; > > After a while (i need a long time to finish this Query), i start my > second session and try > to insert a data into Y > > What happened later make me confuse, because > > INSERT INTO Y VALUES (something) is just hang on, seems waiting another > operation to be finished > > Why concurrent insert is not working? > > FYI, i use standar configuration from MySQL > > Any explanation? > > Thx > > -- 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]
