Just installed MaxSQL 3.23.38 on a test system to check out InnoDB. Here are my
observations:
1) Manual is not clear on permissions of directories - They should be mysql.root
owned. The error in the error log just says cannot create file. This could be one of
many things! I had to use my initiative, but newbie user will never pick this up.
2) The error logs format is not consistent across InnoDB and normal Mysql:
010514 17:11:32 mysqld started
InnoDB: Error in creating or opening /data/ibdata/ibdata1
InnoDB: Could not open data files
010514 17:11:33 Can't init databases
010514 17:11:33 mysqld ended
This makes it almost impossible to do something useful (like parse) the log file.
3) Initial data file creation is VERY slow. I am still waiting after 15 minutes for
the first file to complete - It is only 606megs now. I have two files. What happens if
you run out of table space and quickly need to create more extents? Shutting down the
database does not sound like a good option in a mission critical 24/7 environment.
This is on a linux Redhat 6.2 (latest patches) box with Raid 5 disks on an IBM
Serveraid controller.
4) Ok, datafiles created overnight. Now trying alter table ... type=innodb on a file
with 1.2mil records. Still waiting after about 12 hours. Dumping files this size is
going to be problematic. Machine pegs with load of around 12! I suggest LOTS more
testing on BIG tables. Small stuff normally works quite well, but HUGE tables is where
it counts.
Thanks for the help.
PS: I am willing to test stuff on my development machine.
--
Richard Ellerbrock
[EMAIL PROTECTED]
---------------------------------------------------------------------
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
