Hi Dan, 133MHz huh? :-) Well, how large is the table? Huge rows? How many other indexes are on the table and on how many columns? Are those columns large? If you had a full-text index on a large column, for example, it could take very long on that system, especially if you're using 3.23.
Hard disk could be the slowdown too. What does SHOW PROCESSLIST say? I think it will say "Copy to tmp table" when making a copy of the data file. And then, when building the indexes, "Repair with keycache", or "Repair by sorting" (faster than keycache). If there's CPU or disk activity (and it's not from other things...), then it's not hung. Just sit and wait. :-) Matt ----- Original Message ----- From: "D. R. Hansen" Sent: Wednesday, October 15, 2003 3:39 PM Subject: ALTER TABLE z ADD INDEX... Speed: Follow up to LEFT JOIN question > What amount of time is reasonable to expect for indexing an FK int field on > a simple table with about 30K records. It's running on my "learning" > machine -- an aging Pentium 5/133 box running RH 8 which is ordinarily > quite fast enough for my purposes. It's been running about six hours now, > and I'm beginning to suspect something is hung (though I can query other > tables just fine from another ssh session. > > The running query is: > mysql> ALTER TABLE city ADD INDEX idx_city_state_id (state_id); > > If the answer is "Well, yes, you dolt, something is OBVIOUSLY crapping > out," can you give me some suggestions for troubleshooting? > > Thx - > > Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
