On Jul 23, 2005, at 11:56 AM, Dan Tappin wrote:
I am all most ready to give up on MySQL at this point. I'm still
getting regular table corruption on multiple installs of OS X.
I went as far as reporting it as a bug:
http://bugs.mysql.com/bug.php?id=12066
They seem to want more info but my requests for clarification have
gone unanswered.
Has your mysql crashed or have your restarted the machine without
first shutting down mysql manually? We only saw this error when
mysql was not shut down normally. You can look in your .err file
which should be in your data directory. Every mysql sartup sequence
should be preceded by a line saying "mysqld ended." If not it's
crashing and that's the issue to address.
2.) Try Innodb
This is a MyISAM error, but if mysqld is crashing or being shutdown
abnormally InnoDB too will have to go through a crash recovery at
startup (it's just automatic, but you'll see it in the .err file).
I have changed one of the tables that consistently gives my trouble
to Innodb. I will continue to watch for corruption.
Given that can anyone point out any big things to note about innodb
tables. I've read that they are in general better than myisam
tables but you loose the fulltext index option.
I think it's more that they are different. InnoDB has some
complexities related to backups and slightly different functionality,
and the number of tips on the Internet are much fewer than for
MyISAM. However, if you are doing lots of inserts with simultaneous
selects you really have to use InnoDB to get reasonable performance.
Is there a typical work around for this?? I typically only have
the odd tables that needs a full text search capability. I think
what I have seen was to create a dummy myisam table with just the
key and fields from the innodb table and add a fulltext index to
search against. It would just be a matter of keeping the tables
synced.
I think that's what most people do.
I am also wondering about back-ups. The docs seem to indicate that
you can still run mysqldump... but how does this effect restoring.
In my case I can afford to shutdown the server in the wee hours of
the morning and back-up the data dir manually.
1) Shut down and manually copy, but make sure you get all the InnoDB
parts...data files and transaction logs. One is pretty much useless
without the other.
2) mysqldump, look at the options. This with InnoDB is pretty nice
b/c you can use --single-transaction and get a point in time copy of
the table without disrupting other users. In particular the comments
on the mysql documentation page for mysqldump detail a good set of
flags for InnoDB.
3) The (non-free) ibbackup which takes a backup while running
without disturbing users
I don't think there's any fundamental issue with MySQL (either myisam
or innodb) on OS X, but I do think that MySQL is something that
doesn't do well when run only through Apple's front end. It has two
many options, configuration details, etc... if you are doing anything
more than a few small tables. Plus, if you are relying on it all
you'll want to be able to take advantage of bug fixes faster than
Apple's MySQL updates allow you too.
Fortunately, it's easy enough to download the mysql binary and use/
configure it independently. We've had quite good luck with MySQL on
OS X with a pretty big install, but there are a lot of details to
learn so it can seem tough to work out at times.
Good luck,
Ware
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
