Are you saying there was a regression in the Optimizer? (Sounds like a workaround is to do STRAIGHT_JOIN -- yuck!)
I compared several hundred "slow" queries on 5.1 versus MariaDB 5.5. I found several improvements. > -----Original Message----- > From: Mihail Manolov [mailto:mihail.mano...@liquidation.com] > Sent: Thursday, February 14, 2013 3:30 PM > To: Rick James > Cc: Singer Wang; Mike Franon; Akshay Suryavanshi; > <mysql@lists.mysql.com> > Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6 > > The ones that didn't work for me required table rearrangement in the > query. MySQL 5.5 was very particular about the table join order. > > On Feb 14, 2013, at 6:11 PM, Rick James wrote: > > > Singer, do you have some examples? > > > >> -----Original Message----- > >> From: Singer Wang [mailto:w...@singerwang.com] > >> Sent: Thursday, February 14, 2013 2:59 PM > >> To: Mihail Manolov > >> Cc: Mike Franon; Akshay Suryavanshi; <mysql@lists.mysql.com> > >> Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6 > >> > >> There are queries that works with 5.1/5.0 that do not work with 5.5, > >> I would test extensively.. > >> > >> S > >> > >> > >> On Thu, Feb 14, 2013 at 5:22 PM, Mihail Manolov < > >> mihail.mano...@liquidation.com> wrote: > >> > >>> You could jump from 5.0 directly to 5.5 and skip 5.1. I have > without > >>> any issues. There are some configuration file change, which you may > >>> want to consider checking. I definitely recommend upgrading your > >>> development servers for an extensive testing. Some queries _may_ > run > >>> slower or not work at all and you may have to rearrange how you > join > >> tables in your queries. > >>> > >>> The upgrade from 5.5 to 5.6 should me smoother, though. > >>> > >>> > >>> On Feb 14, 2013, at 4:28 PM, Mike Franon wrote: > >>> > >>>> Great thanks for the info, I guess the best way to do this is take > >> a > >>>> spare server, set it up with our standard setup, and then start > the > >>>> upgrade as you said 5.0 -> 5.1 -> 5.5, test and then upgrade to > 5.6 > >>>> and test. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On Thu, Feb 14, 2013 at 4:22 PM, Akshay Suryavanshi > >>>> <akshay.suryavansh...@gmail.com> wrote: > >>>>> Mike, > >>>>> > >>>>> 5.6 is GA now, so its stable release. Also you should not jump to > >>>>> 5.6 directly, atleast from 5.0. > >>>>> > >>>>> There are many bug fixes and changes in 5.1, so you should > >> consider > >>>>> this way. > >>>>> > >>>>> 5.0-->5.1-->5.5 (all slaves first, and then the master) > >>>>> > >>>>> And further 5.5 --> 5.6 (again all slaves first and then the > >>>>> master) > >>>>> > >>>>> Hope this helps. > >>>>> > >>>>> Cheers! > >>>>> > >>>>> On Fri, Feb 15, 2013 at 2:38 AM, Mike Franon > >> <kongfra...@gmail.com> > >>> wrote: > >>>>>> > >>>>>> I have 1 master with many slaves, using the master only for > >>>>>> inserts and the rest are readers. > >>>>>> > >>>>>> > >>>>>> Is 5.6 stable? Or better off to go to 5.5? > >>>>>> > >>>>>> If so do I need to make a few steps or can go straight from 5.0 > >> to 5.6? > >>>>>> > >>>>>> > >>>>>> Any best practices and recommendations? > >>>>>> > >>>>>> Thanks > >>>>>> > >>>>>> -- > >>>>>> MySQL General Mailing List > >>>>>> For list archives: http://lists.mysql.com/mysql > >>>>>> To unsubscribe: http://lists.mysql.com/mysql > >>>>>> > >>>>> > >>>> > >>>> -- > >>>> MySQL General Mailing List > >>>> For list archives: http://lists.mysql.com/mysql > >>>> To unsubscribe: http://lists.mysql.com/mysql > >>>> > >>> > >>> > >>> -- > >>> MySQL General Mailing List > >>> For list archives: http://lists.mysql.com/mysql > >>> To unsubscribe: http://lists.mysql.com/mysql > >>> > >>> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
