chris I chased this down a while back. you are correct. 4G is max on 4.0 & 4.1 versions of mysql. I don't know about 5.0 though.
I looked at the source for sql/mysqld.cc line 4170 UINT_MAX32 someone else found docs that said monty had done this since myism tables had issues deep inside the code base. so to prevent issues, simply clamped to 32 bit. I hope he has had time to change it for 5.0. maybe you could post if you find the answer to 5.0. david -----Original Message----- From: Chris Kantarjiev [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 9:55 AM To: mysql@lists.mysql.com Cc: [EMAIL PROTECTED] Subject: really big key_buffer_size (> 4GB)? I'm running 4.0.25 on NetBSD 3 on an amd64. It appears that the key_buffer_size is being truncated to 4GB, even though I've set it larger. Could someone give me a hint about where to look? I'm a little suspicious of ha_resize_key_cache() which is using longs internally to hold the keybuff_size, but I suspect this is not quite the source of the problem (there's no logic here to truncate the input value). Thanks, chris -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
