On Di, 1999-07-13 14:26:19 +0300, Sinisa Milivojevic wrote:
> > > One of the most elegant backup strategy would be to lock all tables
> > > for read. This will wait until all other threads finish their updating
> > > of all tables, and will put them in waitings for other new
> > > writes.Then, in the same thread, mysqldump should be run, with -e and
> > > -q options, piped optionally through gzip stream to backup
> > > device. Then UNLOCK of the tables should be performed.
> After reviewing what I wrote, I concluded that LOCKS are NOT
> necessay. You can run mysqldump so that it does all the locking /
mysqldump --opt ...
should do all the work. It this what you meant?
Running "mysqldump --help" says that "--opt" is the same as "--quick
--add-drop-table --add-locks --extended-insert --lock-tables", the
latter doing the locking necessary for data consistency.
Martin Ramsch <m.ramsch@stripped> <URL: http://home.pages.de/~ramsch/ >
PGP KeyID=0xE8EF4F75 FiPr=52 44 5E F3 B0 B1 38 26 E4 EC 80 58 7B 31 3A D7