Hi,
My 2 cents about this inline.
Peter Boros
On 5/6/11 1:50 PM, Reindl Harald wrote:
Am 06.05.2011 13:26, schrieb J M:
Config:
Running on 8G Server.. Currently utilizing 7G.. running only mysql..
[mysqld]
port= 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key
> From: h.rei...@thelounge.net
> To: mysql@lists.mysql.com
> Subject: Re: Input needed...
>
> Am 06.05.2011 13:26, schrieb J M:
> > Config:
> >
> > Running on 8G Server.. Currently utilizing 7G.. running only mysql..
>
> > [mysqld]
Am 06.05.2011 13:26, schrieb J M:
> Config:
>
> Running on 8G Server.. Currently utilizing 7G.. running only mysql..
> [mysqld]
> port= 3306
> socket = /var/lib/mysql/mysql.sock
> skip-locking
> key_buffer_size = 384M
depends on the size of all yur keys
> max_allowed_packet
Inhalt uebernehmen.
> Date: Fri, 6 May 2011 07:26:20 -0400
> Subject: Re: Input needed...
> From: jerom...@gmail.com
> To: h.rei...@thelounge.net
> CC: mysql@lists.mysql.com
>
> Config:
>
> Running on 8G Server.. Currently utilizing 7G.. running only m
Config:
Running on 8G Server.. Currently utilizing 7G.. running only mysql..
[client]
port= 3306
socket = /var/lib/mysql/mysql.sock
[mysqld]
port= 3306
socket = /var/lib/mysql/mysql.sock
skip-locking
key_buffer_size = 384M
max_allowed_packet = 1M
table_
please post your my.cnf settings becuase stats are useless without
knowing the configuration and without knowing your hardware (memory!)
nobody can say what buffers are making sense
i would use "mysqltuner.pl" because it shows in the most cases good advises
Am 05.05.2011 20:42, schrieb J M:
> Hi
On Saturday 12 January 2002 20:53, Jeremy Zawodny wrote:
> On Fri, Jan 11, 2002 at 08:08:51AM -0800, Kyle Hayes wrote:
> > We write our own replication system using our own checkpointing and
> > code. We start with the update logs (we're not happy about the
> > future removal of the update logs b
On Fri, Jan 11, 2002 at 08:08:51AM -0800, Kyle Hayes wrote:
> We write our own replication system using our own checkpointing and
> code. We start with the update logs (we're not happy about the
> future removal of the update logs because of this). I've looked
> through the MySQL source to see
Hi!
Two-way replication is complex, and even more difficult is coping with
broken communications.
MySQL only supports one-way replication (master -> slaves). Auto-inc column
values are communicated in the binlog to the slaves.
Some ideas:
- Generate primary keys where you concatenate the id of
On Thursday 10 January 2002 17:22, Matthew Walker wrote:
> Where I work, we're at the point of needing to maintain two database
> servers, one inhouse, and the other at another physical location. We
> need to replicate between the servers, to keep them both up to date, as
> both will be getting up
10 matches
Mail list logo
