Hi Kristian! On Wed, Mar 8, 2017 at 4:58 PM, Kristian Nielsen <knielsen@knielsen-hq.org> wrote:
One thing that could be done is to supply a standard stored procedure to add an engine table, to avoid direct changes to the mysql database:
mysql.gtid_pos_add_engine("MyRocks");
My concern is about configuration management and automated deployments. Having an extra "query" step is not so ideal...
So to summarise
- Auto create mysql.gtid_slave_pos_{innodb,tokudb,myrocks} if a transaction is seen in one of those engines
- A --skip-gtid-auto-create-pos-table to disable this auto behaviour
- A stored procedure mysql.gtid_pos_add_engine() to facilitate manually adding an engine table.
What do you think, does this sound ok? Suggestions for better ways?
I like this idea very much!!! Thanks, -will -- Will Fong, Senior Support Engineer MariaDB Corporation