Hi,
There's something I'm not sure about with DELETE LOW_PRIORITY. It says in
the manual that:
"If you specify the keyword LOW_PRIORITY, execution of the DELETE is delayed
until no other clients are reading from the table."
What exactly does it mean by "no other clients are reading"? Does it mean
that when you first issue the delete query that if other processes are
reading from the table then it won't start until they have finished? I
imagine this is the case, BUT, what if other processes want to read from the
table once the delete has started - will the delete pause until the other
processes have finished reading? What about other processes wanting to
insert records too?
The reason I ask this is that it's critical that I delete approximately
300,000 records from a 2 million record table, but whilst still letting
other processes read from and (mainly) insert records in a timely manner.
Can anyone offer a precise explanation of what DELETE LOW_PRIORITY
facilitates?
Regards,
------------------------------------------------
Basil Hussain ([EMAIL PROTECTED])
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
