In the last episode (Jul 11), Leonardo Leonardo said:
> On Sun, Jul 11, 2010 at 7:07 PM, Leonardo Leonardo
> wrote:
> > Here is the structure of the Table T1 ( ENGINE=InnoDB ) -
> >
> > `c1` varchar(128) NOT NULL default '',
> > `c2` int(11) NOT NULL default '0',
> > `c3` varchar(32) NOT NUL
On Sun, Jul 11, 2010 at 7:07 PM, Leonardo Leonardo wrote:
>
> Here is the structure of the Table T1 ( ENGINE=InnoDB ) -
>
> `c1` varchar(128) NOT NULL default '',
> `c2` int(11) NOT NULL default '0',
> `c3` varchar(32) NOT NULL default '',
> `c4` blob,
> `c5` double default NULL,
> `c6
You you send us explain of that query.
On Sun, Jul 11, 2010 at 6:31 PM, arijit bhattacharyya
wrote:
> optimize / analyze table in each of the hosts is not a good option for me ,
> this is an in-production set-up with minimal number of boxes in rotation .
>
>
>
> On Sun, Jul 11, 2010 at 5:57 PM, a
optimize / analyze table in each of the hosts is not a good option for me ,
this is an in-production set-up with minimal number of boxes in rotation .
On Sun, Jul 11, 2010 at 5:57 PM, arijit bhattacharyya
wrote:
>
> Hi , i am running into trouble due to wrong index chosen by mysql in some
> par
Hi , i am running into trouble due to wrong index chosen by mysql in some
particular type of queries . This is happening in a critical production
environment where we have deployment in two different colocations . I am
seeing that a paticular query is using one index in one set of hosts &
another i
