FLUSH TABLES WITH READ LOCK does *NOT* work with InnoDB
Hello everyone,
I recently had a issue when MySQL would crash when trying to access a innodb database. I submitted a bug report:
http://bugs.mysql.com/?id=32629
But quickly learned from Heikki (thanks for helping) that it was because I move a database containing innodb tables to another partition to create a symbolic link while the server was running. I did this after I ran a FLUSH TABLES WITH READ LOCK thinking that should be safe. I had done this many times before with MyISAM tables but Heikki tells me that this doesn't do the same for InnoDB tables.
Two things:
1) is there anyway to flush innodb tables to disk and move a db while the server is running?
2) Has anyone else been using symlinks and had/having problems?
Thanks!
--Dave
Edited 1 time(s). Last edit at 11/24/2007 01:26PM by Dave Juntgen.
Subject
Views
Written By
Posted
FLUSH TABLES WITH READ LOCK does *NOT* work with InnoDB
4641
November 23, 2007 12:15PM
7233
November 23, 2007 02:31PM
3417
November 23, 2007 10:29PM
2699
November 27, 2007 08:22PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.