Janusz Krzysztofik wrote:
> ...
> I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
> ASPseek application. I decided to try InnoDB in order to be able
> to update tables while performing time consuming selects.
> After converting all tables to InnoDB I noticed a
>From MySQL Manual:
"If you want to change the number or the size of your InnoDB log files,
you have to shut down MySQL and make sure that it shuts down without
errors. Then copy the old log files into a safe place just in case
something went wrong in the shutdown and you will need them to recover
Martijn Tonies wrote:
>
> Hi,
>
> > You are not using any indicies, because there aren't any that could be
> > used in this query.
> > Try adding an index on (status,deleted)
>
> I wonder: how many possible different values would such an index
> return?
mysql> select distinct status, deleted fr
evant one).
>
> Have you done an EXPLAIN on your query ?
>
> May be an index on (origin,status,deleted) could help.
>
> Marc.
>
> -Message d'origine-
> De : Janusz Krzysztofik [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 24 novembre 2003 13:58
> A : [E
Hello,
I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
ASPseek application. I decided to try InnoDB in order to be able
to update tables while performing time consuming selects.
After converting all tables to InnoDB I noticed a big difference
in processing speed of one of the
