Dear all,
I have a table a_src in a mysql database as :
12K ac_src.frm
25G ac_src.MYD
60M ac_src.MYI
Yesterday, near about 2 pm , I got the error :
Error 1602 (23000) : Duplicate '6204567' for key 1
I solve this issue before by repairing the table but this time the data
is very
Hi Aveek,
I would like to suggest some points here:
You could try increasing the max allowed packets to 128MB. Though you think
16MB is enough, increasing it is not going to affect the server. It is
dynamic value, so you could revert back the changes if you feel so.
Also make sure log_warnings=2
I'm trying to optimize a query that doesn't seem all that complicated,
however I can't seem to get it to not use a temp table and filesort.
developer@vm_vz_daevid:~$ mysql --version
mysql Ver 14.12 Distrib 5.0.92, for portbld-freebsd8.1 (amd64) using 5.2
EXPLAIN EXTENDED
SELECT
--
Try setting wait_timeout=36000
Regards,
Chandru
On 5/29/2011 11:13 PM, ars k wrote:
Hi Aveek,
I would like to suggest some points here:
You could try increasing the max allowed packets to 128MB. Though you think
16MB is enough, increasing it is not going to affect the server. It is
dynamic
Are you using connection pooling in your application?
Regards,
Chandru
On 5/27/2011 11:05 AM, Claudio Nanni wrote:
'MySQL server has gone away'
Can be a network problem,
Just to increase complexity :)
On May 26, 2011 11:03 PM, Prabhat Kumaraim.prab...@gmail.com wrote:
I had experience with
s 2011/05/27 12:26 -0700, Daevid Vincent
[a] the EXTENDED keyword doesn't seem to do anything different? I get the
same columns and results??!
show warnings
2011/05/27 12:26 -0700, Daevid Vincent
In other words, am I wasting my time trying to tweak my
query and indexes here with the idea
I sent this Friday, but it never made it to the list?!
-Original Message-
From: Daevid Vincent [mailto:dae...@daevid.com]
Sent: Friday, May 27, 2011 12:27 PM
To: mysql@lists.mysql.com
Subject: Using where; Using temporary; Using filesort
I'm trying to optimize a query that doesn't seem
Is it ALWAYS possible to fabricate a query/schema in
such a way that MySQL ALWAYS uses the ideal
No. Optimisation is better in 5.6 than in 5.0, though.
Did you try adding multi-column indexes to cover the join and the order
by clause?
'Using where' extra -- you just have to keep at it?
Dear MySQL users,
MySQL 5.5.13 is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.13 is recommended
for use on production systems.
MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL
