Description:
mysqld will not accept large values for some command line options like:
- max-seeks-for-key
- max-write-lock-count
- max_tmp_tables
- master-retry-count
- max-binlog-cache-size
- binlog-row-event-max-size
- ...
Moreover, some of these have corresponding dynamic variables, which can
be set to large values in a regular user session, much like:
SET GLOBAL max_binlog_cache_size=18446744073709547519;
Finally, mysqld --help --verbose will actually report that some of
these have large default values, that apparently cannot be set on
the CLI. At the very least, this is inconsistent.
I have found this in:
- tree: mysql-trunk-bugfixing
- revid: davi.arnaut@oracle.com-20100727132511-fx4bd0xn57p8o52h
It's possible that it also exists in older trees, like 5.1.
How to repeat:
Just start an mtr test case with one of the options above set to
a large value (according to the interval stated in the manual), eg:
./mtr --mysqld=--max-tmp-tables=18446744073709547519 main.bool
Suggested fix:
.