Of course, we are experiencing some serious sadness with the RANGE vs REF optimization bug, but I am hopeful that when 4.0.17 comes out all will be well again.
Tomek Dudziak wrote:
Hi,
Did anyone get the 4.0.16 binary to work on RedHat 3 Enterprise for IA64? I read that the same happens on RH3AS for AMD64.
"This was thoroughly tested with our production team and it works truly just fine. " according to MySQL support :-\
031102 22:07:17 mysqld started
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. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
031102 22:07:17 mysqld ended
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
