Hello.
Here is described the possible way of how to force the rollback
(you can kill the mysqld process and set innodb_force_recovery to 3 to
bring the database up without the rollback, then DROP the table that is
causing the runaway rollback):
http://dev.mysql.com/doc/mysql/en/forcing-recovery.html
Joseph Cochran <[EMAIL PROTECTED]> wrote:
>
>Thanks for the questions, hopefully this will help: InnoDB, yes. It's
>version 4.1.11, not replicated.
>
>I am familiar with KILL. It is definitely something I CAN do, but not
>necessarily something I SHOULD do at this point in time. Usually when you
>kill a process while it's running, it will roll back the transaction before
>releasing the process, which often takes as long as the commit: I'd rather
>not kill it and have it rolling back for two weeks if I can help it.
>
>Thanks!
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
