Dan Wilga wrote:
I've been running with InnoDB for the last year; IMHO more reliable in
case of system crashes where MyISAM tables tend to corrupt more easily
(esp. recordmarkup).
I run a high-volume web site that uses MySQL for some pretty frequent
tasks, and haven't had any data corruption problems.
I found my problem, but I'm not sure how to fix it. Every sunday morning
I shut down my
MySQL database and analyze and repair all tables. This is a trick I
learned from my production
Sys Admin days with MySQL versions 3.23.x.
Unfortunately, it looks like the Gentoo /etc/init.d/mysql doesn't shut
down the database properly.
So I get errors. Ugh. Oh well, INNODB won't solve that. I just need to
fix the shutdown proceedure
I guess.
--
Jesse Guardiani
Programmer/Sys Admin
[EMAIL PROTECTED]
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
