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

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Serial key mismatch in master and slave, while using slony
Date: 2010-12-20 14:24:49
Message-ID: AANLkTin8P5C=i_=9EQMOBoyO=H0qTrhL_pzVWu=P8e1t@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Dec 18, 2010 at 7:12 AM, Vishnu S. <vishnu(dot)s(at)nestgroup(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jorge Godoy 2010-12-20 14:24:58 Re: Copy From suggestion
Previous Message Mark Watson 2010-12-20 13:49:37 Re: Copy From suggestion