Am 05.06.2011 23:49, schrieb ag...@airpost.net: > > On Sun, 05 Jun 2011 23:29 +0200, "Reindl Harald" > <h.rei...@thelounge.net> wrote: >> i would use a replication slave and stop him for consistent backups >> because dumb locks are not really a good solution independent >> if this works "normally" > > unfortunately, i have no idea what that means. > > something's apparently broken with mysqldump -- enough so that lots of > people are seeing and reporting this same error after the 5.1 -> 5.5 > upgrade. > > why would setting up a replication slave be necessary or a good solution > to the problem?
because there is no lock on any production table? have fun using mysqldump with really hughe databases :-) a replication slave is synchron, you can stop the slave, copy the whole datadir and after starting the slave it will make all changes from the binary log
signature.asc
Description: OpenPGP digital signature
