List:General Discussion« Previous MessageNext Message »
From:Michael Widenius Date:September 2 1999 5:05pm
Subject:Re: How exactly does INSERT DELAYED work?
View as plain text  
>>>>> "Jules" == Jules Bean <jmlb2@stripped> writes:

<cut>

>> (The lock manager schedules locks according to priority.   INSERT
>> DELAYED simply has a lower priority than SELECT)

Jules> OK.  That sounds neat and straight-forward.

Jules> But, if that's the case, what is the point of delayed_insert_limit?  Why
Jules> should the thread check every 100 (or whatever) rows?  Surely if the
Jules> selects had finished, it would have got its lock already anyway?

Jules> Ah.  Hang on.  I understand!

Jules> delayed_insert_limit is used when the thread has already obtained the
Jules> lock, right?  And it will automatically give the lock up again if it
Jules> sees a select query coming?

Yes!

Regards,
Monty
Thread
How exactly does INSERT DELAYED work?Jules Bean1 Sep
  • How exactly does INSERT DELAYED work?Michael Widenius2 Sep
  • Re: How exactly does INSERT DELAYED work?Jules Bean2 Sep
    • Re: How exactly does INSERT DELAYED work?Michael Widenius2 Sep
  • Re: How exactly does INSERT DELAYED work?Jules Bean2 Sep
    • Re: How exactly does INSERT DELAYED work?Michael Widenius2 Sep