OTECTED]>
To: "Bob O'Neill" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, June 03, 2005 3:20 PM
Subject: Re: max_seeks_for_key in InnoDB
Hi,
you can use a hint to force specific index usage :
http://lib.hutech.edu.vn/ebookonline/ebook1/0596003064/hpmysql-CHP-5-SECT-4.html
But this
I am having problems with MySQL inconsistently choosing the wrong index, or no
index at all, for queries on tables with 20 million rows. Would it be a good
idea for me to set max_seeks_for_key to 1 (or something less than 4 billion),
in order to force MySQL to use an index? We are using InnoDB
If I try to read table 'b' after locking table 'a', I expect to get
the error message "Table 'b' was not locked with LOCK TABLES".
However, if my query that accesses table b is stored in the query
cache, I don't get the error. This causes a problem in the following
scenario:
User 1:
LOCK TABLES
Hello. I am wondering why some of my queries are slow on the first run, but
speedy on subsequent runs. They are not being query cached, as I have
query_cache_type set to DEMAND. Is it something as simple as pulling the
data into RAM from disk, or is there something else going on? Here's a
simpl
