2005 2:56 PM
> To: Keith Ivey; mysql@lists.mysql.com
> Cc: Homam S.A.
> Subject: Re: Why does dropping indexes takes such a long time?
>
> This is the reply I got when I posted the same message
> last week. I checked the list for hours and my message
> didn't show up. This
This is the reply I got when I posted the same message
last week. I checked the list for hours and my message
didn't show up. This is why I assumed it never made
it. I have no idea what this auto-reply is saying. I
tried the AltaVista bablefish with Spanish. It was the
closest, but it gave me garbl
DVP
Dathan Vance Pattishall http://www.friendster.com
> -Original Message-
> From: Homam S.A. [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 02, 2005 11:50 AM
> To: mysql@lists.mysql.com
> Subject: Why does dropping indexes takes such a long time?
&g
Homam S.A. wrote:
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?
You asked the question last week, and several people answered.
Do you think the answer has chang
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
