I have a non-primary-key index on a large MyISAM
table, and dropping the index takes a long time, in
addition to maxing out the CPU utilization in its
final 1/3 interval.
Why is that?
In MS SQL Server for example, dropping the index is
almost instantaeous, unless it's clustered and you
have other indexes on the same table, because they
have to be rebuilt. But we're talking here about
MyISAM tables with non-clustered indexes.
This defeats the whole idea of dropping an index on a
table before a large batch update.
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
