MySQL Bugs: #39093: Warning message about wrong 'max_join

Bug #39093	Warning message about wrong 'max_join_size' value on startup
Submitted:	28 Aug 2008 13:35	Modified:	11 Sep 2008 14:28
Reporter:	Athan Dimoy	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.67	OS:	FreeBSD (7.0)
Assigned to:		CPU Architecture:	Any
Tags:	freebsd, Max_join_size, regression, startup

Description:
After upgrading to the latest MySQL (5.0.67) I've noticed that it emits the following warning whenever it starts.

[Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295

I tried without any cnf, avoiding any mistakes but still the same. The weird is that this problem only exists on my 32bit P4 testing machine. On production server (64bit-Opteron) there is no warning. BTW both machines use the same OS version, same config and most other settings.

Never had such a problem before version 5.0.67. After switched back to 5.0.51 problem disappeared.

How to repeat:
Just startup mysql.

Looks similar to bug #35346

I even tried to manually enter "max_join_size = 4294967295" in my.cnf but still getting the same warnging whenever mysqld starts.

Is it a 64-bit system?

The system where this problem occure is 32bit P4.
On 64bit Opteron everything is just fine, no warning messages.

This is on CentOS 5.2 from a test I ran on 8/8/08:

080808 15:37:01 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
080808 15:37:01 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
080808 15:37:01 - 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=0
read_buffer_size=8388608
max_used_connections=0
max_connections=4096
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 0 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbf965868, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81bd064
0x823d757
0x823d9ef
0x824cc9c
0x81be303
0x81c2115
0x736dec
0x8119ea1
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
080808 15:37:01 mysqld ended

This is a duplicate of bug #35346