There seem to be some operations that cannot be performed on the
server whie InnoDB is doing something.
For example I inserted about 200,000 rows in to a table from
a file (mysql database < file) the file starts with begin; and
contains many inserts, I cancelled (ctrl-c) in the middle of the
operation which caused InnoDB to rollback (as expected) but
the mysql database whas unresponsive for about 10 minutes while
innoDB did the rollback. The server would not respond to any
processlist requests, connections or anything. This is not so good
for the increased read/write concurrency expected from innodb.
Also.. If a new table space has been added, it can take a while
for innoDB to format 1Gig of tablespace (a long while on a 400mhz
pentium). Is there a reason why the whole mysql database must
be unresponsive durring this time? Why can't the system only lock
out InnoDB format tables if need be and allow MySQL to startup and
respond to questions.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
