Hello.
For auto_increment columns MySQL sets in the binary logs INSERT_ID
variable, research binary and relay logs and check if it is set to
the same value. Is it possible that you forgot to change the
master_log_pos and master_log_file after copying the data to the slave?
PaginaDeSpud
Trying to help you with your replication problems is pretty much
impossible without more information, such as: mysql versions and a more
detailed explanation of your replication setup.
I manage setups ranging from 1-14 replication slaves transmitting up to 2
gigabytes of data per day, and none of
dì 29 dicembre 2005 9.01
A: [EMAIL PROTECTED]; [EMAIL PROTECTED]; mysql@lists.mysql.com
Oggetto: Re: inconsistent replication?
Hi,
I have had same issue for very long time - but managed.
I see this as a "bug / issue" to be handled by MySQL - because the
logfile/replicationfile should not add
Hi,
I have had same issue for very long time - but managed.
I see this as a "bug / issue" to be handled by MySQL - because the
logfile/replicationfile should not add more data then the orig SQL from program
- in this case is added the auto-increment, which is dealt with internal by
MySQL.
Bes
inale-
Da: PaginaDeSpud [mailto:[EMAIL PROTECTED]
Inviato: mercoledì 28 dicembre 2005 22.38
A: mysql@lists.mysql.com
Oggetto: inconsistent replication?
Hi,
Some hours ago i setup the replication for my cluster and it's the third
time i need to reset the replication and copy the whole database from m
Hi,
Some hours ago i setup the replication for my cluster and it's the third
time i need to reset the replication and copy the whole database from master
to slave due to errors like this:
051228 17:13:35 [ERROR] Slave: Error 'Duplicate entry '9947776' for key 1'
on query. Default database: '
from:
error=0;
to
error=1;
I will submit this patch to the maintainer of sql_delete.cc.
Thank you,
Heikki
- Original Message -
From: "Chris Tucker" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Thursday, July 03, 2003 9:42 PM
Subje
Hi,
As I understand it any statement that fails with a foreign key error should not
be written to the binlog and subsequently should not execute on the slave.
Referring to the InnoDB manual, section 4.5:
"If a statement fails, for example, because of a foreign key violation, then
the statement