Bug #33382 set global var=default allows invalid values
Submitted: 19 Dec 2007 20:25 Modified: 21 May 2008 8:27
Reporter: Sergei Golubchik Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0+ OS:Any
Assigned to: Sergei Golubchik CPU Architecture:Any
Triage: D3 (Medium)

[19 Dec 2007 20:25] Sergei Golubchik
bug#31177 fixed almost all cases when an invalid default value of an option could have an effect, but one case was missed:

How to repeat:
set global myisam_max_sort_file_size=default;
[19 Dec 2007 20:28] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:


ChangeSet@1.2583, 2007-12-19 21:31:04+01:00, serg@janus.mylan +3 -0
  correct invalid values in SET GLOBAL var=DEFAULT
[28 Jan 2008 6:40] Bugs System
Pushed into 6.0.5-alpha
[28 Jan 2008 6:51] Bugs System
Pushed into 5.1.24-rc
[28 Jan 2008 6:52] Bugs System
Pushed into 5.0.56
[6 Mar 2008 15:38] Jon Stephens
Documented in the 5.0.56, 5.1.23-ndb-6.2.14, 5.1.24, and 6.0.5 changelogs as follows:

        SET GLOBAL myisam_max_sort_file_size=DEFAULT set
        myisam_max_sort_file_size to an incorrect value.

Let bug status as PP.
[2 Apr 2008 16:06] Jon Stephens
Fix also noted in the 5.1.23-ndb-6.3.11 changelog.
[2 Apr 2008 16:06] Jon Stephens
Can this bug be closed now? Thanks!
[21 May 2008 8:27] Jon Stephens
Closed per email discussion with Paul.