Hi Martin,
Replication definitely does not ignore CREATE DATABASE all the time,
just every now and then :) I had 93 databases that made it through
replication, and the 94th failed. There aren't any binlog-ignore-db
paramaters. I've dumped the binlog out, and CREATE DATABASE did make
it into the
my Zawodny wrote:
> On Mon, Jan 13, 2003 at 02:16:23PM -0500, David Nedved wrote:
> >
> > We keep having issues where we create a new table on the master, and
> > a short while later the slave will crash because it starts trying to
> > perform queries which insert into
his. We're
not using the slaves for anything at present, but they are meant to be
a disaster recovery option. Right now they're worthless...
Thanks in advance,
David Nedved
here is the output of "show slave status" on a currently broken slave:
(sure enough the table exists on the
Hi All,
I have two qestions about the binary log files that I couldn't find the
answer to.
1.) how do you force a log switch other than startup / shutdown?
2.) when the number gets to 999 does it keep going with more digits, wrap around, or
some other behavior?
I'm running mysql-max-3.23.53a-pc
Hi All,
(sorry if this is a duplicate -- I don't think the original made it)
Running mysql 3.23.53-max binary on a RedHat 7.2 based server. Replication
is working fine, but I'm running into errors with the replicate-rewrite-db
directive. Here's a snippet from my my.cnf file on the slave:
maste
Hi All,
Running mysql 3.23.52-max binary on a RedHat 7.2 based server. Replication
is working fine, but I'm running into errors with the replicate-rewrite-db
directive. Here's a snippet from my my.cnf file on the slave:
master-port = 3306
replicate-rewrite-db=mysql->master_mysql
When I
