About "START TRANSACTION WITH CONSISTENT SNAPSHOT " for tokudb

Hi all,

During my test, I find out that the tokudb does not support "START TRANSACTION WITH CONSISTENT SNAPSHOT" just like innodb,
and so it is hard to get a consistent binlog pos before do a dump of target tokudb table.

Then I try a new method, which seams work, the full process is:

Assume that: I want to dump tokudb table t_big

Firstly, I create a extra tmp tokudb table t_tmp:
CREATE TABLE t_tmp(c1 int) engine=tokudb;
INSERT INTO t_tmp values (1);

Then start the dump:

FLUSH TABLES WITH READ LOCK;
begin;
select * from t_tmp; // let this session to get the transaction snapshot
show master status; //to get binlog file and pos
unlock tables;
select * from t_big;

I test above approach, and it works.
Is it above approach works for all tokudb use cases?

Best Regards!

Dennis