Jeff Smelser wrote:
On Wednesday 02 November 2005 02:23 pm, kashani wrote:
Because once you start caring about your db that much it's usually
easier to setup a crap box that replicates off your master. Then you can
lock the whole db on your slave and do a mysqldump without causing
issues on your main db regardless of which table type you're using. You
also get the added benefit of a hot backup and no I/O hits on the main db.
No, thats unfeasable.. Your talking about little DB's.. I have a 300+ gig
dbs's here and replication isnt the answer. Specially considering it is
statement level over row level.
Don't think you could have brought up the fact that you're complaining
about the shortcomings of Mysql in an entirely different class than I
and likely the original poster were talking about? I'd have wanted to
know a bit more about the setup before attempting to needlessly
complicating everything.
So yes, if your db is 20 GB or less, what I mentioned will probably
work without too much trouble. If your db is 100 GB or larger, you're
likely spending enough on hardware and software to solve your issues
that some vendor will offer to buy you flaming Tiki drinks so it's not
all bad.
kashani
--
gentoo-user@gentoo.org mailing list
