MySQL warns that a numeric option value is out of range and has been auto-adjusted to the closest unsigned long long limit.
MySQL Error 82: EE_ADJUSTED_ULONGLONG_VALUE_FOR_OPTION appears when you set a numeric system variable (for example, max_connections) to a value outside its allowed 0-18,446,744,073,709,551,615 range. MySQL silently clips the value and returns this warning. Supply a valid in-range value to clear it.
option '%s': value %s adjusted to %s. EE_ADJUSTED_ULONGLONG_VALUE_FOR_OPTION was added in 8.0.13.
MySQL raises Error 82 (symbol EE_ADJUSTED_ULONGLONG_VALUE_FOR_OPTION) when you pass an unsigned integer option that exceeds its permitted bounds. The server keeps running but issues a global warning stating that the supplied value has been reduced or increased to the nearest legal value.
Because the warning is non-fatal, the server starts with the adjusted configuration.
However, unexpected runtime behavior can follow if you assume the original value was accepted.
The symbol EE_ADJUSTED_ULONGLONG_VALUE_FOR_OPTION first appeared in MySQL 8.0.13 to offer clearer feedback for over-sized numeric assignments. Older versions either failed silently or produced generic messages.
Ignoring the warning leaves the server running with a different configuration than intended, possibly masking performance issues or security limits.
Clearing the warning guarantees that the active settings match your configuration files and deployment scripts.
.
For many global variables, MySQL prefers availability. It clips values to safe limits so the server can start, logging a warning for administrators to review.
No. It is logged as a warning. Your application continues to run, but with a possibly unintended configuration.
Galaxy’s results pane surfaces server warnings after each query. You immediately see Error 82 when a SET statement clips a value, letting you correct it before committing.
Yes. Supplying negative numbers or anything lower than the documented minimum is also adjusted upward and reported with Error 82.