I want a new command in MySQL/InnoDB to freeze all filesystem activity in InnoDB… until I unfreeze it?
Why? I want mysqlhotcopy semantics for InnoDB.
Right now you can run FLUSH TABLES WITH READ LOCK and then xfs_freeze but it’s not very efficient or easy to code, and it’s pretty fragile.
INNODB FREEZE should not require a connection to remain open and should require an INNODB UNFREEZE to return IO to its normal state.
Further, when you copy away an underlying InnoDB database to a new server, crash recovery should NOT be required.
What really bothers me about the recent desire for MySQL features (triggers, etc) is that these type of features mean a LOT more to me. Operational competence in MySQL is very important and it seem the MySQL developers often forge this…
Drizzle and the InnoDB plugin are starting to show the way though….
I also want the ability to tell InnoDB to import a tablespace from a given .ibd created with innodb-file-per-table REGARDLESS of transaction identifiers and other information.
I know the tables is from another server, just import it already…