> I'm using the same MySQL version on debian and have no problem
> setting the key_buffer size. I take it you are setting
> "key_buffer" and not "key_buffer_size" in the my.cnf file ?
> eg.
> set-variable= key_buffer=32M
Yes, this is what I'm doing.
> Are you saying that running "change mas
Hi,
I'm using the same MySQL version on debian and have no problem
setting the key_buffer size. I take it you are setting
"key_buffer" and not "key_buffer_size" in the my.cnf file ?
eg.
set-variable= key_buffer=32M
I don't know why it has a different name in the 'show variables'
list.
Are
William, Egor, thanks for your attention on this.
William is correct, on debian the standard place for my.cnf is
in /etc/mysql, and we aren't having problems not reading my.cnf
(it worked perfectly well to change the param there for the master).
In desperation, I figured I'd just redo the slave
> On Thursday 27 February 2003 05:41, Liz Derr wrote:
>
>> I'm using MySQL 3.23.49-log on Debian Linux 2.4.18-bf2.4.
>> I am using replication over ssh tunnels, and one of the slaves is
>> apparently in need of performance tuning.
>>
>> After reviewing the status and variable settings (detailed bel
On Thursday 27 February 2003 05:41, Liz Derr wrote:
> I'm using MySQL 3.23.49-log on Debian Linux 2.4.18-bf2.4.
> I am using replication over ssh tunnels, and one of the slaves is
> apparently in need of performance tuning.
>
> After reviewing the status and variable settings (detailed below) and
Hello MySQL Gurus,
I'm using MySQL 3.23.49-log on Debian Linux 2.4.18-bf2.4.
I am using replication over ssh tunnels, and one of the slaves is apparently
in need of performance tuning.
After reviewing the status and variable settings (detailed below) and the
MySQL online manual, I decided tha
