-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
centOS 编译错误 #63
Comments
按文档:https://www.mf8.biz/install-alisql-with-tokudb/ 报错 [ 17%] Built target regex |
系统是不是 CentOS 6? 推荐使用 CentOS 7 编译 |
也是 CentOS 7 它,新装的。 阿里云新买的服器器。 |
拉最新的代码再编译一下。 |
fungo
pushed a commit
that referenced
this issue
May 1, 2018
TokuDB has status to expose the compression ratio: mysql> show global status like 'tokudb%COMPRESSION_RATIO'; +---------------------------------------+----------+ | Variable_name | Value | +---------------------------------------+----------+ | Tokudb_LEAF_NODE_COMPRESSION_RATIO | 5.850260 | | Tokudb_NONLEAF_NODE_COMPRESSION_RATIO | 0.564453 | | Tokudb_OVERALL_NODE_COMPRESSION_RATIO | 4.528809 | +---------------------------------------+----------+ but this a global level ratio, and sometimes the users may be interested in table level compression ratio. This patch address this request by exposing FT level compresstion ratio through information_schema.TokuDB_fractal_tree_info table. We add two columns, leaf_compress_ratio and internal_compress_ratio, which indicate the compression ratio of leaf nodes and internal nodes accordingly. Limitations, the comppression ratio infos are maintained in memeory, and will lost when server is restarted or ft get evicted from memory. Maybe in future there infos will be persisted in ft file, when this feature is accepted by PerconaFT upstream.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/mnt/service/AliSQL/sql/sql_planner.cc:431:18: note: ‘loose_scan_opt.Loose_scan_opt::best_loose_scan_start_key’ was declared here
Loose_scan_opt loose_scan_opt;
The text was updated successfully, but these errors were encountered: