← Back to team overview

maria-developers team mailing list archive

Re: MDEV-5277 - Ensure that all MySQL 5.6 options are supported by the MariaDB 10.0 server

 

On Fri, Nov 15, 2013 at 12:07:38PM +0400, 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:
> * end-markers-in-json
> * optimizer-trace
> * optimizer-trace-features
> * optimizer-trace-offset
> * optimizer-trace-limit
> * optimizer-trace-max-mem-sizea
These all are for Optimizer Trace. It hasn't been ported to 10.0. There is no
consensus among MariaDB optimizer developers the whether optimizer trace is
useful and whether it should be ported.

> * eq-range-index-dive-limit

This is from a feature that hasn't been ported from 5.6 to 10.0. In my opinion,
we should port it (and maybe think how it can work with EITS).  I don't know
what others think, though.

BR
 Sergei
-- 
Sergei Petrunia, Software Developer
MariaDB | Skype: sergefp | Blog: http://s.petrunia.net/blog




Follow ups

References