← Back to team overview

maria-developers team mailing list archive

Re: Proposal to split @@optimizer_switch

 

> -----Original Message-----
> From: maria-developers-
> bounces+wlad=montyprogram.com@xxxxxxxxxxxxxxxxxxx [mailto:maria-
> developers-bounces+wlad=montyprogram.com@xxxxxxxxxxxxxxxxxxx] On
> Behalf Of Sergey Petrunya
> Sent: Montag, 27. Juni 2011 15:28
> To: maria-developers@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Maria-developers] Proposal to split @@optimizer_switch
> 
> On Fri, Jun 10, 2011 at 12:13:12PM +0400, Sergey Petrunya wrote:
> > Hello,
> >
> > Please find below descriptions of problems with current
> @@optimizer_switch
> > variable, as well as a proposal on how to fix it.
> >

I would actually prefer more traditional underscore syntax, just for the
sake of uniform parameter handling.  Whether the dotted notation is better
readable that underscore one, is mostly matter of  individual taste.
Besides, I would remove underscore from some already existing underscored
keyword (this also eliminated differences between semijoin and outer_join
for example). Stuff like indexconditionpushdown  becomes unreadable, perhaps
can be "icp", it is referred as ICP everywhere anyway, and there are other
abbreviations already in place, like mrr and bka. 

With this proposal , keywords would look like :

optimizer_indexmerge=on
optimizer_indexmerge_union=on
optimizer_indexmerge_sortunion=on
optimizer_indexmerge_intersection=on
optimizer_indexmerge_sortintersection=off
optimizer_icp=on
optimizer_joincache_bka=on
optimizer_joincache_hashed=on
optimizer_joincache_incremental=on
optimizer_joincache_optimizebuffersize=on
optimizer_joincache_outerjoin=off
optimizer_joincache_semijoin=off
optimizer_mrr=on
optimizer_mrr_costbased=off
optimizer_mrr_sortkeys=on
optimizer_semijoin=on
optimizer_semijoin_firstmatch=on
optimizer_semijoin_loosescan=on
optimizer_subquery_cache=on
optimizer_subquery_intoexists=on
optimizer_subquery_materialization=off
optimizer_subquery_partialmatch_rowidmerge=on
optimizer_subquery_partialmatch_tablescan=on
optimizer_tableelimination=on




Follow ups

References