On Tue, 04 Sep 2012 00:39:08 +0200 Reindl Harald <h.rei...@thelounge.net> wrote:
> Am 03.09.2012 23:56, schrieb Titanus Eramius: > > > > MySQL Replication, which seems a bit dodgy, with the risk of silent > > data corruption. > > where do you see a risk of silent data corruption? > > if htis would be the case it would be simply > impossible have a omplete dbmail-database running > on a replication salve over 3 years with a lot of > foreign constraints and a major scheme update > > there is BO silent corruption > please do not post FUD I'm somewhat sorry for being unable to ask my question in a manner that can't be misunderstood, but I suppose it's always possible to find someting negative if you are looking for it. Like I said "I've been reading up on the subject, but seems to lack the experince ..." which should be understood as I don't know anything about the subject besides what I have read. Like this http://www.iheavy.com/2012/04/26/bulletproofing-mysql-replications-with-checksums/ And this http://www.xaprb.com/blog/2007/11/08/how-mysql-replication-got-out-of-sync/ (which I found here http://forums.mysql.com/read.php?27,216438,216438 ) And so on http://www.pythian.com/news/1273/mysql-replication-failures/ So I'm sorry, I don't see the FUD, and because I know next to nothing about databases, I simply can not see these replication errors as anything else than corruption*. But please enlighten me, that was why I posted to the list. --- * "Data corruption refers to errors in computer data that occur during writing, reading, storage, transmission, or processing, which introduce unintended changes to the original data." https://en.wikipedia.org/wiki/Data_corruption
