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
- sql,query
On Tue, 2003-01-14 at 23:55, Jeremy Zawodny wrote:
>
> What do the relevant sections of the my.cnf files on the master and
> slave look like?
> --
Hi,
I've had the same issue - but always assumed that
replication was meant to ignore "create database ...".
I've looked into it furth
On Tue, Jan 14, 2003 at 05:26:25PM -0500, David Nedved wrote:
> I've been doing a lot of poking around...
>
> the actual database is what didn't get created. The CREATE DATABASE
> statement did make it into the log file, and the slave got past that
> point without ever creating the database.
Tha
I've been doing a lot of poking around...
the actual database is what didn't get created. The CREATE DATABASE
statement did make it into the log file, and the slave got past that
point without ever creating the database.
Go figure...
On Tue, Jan 14, 2003 at 02:06:39PM -0800, Jeremy Zawodny wrot
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 the new table, but it looks as if the
> query to create
Hi All,
Trying my best to maintain some production servers running
mysql-max-3.23.53a-pc-linux-gnu-i686 with one master and one slave.
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 in
