Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 2F3491337B88
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 18 Dec 2010 10:53:36 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 37054-10 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Sat, 18 Dec 2010 14:53:28 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-iw0-f174.google.com (mail-iw0-f174.google.com
	[209.85.214.174])
	by mail.postgresql.org (Postfix) with ESMTP id E8E4D1337B51
	for <pgsql-admin@postgresql.org>; Sat, 18 Dec 2010 10:53:27 -0400 (AST)
Received: by iwn9 with SMTP id 9so1720288iwn.19
	for <pgsql-admin@postgresql.org>; Sat, 18 Dec 2010 06:53:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:subject:mime-version
	:content-type:from:in-reply-to:date:cc:content-transfer-encoding
	:message-id:references:to:x-mailer;
	bh=Lr0RhCTSs2B0TuLgxuk/eiwAOZNwr6fmIVELlRr6/9g=;
	b=tcrJs3iXKLee8onn8CVog4wlYz1khcO8SfDCaRoRCW8lyI5k1YRWuav+41/P0TpGDz
	dUVQepS9r043+IAv42hs1PZTgsrqBauLgSFYs7Le5YxzKoRd6IvXqbjfmOHfwnPfJ1xx
	tj6XEcEHDUk7TU3TkZIvs5XQNjCKt4+a/s2Sw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=subject:mime-version:content-type:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to:x-mailer;
	b=fu8yI6F16qJsd4WxZmpjvFf+WRt13cNSW9oCebFsa1UruTrzEFAgwCJqETPF9lRd5X
	yEkSFFko7l7jykPIUzBUkatSTJKGbyIfUyhj34q9JLZ+SRrALN2h1gtdtZpdFgcwF3SZ
	u54+ixg0s1tQ/n/JY2ckMVc0CWs7MbSBVV4po=
Received: by 10.42.220.136 with SMTP id hy8mr2083972icb.380.1292684008183;
	Sat, 18 Dec 2010 06:53:28 -0800 (PST)
Received: from [192.168.1.2] ([122.170.41.141])
	by mx.google.com with ESMTPS id gy41sm1405363ibb.5.2010.12.18.06.53.24
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Sat, 18 Dec 2010 06:53:26 -0800 (PST)
Subject: Re: Serial key is different in master and slave machine
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Vibhor Kumar <vibhor.aim@gmail.com>
In-Reply-To: 
 <D0124DE0373A744CA8192AFA82C831170216EA83@mail-4.tvm.nestgroup.net>
Date: Sat, 18 Dec 2010 20:23:20 +0530
Cc: <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B18A799-CCCD-42B2-90FB-3991F7533CC4@gmail.com>
References: <D0124DE0373A744CA8192AFA82C83117558EFC@mail-4.tvm.nestgroup.net>
	<21EEFF80-C6CB-451B-A87C-95D5B82F72FD@gmail.com>
	<D0124DE0373A744CA8192AFA82C831170216EA83@mail-4.tvm.nestgroup.net>
To: Vishnu S. <vishnu.s@nestgroup.net>
X-Mailer: Apple Mail (2.1082)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7
X-Spam-Level: 
X-Archive-Number: 201012/118
X-Sequence-Number: 36347


On Dec 18, 2010, at 5:55 PM, Vishnu S. wrote:

>=20
>=20
> Hi,
>=20
>=20
> I am usinf Slony slony-I-2.0.2 in windows. I have a Master and a slave
> machine. When the master machine is failed, I have executed the =
failover
> script and the slave is switched to master. My problem is that while
> inserting a record into the current master machine, it will show an
> error saying that Duplicate key value. Please help me to overcome this
> error

This means you haven't replicated the Sequences using Slony on Slave.

To overcome this problem, you have reset the sequences on New Master =
using Following command:
 SELECT pg_catalog.setval('<sequencenumber>', <nextvalof sequence on Old =
Master>, true);

Thanks & Regards,
Vibhor Kumar (PCP & OCP)
ITIL V3 Cerftified.