maria-developers team mailing list archive

[Sergey Vojtovich <svoj@xxxxxxxxxxx>]

Hi Sergei,

I updated task accordingly.

Thanks,
Sergey

On Sat, Nov 16, 2013 at 02:53:26AM +0400, Sergei Petrunia wrote:
> On Fri, Nov 15, 2013 at 03:53:47PM +0400, Sergey Vojtovich wrote:
> > Sergei,
> > 
> > thanks for your feedback.
> > 
> > On Fri, Nov 15, 2013 at 12:32:11PM +0400, Sergei Petrunia wrote:
> > > 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.
> > Ok to state "not used or needed in MariaDB"?
> > 
> > > 
> > > > * 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.
> > Ok to state "to be implemented in later 10.x versions"?
> > 
> 
> My opinion is that both should be "to be implemented in later 10.x versions".
> (others may say "not used or needed" for optimizer trace options).
> 
> BR
>  Sergei
> -- 
> Sergei Petrunia, Software Developer
> MariaDB | Skype: sergefp | Blog: http://s.petrunia.net/blog
> 
>