Hi everybody, We've been badly hit by a very interesting problem: an index gets into a "disabled" state if, during the filling up of a table containing a column having the said index, one only *looks* at the data which is being loaded! =:-o
In other words I start with "DROP TABLE" after which I "CREATE TABLE... " and then "CREATE INDEX...". I prepare another mysql console and then, in the first console, I do a "LOAD DATA INFILE ... INTO TABLE...". Since the INFILE is some 1.5 milion records and the server is rather slow I have plenty of time to switch consoles and issue a simple "DESCRIBE ..." for the table being loaded; or even an "EXPLAIN SELECT * FROM suspect_indexed_column WHERE...". In both cases the outcome of an "SHOW INDEXES FROM..." shows the index as having a "Comment" with value "disabled". And yes, a simple SELECT takes forever so the index is actually disabled! Of course an "ALTER TABLE... ENABLE KEYS" fixes the problem; But so does a "LOAD DATA INFILE..." when it's the only MySQL command being executed!! Why? :-o The only related issue that I could find so far was this bug http://bugs.mysql.com/bug.php?id=14709 but it looks like a more serious issue: running parralel "LOAD " commands looks very different to me as compared to one "LOAD " and one "EXPLAIN...". In the later case the one is simply _observing_ the load process... Does my description sound like something known or is it a new bug? Do I need to describe the whole context with kernel versions and exact table layouts or this is how things should happen? 'coz if this is not an exact illustration of "quantum mechanics" then I don't know what. :-))) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
