It appears that mysqld won't start if the setting for key_buffer
is more than 2GB.
Maybe you've also hit the quirks of memory management and malloc, just as
we've posted a while ago in http://lists.mysql.com/mysql/186930 ?
It seems to have been a simple issue of not unlimiting the
We're starting to use mysql (4.0.25) on an amd64 machine (running
NetBSD-3). One of the reasons for doing this is to use much more
RAM - we tend to thrash the key_buffer on i386 because one of our
indexes is 10GB in size (the table is 15GB).
It appears that mysqld won't start if the setting for
- Original Message -
From: Chris Kantarjiev [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Monday, September 19, 2005 9:06 PM
Subject: very large key_buffer on amd64?
We're starting to use mysql (4.0.25) on an amd64 machine (running
NetBSD-3). One of the reasons for doing
Maybe you've also hit the quirks of memory management and malloc, just as
we've posted a while ago in http://lists.mysql.com/mysql/186930 ?
An interesting thread, but I'm on NetBSD, not Linux. But it's some place
to start looking around, I guess.
--
MySQL General Mailing List
For list