Client C - LOW PRIORITY inserts will always wait until absolutely no other processes are using a table.
----- Original Message ----- > From: "Jon Siebert" <jon.siebe...@gmail.com> > To: mysql@lists.mysql.com > Sent: Saturday, 9 July, 2011 5:54:58 PM > Subject: Low priority write > > Low Priority Lock > > Hello was wondering if anybody would have some input: > > This will be on the same table. > > Client (A) acquires a READ lock; > immediately thereafter a large amount of clients wait for a read lock > as > well, and client(B) requests a LOW PRIORITY insert. > > Another surge of clients request read locks as client(C) requests a > INSERT > lock. > > The last of the read locks are finished selecting. > > Does client (B) or (C) acquire their lock first? > > Will it go by priority or in order which the requests were received. > > I could not find documentation in forums or MySQL reference regarding > this. > > Thanks! > -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
