Sneak peek at Falcon tablespaces in MySQL 6.0 Beta
We’re rounding the corner on releasing the first MySQL 6.0 beta, which will have a number of updates to our new Falcon transaction storage engine. One enhancement I wanted to give everyone a sneak-peek on is the addition of user-defined tablespaces for Falcon.
Many of you have requested the ability to define tablespace storage containers that allow you to place data exactly where you want it. Well, now in MySQL 6.0/Falcon you get your wish (below example is on Windows):
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 6.0.1-alpha-pb605 MySQL Pushbuild Edition, build 605
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> use gimf;
Database changed
mysql> create tablespace gimf_ts
-> add datafile 'c:/dev/gim_ts1.fts'
-> engine=falcon;
Query OK, 0 rows affected (1.17 sec)
mysql> create table t1 (c1 int) engine=falcon tablespace gimf_ts;
Query OK, 0 rows affected (0.16 sec)
mysql> insert into t1 values (1), (2), (3);
Query OK, 3 rows affected (0.02 sec)
Records: 3 Duplicates: 0 Warnings: 0
mysql> drop table t1;
Query OK, 0 rows affected (0.05 sec)
mysql> drop tablespace gimf_ts engine=falcon;
Query OK, 0 rows affected (0.00 sec)
No more having to add datafiles to a single tablespace defined in the my.cnf file and stop/restart the server for the change to take affect - with Falcon, you now have dynamic storage management abilities, which is nice.
I’ll write a more in-depth article on Falcon tablespace management once the 6.0 beta is available so be looking for that as well as the 6.0 beta release announcement that will be coming soon!