Ingo Strüwing wrote:
> I tried to use your my.cnf, but still cannot
> repeat the problem.
>
> How did you get at the binary of your MySQL 5.0.18
> version?
>
We have actually figured out a workaround to the problem. Apparently, there is a bug where if you specify any value for the --with-max-indexes parameter, indexes are disabled. Our fix was to simply rebuild our binary and omit the --with-max-indexes flag.
Previously, we were using the following line to configure the build:
~~~~~~~
./configure \
--prefix=/mysql/mysql \
--datadir=/mysql/data \
--without-debug \
--with-embedded-server \
--with-extra-tools \
--with-mysqlmanager \
--with-bench \
--with-big-tables \
--without-innodb \
--with-max-indexes=128
~~~~~~~~
We redid the build using these options and it worked fine:
~~~~~~~~
./configure \
--prefix=/mysql/mysql \
--datadir=/mysql/data \
--without-debug \
--with-embedded-server \
--with-extra-tools \
--with-mysqlmanager \
--with-bench \
--with-big-tables \
--without-innodb
~~~~~~~~
For reference, here is an entry in the commits mailing list regarding the bug:
http://lists.mysql.com/commits/998
And here is a related bug report:
http://bugs.mysql.com/bug.php?id=10932