Thread: Serial key mismatch in master and slave, while using slony

***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

On Sat, Dec 18, 2010 at 7:12 AM, Vishnu S. <vishnu.s@nestgroup.net> wrote:
> I am using Slony-I slony-I-2.0.2 in windows .I have a master and a slave
> machine. The replication is working fine. When the master switches to slave
> , there exists a serial key mismatch in master and slave machines. So
> insertion fails in the slave machines. I am using the failover command to
> switch the slave to master.  Now the error message shown is  ‘Duplicate key
> violation’. On selecting the next value of the serial key the value shown is
> different from the actual value. Ie the shown value is very much less than
> the number of records in the table.

Why failover?  Is the master dead?

Are you syncing your sequences?  Is the duplicate a result of trying
to insert the primary key based on some sequence?  Clearly some data
is not fully synchronized when you did your failover.

Also, there is a whole mailing list dedicated to slony replication.
Take your question over there for best reach of people who can help
you.