Dathan Pattishall wrote:
From the brief sound of it your using myISAM, and the query taking themost time is not indexed or using an index properly.
Alters will lock the table, and once it starts it should finish or your
going to have to recover the table. I suggest taking an outage. If you
can't
Make a replica of the server, put it in a master slave role. Alter the slave (ensure the new column has a default) swap the roles OR copy the table if the application can handle having writes blocked. If not, the slave must take the role of master, and the previous master can go away.
The queries waiting are not locked, and are hitting a different table
I'm updating tableA
users are doing queries on an indexed field on table B
I just stopped my update, and tested the users queries, all responded in ms's, each were hitting the main primary key
I am going to take tableA and modify it on an offline server
it would be nice if I could limit drive useage so it did not kill the server like that
running raid 5
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
