11 messages in com.mysql.lists.bugsRE: More on replication ..
FromSent OnAttachments
Weslee Bilodeau08 Sep 2000 14:46 
sas...@mysql.com09 Sep 2000 20:27 
Thimble Smith11 Sep 2000 06:39 
sas...@mysql.com12 Sep 2000 14:12 
sas...@mysql.com12 Sep 2000 17:20 
Weslee Bilodeau12 Sep 2000 19:56 
Michael Widenius13 Sep 2000 01:03 
Michael Widenius13 Sep 2000 01:13 
Benjamin Pflugmann23 Sep 2000 19:24 
sas...@mysql.com25 Sep 2000 08:26 
sas...@mysql.com04 Oct 2000 17:32 
Subject:RE: More on replication ..
From:Michael Widenius (mon@mysql.com)
Date:09/13/2000 01:13:15 AM
List:com.mysql.lists.bugs

Hi!

"Weslee" == Weslee Bilodeau <sha@sell.com> writes:

Just a note (I assume Sasha will give a longer answer :)

<cut>

Weslee> And out of curiosity - Would it be possible to have a 'FLUSH TABLES WITH Weslee> WRITE LOCK', Weslee> so that I can stop the writes on the master while I'm moving tables, but
not Weslee> stop the Weslee> selects - Or is this making things more of a mess for things that will
get Weslee> easier later on? Weslee> Its not that big of a deal as the master has few selects being sent to
it.

The FLUSH TABLES WITH READ LOCK means exactly the above; It makes a READ LOCK on all tables, which means that other threads can search on the tables but updates will wait until the lock is released.

<cut>

Regards, Monty