Killing the mysqld process

Posted by Josh K on Stack Overflow See other posts from Stack Overflow or by Josh K
Published on 2010-06-09T22:02:21Z Indexed on 2010/06/09 22:12 UTC
Read the original article Hit count: 258

Filed under:
|
|
|
|

I have a table with ~800k rows. I ran an update users set hash = SHA1(CONCAT({about eight fields})) where 1;

Now I have a hung Sequel Pro process and I'm not sure about the mysqld process.

This is two questions:

  1. What harm can possibly come from killing these programs? I'm working on a separate database, so no damage should come to other databases on the system, right?

  2. Assume you had to update a table like this. What would be a quicker / more reliable method of updating without writing a separate script.

I just checked with phpMyAdmin and it appears as though the query is complete. I still have Sequel Pro using 100% of both my cores though...

© Stack Overflow or respective owner

Related posts about mysql

Related posts about database