mysqlcheck -h$host -u$user -p$pass --analyze $dbname
I wish that was the case!
I tried analyze table ... and optimize table ..., which I presume
would be the same. It did not help. I also ran mysqlcheck just to see
if it will make a difference. Nope!
--
MySQL General Mailing List
For list arch
Gmail User wrote:
> I had perfectly working complex queries both with LEFT JOIN and without
> and they were returning results in under a second. After upgrade to
> 5.0.x, the same queries would return results in 20-30 second range.
I had a similar problem once (not related to 4.x->5.x though), it
When you upgraded from 4.1 to 5.0, did you do an in-place upgrade, or mysqldump
your data and then re-import?
As replied to Sebastian's post, in-place.
Try using either mysqldump or mysql-administrator to dump out your data to an
.sql file. Then re-import all of your data into 5.x. You will
possible you had set up some query cache in 4, but not currently in 5?
may not be optimized, but yes, query cache is enabled, all 25 MB of it. :-)
how did you 'upgraded' your data?
regrettably, in-place.
interestingly, I was recovering after server crash that chopped of a
table. after upgra
27;s amount of RAM.
HTH!
J.R.
From: Gmail User <[EMAIL PROTECTED]>
Sent: Tuesday, May 22, 2007 2:30 AM
To: mysql@lists.mysql.com
Subject: Upgraded to 5.0.x from 4.1.x and ORDER BY sucks!
I had perfectly working complex queries both with LEFT JOIN and without
and they were
Gmail User schrieb:
> I had perfectly working complex queries both with LEFT JOIN and without
> and they were returning results in under a second. After upgrade to
> 5.0.x, the same queries would return results in 20-30 second range.
possible you had set up some query cache in 4, but not currently
I had perfectly working complex queries both with LEFT JOIN and without
and they were returning results in under a second. After upgrade to
5.0.x, the same queries would return results in 20-30 second range.
Through trial and error, I discovered that in case of SELECT ... FROM
table1, table2 ... O
