MySQL tells me at startup that it can not allocate more than 512MB of RAM. It will fail to start the server if I specify any further.
As far as separate instances, we have not looked into doing that for the masters, but we may use that for the data warehouse copy. The idea of multiple MySQL master instances on the same box just doesn't sound friendly. Perhaps you have had better experience with this. Thanks for the tip on mysqlbinlog, but using that will require a lot of tweaking and development. It may prove useful though. What I did like about MySQL replication is that it is pretty simple. This simplicity however also causes the problem of wanting to replicate only one database at a time. Its not that we need separate replication, its that we want to be able to stop replication of one database and let the others continue while we do things to the stopped database. -----Original Message----- From: Jeremy Zawodny [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 2:11 PM To: Misao Cc: [EMAIL PROTECTED] Subject: Re: InnoDB, Replication, and Data warehouse: Oil, Water, and little floating plastic men On Mon, Sep 22, 2003 at 06:09:22PM -0700, Misao wrote: *snip* How does it make this claim? *snip* Have you considered running separate instances of MySQL, one for each database? *snip* Sure you can. Use the mysqlbinlog tool. It has a "-d" argument that will only show queries from the given database. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 10 days, processed 392,383,279 queries (417/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
