Hi Philip, Sergei I'm a bit confused about the order... It was possible to switch on already. So, if the objective is to switch it on by default, the appropriate process flow would appear to be: - Sergei lets Philip know of the intent (since Sergei knows best when the code appears mature enough) - Philip does his testing nasties with the switch enabled, providing feedback to Sergei/bugsystem. - once all is well, the default is changed. With the flow as going below, you can have the potential nasty of having to undo the default change again if Philip finds something that cannot be quickly fixed. Plus you have to keep track of it to make sure nothing gets released before testing is completed successfully. Cheers, Arjen. ----- Original Message ----- From: "Philip Stoev" <pstoev@askmonty.org> To: "Sergei Petrunia" <psergey@askmonty.org> Cc: maria-developers@lists.launchpad.net Sent: Tuesday, 8 November, 2011 5:58:22 AM Subject: Re: [Maria-developers] FYI: @@optimizer_switch default changed to havesemijoin switched ON. No problem, will do so right away. Philip Stoev ----- Original Message ----- From: "Sergei Petrunia" <psergey@askmonty.org> To: <maria-developers@lists.launchpad.net>; "Philip Stoev" <pstoev@askmonty.org> Sent: Monday, November 07, 2011 9:37 PM Subject: [Maria-developers] FYI: @@optimizer_switch default changed to havesemijoin switched ON.

Hi!

If you haven't noticed: last week I've pushed a change that enabled semi-join optimization flags by default, i.e. now the default @@optimizer_swich value has:

semijoin=on firstmatch=on loosescan=on

Philip: if you have any testing planned for "after semi-join optimizations are enabled by default", now it's time to do them.

BR Sergei -- Sergei Petrunia, Software Developer Monty Program AB, http://askmonty.org Blog: http://s.petrunia.net/blog

-- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Remote expertise & maintenance for MySQL/MariaDB server environments. Follow us at http://openquery.com/blog/ & http://twitter.com/openquery