5 messages in com.mysql.lists.win32Re: Power down| From | Sent On | Attachments |
|---|---|---|
| Daniel Hägg | 07 Nov 2002 02:10 | |
| Alan McDonald | 07 Nov 2002 02:15 | |
| Daniel Hägg | 07 Nov 2002 03:55 | |
| Charles Burnaford | 07 Nov 2002 05:47 | |
| Daniel Hägg | 07 Nov 2002 06:28 |
| Subject: | Re: Power down |
|---|---|
| From: | Daniel Hägg (dani...@factum.se) |
| Date: | 11/07/2002 06:28:21 AM |
| List: | com.mysql.lists.win32 |
I have thought about it, but I didn't really think it would be practical, considering performance and memory requirement. We are talking about rougly 50 Mb of data. Doesn't INNODB need alot of RAM?
/ / Daniel
Charles Burnaford wrote:
Get the current version 3.23.49 and create the tables needed using the INNODB table type. Make sure that the default setting for Autocommit is One (1). INNODB is transaction safe and with Autocommit on you will get the ability rollback the incomplete entries and hopefully you won't have to repair the db as often.
Charles Burnaford cr...@nb.net
----- Original Message ----- From: "Daniel Hägg" <dani...@factum.se> To: <win...@lists.mysql.com> Sent: Thursday, November 07, 2002 5:10 AM Subject: Power down
Hi! We are using MySQL on NT 4.0 for storing system log messages. The log messages are pouring in more or less continusly. We have found
that
after a power failure the database in which the logs are stored are very often broken (maybe 1 times out of 3). Currently we solve this problem by telling our customers to manually stop MySQL and run "myisamchk --safe-recover". This helps most of the time. However, our customers are not very found of having to do things manually. Any thoughts on how we can improve things ?
/ / Daniel