Actually the SIGKILL is really always a no go unless a sysadmin decides
to do this manually. An upstart script should never do this
automatically (not even as a feature ;-) ) I can guarantee that in more
than 90% of the cases after a SIGKILL you will have corrupted tables.
With the default config o
Public bug reported:
Release: Ubuntu 10.04 LTS
Package Version: 5.1.41-3ubuntu12.6
Stopping a MySQL server can take some time, especially on a busy
database. If mysqld gets killed while having open connections, then
after the next start you will likely have a lot of tables corrupted.
The new up
