Hi Kristian, thanks for your feedback it helped a lot. I updated jira task accordingly. Below are fields that haven't been identified yet. And a few comments inline. The following options exist in 5.6 but not in 10.0: * default-tmp-storage-engine * log-raw * default-authentication-plugin * ignore-db-dir * explicit-defaults-for-timestamp * log-throttle-queries-not-using-indexes * disconnect-on-expired-password * sha256-password-private-key-path (sha256_password plugin) * sha256-password-public-key-path (sha256_password plugin) The following options exist in 5.5 and 5.6 but not in 10.0: * abort-slave-event-count => debug-abort-slave-event-count * disconnect-slave-event-count => debug-disconnect-slave-event-count * exit-info => debug-exit-info * max-binlog-dump-events => debug-max-binlog-dump-events * sporadic-binlog-dump-fail => debug-sporadic-binlog-dump-fail * new * skip-new * skip-stack-trace The following options were added after 5.6.10: * innodb-buffer-pool-evict // UNIV_DEBUG * innodb-ft-total-cache-size * innodb-ft-result-cache-limit * innodb-log-compressed-pages * innodb-log-checkpoint-now // UNIV_DEBUG * validate-user-plugins On Fri, Nov 15, 2013 at 10:54:03AM +0100, Kristian Nielsen wrote: ...skip...
* server-uuid
Hm, I thought we had this already? I guess not... Anyway, I think the server-uuid feature is stupid, and I would suggest not to merge it. AFAIK, this is anyway only a read-only system variable, it cannot be set in my.cnf or command line... Sorry, it is here by mistake. I didn't notice NO_CMD_LINE. Removed.
...skip...
* enforce-gtid-consistency * gtid-mode
This is for MySQL 5.6 GTID, which will not be in MariaDB (we have a completely different GTID implementation). So they should not be implemented, nor should we have dummy options for compatibility. You mean refuse to start mysqld if any of those two specified? Please confirm.
Thanks, Sergey