Agreed. Will do that along with several other possible changes. But
for the moment, I'm still gathering information and coming up with
plausible models.
Will also be turning on general mysql logging on both Master and
Slave, at least briefly, to see what statements are being run on both.
Regard
bkp0# mysql h5000_bill
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1643184
Server version: 5.1.68-log FreeBSD port: mysql-server-5.1.68
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracl
To adjust a table name within a SQL statement, you need to create a
string with the updated values and use PREPARE/EXECUTE
See below, I am replacing your CONCAT with the complete insert statement
The example below is also assuming the value in the WHERE clause should
be adjusted to the number, inst
2013/2/13 Robert Citek
> On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek
> wrote:
> > Any other possibilities? Do other scenarios become likely if there
> > are two or more tables?
> >
> > Of those, which are the most likely?
>
> [from off-list responder]:
> > Other possibility: The replication i
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.
Yes. Except for a handful of static MyISAM tables. But the tables
that are experiencing the issues are all InnoDB and large (a dozen or
so fields, but lots of records.)
Regards,
- Robert
On Thu, Feb 14, 2013 at 5:59 PM, Singer Wang wrote:
> Are you using all InnoDB?
>
> S
--
MySQL General Ma
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 configur
On Thu, Feb 14, 2013 at 4:54 PM, Manuel Arostegui wrote:
> 2013/2/13 Robert Citek
>>
>> On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek
>> wrote:
>> > Any other possibilities? Do other scenarios become likely if there
>> > are two or more tables?
>> >
>> > Of those, which are the most likely?
>>
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
Its a very pedantic case, but we had a few instances where it was an issue
at my last job. It basically involved multi-table deletes and aliasing.. I
quote the change notes for MySQL 5.5.3
*Incompatible Change:* Several changes were made to alias resolution in
multiple-table DELETE statements so t
Sounds like something that, once discovered, can be fixed in the old version --
then it works correctly in both.
That is what happened with a 4.0->5.1 conversion years ago. With 1000
different tables and associated code, we encountered two incompatibilities.
One had to do with NULLs, the othe
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...@liqui
On Thu, Feb 14, 2013 at 5:46 PM, Rick James wrote:
>> Is it in read only mode?
> Furthermore, are all users logging in as non-SUPER users? Note: root
> bypasses the readonly flag!
No. The user that is commonly used does have Super privileges. I am
not sure why, but it does.
Regards,
- Rober
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;
> Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6
>
> There are queries
Are you using all InnoDB?
S
On Thu, Feb 14, 2013 at 5:55 PM, Robert Citek wrote:
> On Thu, Feb 14, 2013 at 4:54 PM, Manuel Arostegui
> wrote:
> > 2013/2/13 Robert Citek
> >>
> >> On Wed, Feb 13, 2013 at 8:59 AM, Robert Citek
> >> wrote:
> >> > Any other possibilities? Do other scenarios bec
> Is it in read only mode?
Furthermore, are all users logging in as non-SUPER users? Note: root bypasses
the readonly flag!
> -Original Message-
> From: Manuel Arostegui [mailto:man...@tuenti.com]
> Sent: Thursday, February 14, 2013 1:55 PM
> To: Robert Citek
> Cc: mysql
> Subject: Re:
Recommend, for security reasons, you rectify that.
If you need some SUPER action, create a stored procedure with privileges
'creator', so the security hole is still mostly contained.
> -Original Message-
> From: Robert Citek [mailto:robert.ci...@gmail.com]
> Sent: Thursday, February 14, 2
Ditto. I would mysqldump 5.0, load it onto a 5.5 (or 5.6) box that you have as
a slave of the 5.0 master. The load may uncover some issues. Testing reads
may uncover issues. The replication stream will test the writes; it may
uncover issues.
After being comfortable with that, build new slav
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
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
wrote:
> Mike,
>
> 5.6
2013/2/14 Mike Franon
> 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.
Do not forget to leave that spare server running f
21 matches
Mail list logo
