| List: | Commits | « Previous MessageNext Message » | |
| From: | Konstantin Osipov | Date: | June 19 2008 9:20pm |
| Subject: | Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | ||
| View as plain text | |||
* Chuck Bell <cbell@stripped> [08/06/17 16:49]: > #At file:///C:/source/bzr/mysql-6.0-bug-36749/ > > 2618 Chuck Bell 2008-06-17 > BUG#36749 Data Loss after Restore, if Trigger fired on the table that is being > Restored. > > The MyISAM native driver is not locking its tables. This results in data losson > restore > as either a collision or an overwrite condition occurs. > > This patch corrects the problem by taking an exclusive name lock on all tables > prior to > restore of the data (after the metadata step). So how is that an "online" backup if you take exclusive metadata locks? Or it's accepted that restore can be "offline"? > +/* > + Gets name locks on table list. > +*/ > +int get_name_locks(THD *thd, TABLE_LIST *tables, bool exclusive); What is this "exclusive" for? --
| Thread | ||
|---|---|---|
| • bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Chuck Bell | 17 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Jørgen Løland | 18 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Rafal Somla | 18 Jun |
| • RE: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Chuck Bell | 19 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Konstantin Osipov | 19 Jun |
| • RE: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Chuck Bell | 19 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | 'Konstantin Osipov' | 19 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Paul DuBois | 20 Jun |
| • RE: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Chuck Bell | 20 Jun |
| • Re: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Paul DuBois | 20 Jun |
| • RE: bzr commit into mysql-6.0-backup branch (cbell:2618) Bug#36749 | Chuck Bell | 20 Jun |
