hi everyone.
sometimes it happens, that the slave mysql server dies because a floating point
exception.
on the console where I started the slave mysql daemon I get the error:
/usr/local/mysql/bin/safe_mysqld: line 274: 24423 Floating point
exception$NOHUP_NICENESS $ledir/$MYSQLD $defaults --b
Hello everybody!
I've just switched from version 3.23.29a-gamma to 3.23.35 and noticed
a very high system load increase. As I switched back, everything worked
fine again.
Can anyone agree with this?
As I'm using the replication feature I like to use always
a recent version. This host is a maste
s,
Martin
--
......Martin Mrvka, Research & Development
..SMS Internet-Dienstleistung GmbH
...Sporgasse 25/2, A-8010 Graz
..Tel./Fax.: +43 316 81 33 80 DW
hi!
make sure you have the dbi module configured with mysql.
use this syntax:
use DBI;
$dbh = DBI->connect("dbi:mysql:rushload:leader","richard", "passwd");
>Can someone tell me whats worng with my syntax:
>
>use DBI;
>$dbh = DBI->connect("DBI:mysql:rushload\@leader","richard", "passwd");
>
>
Hi!
I'm using mysql version 3.23.29a under a heavy loaded production
environment. Now I've set up our mysql server as replication master and
installed second mysql machine to be the slave.
Replications as itself works, but how do I get the slave server in sync with
the master without shutting do
