Bug #39494 please support >4GB key_buffer_size on windows

• Submitted: 17 Sep 2008 7:58
• Modified: 18 Dec 2008 16:46
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.x, 6.x
• OS: Windows (64-bit)
• Assigned to: Vladislav Vaintroub
• CPU Architecture: Any
• Tags: key_buffer_size

[17 Sep 2008 7:58] Shane Bester

Description:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_key_buff... says this 

"The maximum allowable setting for key_buffer_size is 4GB on 32-bit platforms. As of MySQL 5.0.52, values larger than 4GB are allowed for 64-bit platforms (except 64-bit Windows, for which large values are truncated to 4GB with a warning)"

why except windows?  windows has no problems with >4G allocations.

How to repeat:
mysqld-nt --key_buffer_size=5G

Suggested fix:
implement the code to enable large key cache on windows.

[17 Sep 2008 8:37] Sveta Smirnova

Thank you for the report.

Verified as described.

[19 Nov 2008 15:03] 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:

  http://lists.mysql.com/commits/59240

2719 Vladislav Vaintroub	2008-11-19
       Bug#39494 : key_buffer_size > 4GB does not work on 64 bit Windows
      
      Cache size  is truncated via 32bit ulong  in  ha_init_key_cache() and 
      ha_resize_key_cache() 
      
      This change fixes the cast to size_t instead of ulong. This cast is safe,
      because key_buffer_size parameter is limited to SIZE_T_MAX

[21 Nov 2008 8:54] 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:

  http://lists.mysql.com/commits/59478

2942 Vladislav Vaintroub	2008-11-21 [merge]
      merge fix for bug#39494 from 5.1

[8 Dec 2008 10:23] Bugs System

Pushed into 5.1.31  (revid:[e-mail]-20081119150238-zlt9nwkbvvrzysu5) (version source revid:[e-mail]-20081126180318-v685u61mpgoc176x) (pib:5)

[8 Dec 2008 11:34] Bugs System

Pushed into 6.0.9-alpha  (revid:[e-mail]-20081121085318-m5wtvz772gwqz4oi) (version source revid:[e-mail]-20081121151447-dtf2ofz2ys0zqed1) (pib:5)

[18 Dec 2008 16:46] Paul DuBois

Noted in 5.1.31, 6.0.9 changelogs.

On 64-bit Windows systems, the server accepted key_buffer_size values
larger than 4GB, but allocated less. (For example, specifying a value
of 5GB resulted in 1GB being allocated.)

[19 Jan 2009 11:26] Bugs System

Pushed into 5.1.31-ndb-6.2.17 (revid:[e-mail]-20090119095303-uwwvxiibtr38djii) (version source revid:[e-mail]-20090108105244-8opp3i85jw0uj5ib) (merge vers: 5.1.31-ndb-6.2.17) (pib:6)

[19 Jan 2009 13:04] Bugs System

Pushed into 5.1.31-ndb-6.3.21 (revid:[e-mail]-20090119104956-guxz190n2kh31fxl) (version source revid:[e-mail]-20090119104956-guxz190n2kh31fxl) (merge vers: 5.1.31-ndb-6.3.21) (pib:6)

[19 Jan 2009 16:10] Bugs System

Pushed into 5.1.31-ndb-6.4.1 (revid:[e-mail]-20090119144033-4aylstx5czzz88i5) (version source revid:[e-mail]-20090119144033-4aylstx5czzz88i5) (merge vers: 5.1.31-ndb-6.4.1) (pib:6)

[2 Apr 2009 10:28] Anurag Shekhar

closed Bug#38834, duplicate of this bug.