On Tue, Jul 10, 2012 at 05:50:07PM -0400, Jeffrey Grollo wrote:
> Hi,
>
> I’m attempting to optimize a join and am having a difficult time using
> multiple columns from a composite index. The second column of the composite
> key is being used when tested for equality, but not for IN or BETWEEN
> c
On 7/10/2012 5:50 PM, Jeffrey Grollo wrote:
Hi,
I’m attempting to optimize a join and am having a difficult time using
multiple columns from a composite index. The second column of the composite
key is being used when tested for equality, but not for IN or BETWEEN
criteria.
As an example, say t
On Wed, Jul 11, 2012 at 5:46 AM, Reindl Harald wrote:
> > mysql> show profiles;
> >
> +--++--+
> > | Query_ID | Duration | Query
> > |
> >
> +--
sorry.. im using 5.1
On Wed, Jul 11, 2012 at 10:09 AM, J M wrote:
> hi all,
>
> our DB crashed for some reason... any inputs would be greatly appreciated..
>
> 120711 8:12:21 - mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible that this binary
> or one of the li
hi all,
our DB crashed for some reason... any inputs would be greatly appreciated..
120711 8:12:21 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. Th
column used in the order by caluse, should be the first column in the
select statement to make the index work
On Wed, Jul 11, 2012 at 3:16 PM, Reindl Harald wrote:
>
>
> Am 11.07.2012 11:43, schrieb Ewen Fortune:
> > Hi,
> >
> > On Wed, Jul 11, 2012 at 10:31 AM, Reindl Harald
> wrote:
> >> the m
Am 11.07.2012 11:43, schrieb Ewen Fortune:
> Hi,
>
> On Wed, Jul 11, 2012 at 10:31 AM, Reindl Harald
> wrote:
>> the mysql query optimizer is somehow stupid
>
> Its not stupid - remember its not trying to find the best index,
> rather its trying to find the least costly plan
> to return the d
Hi,
On Wed, Jul 11, 2012 at 10:31 AM, Reindl Harald wrote:
> the mysql query optimizer is somehow stupid
Its not stupid - remember its not trying to find the best index,
rather its trying to find the least costly plan
to return the data in the quickest manner.
For the optimizer in this case it
the mysql query optimizer is somehow stupid
a simple query, order by with a indexed column and
you have to use where order_by_field>0 - why the
hell is mysqld not happy that a key is on the field
used in "order by"?
mysql> EXPLAIN SELECT * FROM cms1_quickbar_groups ORDER BY qg_sort ASC;
++---
