Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 8
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 5 votes cast
Dec
8
comment Can a trigger access the query string?
I have tried this, but the query I always get is the "SELECT info INTO" query. The CONNECTION_ID() does change, but it looks like the current id is always that of the select? Should I try and save the CONNECTION_ID() earlier in the process?
Sep
12
awarded  Scholar
Sep
12
accepted Internal reason for killing process taking up long time in mysql
Sep
12
comment Internal reason for killing process taking up long time in mysql
I'll check that, thanks. Anyway, the kill-and-force-recovery seems to have worked, alhtough I couldn't stop the process. In the end I just did a kill -9 to be done with it.
Sep
12
comment Internal reason for killing process taking up long time in mysql
I just found that quote too, i'll try it. @insertion: you are right: it didn't even cross my mind it could take this long, so never considered any alternatives :)
Sep
12
awarded  Supporter
Sep
12
comment Internal reason for killing process taking up long time in mysql
In short: I am fscked... Am I glad this is a test-environment...
Sep
12
revised Internal reason for killing process taking up long time in mysql
added 9 characters in body
Sep
12
comment Internal reason for killing process taking up long time in mysql
I think I get it, but what do you mean by that last sentence? That if I kill the thing, the recovery-phase might start the 'rollback' all over again? That wouldn't be good. I'm now just letting it run, but its getting towards 7 hours of run-time now, which is getting ridiculous-ish. Would you advice in favor or against killing the mysqld?
Sep
12
awarded  Student
Sep
12
awarded  Editor
Sep
12
revised Internal reason for killing process taking up long time in mysql
added 31 characters in body; edited tags
Sep
12
asked Internal reason for killing process taking up long time in mysql
Sep
12
awarded  Autobiographer