We are trying to move over to InnoDB, but we have a few problems that we just can't figure out:
First, for some reason, MySQL claims it can not claim more than .5Gigs of RAM from a system that has 4Gigs of RAM total and not being used for anything but MySQL.
Secondly, MySQL replication leaves a problem for our data warehouse and replication. When you use MySQL binary replication, it has been my experience that it is all or nothing. You can't choose just one database to replicate. You can start or stop just one database on the slave from being replicated. If you stop one, they all stop. This is a problem, because what we need to do is stop replication at midnight, and then do a dump of the database. Just one of them. When we stop it now, they all stop so now we have databases that are idle and not getting up to date replication while this one database gets mysqldumped for hours. InnoDB hot backup is a swell thing, but it doesn't dump the database in a useable format for anything except bringing an entire server online. This doesn't help us when we just want a simple mysqldump file of one database to do data warehouse work.
Before, what we did with MyISAM was a crude but workable in house replication system that used the text file update logs to replicate to a slave. This allowed us to replicate by database, and in turn only affect that one database for replication and dumping. It also allowed us to attach a data warehouse program to the replication so that it could grab the information it needed. With MySQL binary replication, we can not do either of these activities.
So, in a nutshell, this is our problems with InnoDB. I really want to get these problems fixed so I can keep InnoDB around, and use that nice hot backup program. It would be painful to have to stick with MyISAM.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
