title: Killing the mysqld process
body: <p>I have a table with ~800k rows. I ran an <code>update users set hash = SHA1(CONCAT({about eight fields})) where 1;</code></p>
  
  <p>Now I have a hung Sequel Pro process and I'm not sure about the <code>mysqld</code> process. </p>
  
  <p>This is two questions:</p>
  
  <ol>
  <li><p>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?</p></li>
  <li><p>Assume you had to update a table like this. What would be a quicker / more reliable method of updating <strong>without writing a separate script</strong>.</p></li>
  </ol>
  
  <p>I just checked with phpMyAdmin and it <em>appears</em> as though the query is complete. I still have Sequel Pro using 100% of both my cores though...</p>