Hi, Sergey! On Nov 15, Sergey Vojtovich wrote:
Hi!
I'm gathering 5.6 options that are not present in 10.0 and the way we want to handle them. Could you check options listed below and if you're aware of their destiny indicate if options: * not used or needed in MariaDB * to be implemented in later 10.x versions * tuned via different 10.x specific options
The following options exist in 5.6 but not in 10.0: * default-tmp-storage-engine
to be implemented in later 10.x versions (or even in 10.0)
* log-raw
dunno, we don't do query rewriting. not used or needed in MariaDB
* default_authentication_plugin
to be implemented in later 10.x versions
* ignore-db-dir
called ignore-db-dirs in MariaDB
* explicit-defaults-for-timestamp
MDEV-3929
* log-throttle-queries-not-using-indexes
at the moment not used or needed in MariaDB, can be to be implemented in later 10.x versions, if needed
* disconnect-on-expired-password
to be implemented in later 10.x versions
* sha256-password-private-key-path (sha256_password plugin) * sha256-password-public-key-path (sha256_password plugin)
to be implemented in later 10.x versions
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
This will, I guess, stay that way.
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
will be in 10.0 after the next innodb merge
* validate-user-plugins
to be implemented in later 10.x versions ? Regards, Sergei