X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E13F111F6F3B for ; Fri, 21 Apr 2006 01:02:32 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 1.292 X-Spam-Level: * X-Spam-Status: No, score=1.292 required=5 tests=[AWL=-0.627, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_POST=1.44] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id pTcIucJxeS6z for ; Fri, 21 Apr 2006 01:02:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx1.surnet.cl (mx1.surnet.cl [216.155.73.180]) by postgresql.org (Postfix) with ESMTP id AA1B311F77F7 for ; Fri, 21 Apr 2006 01:02:28 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx1.surnet.cl with ESMTP; 21 Apr 2006 00:02:25 -0400 X-IronPort-AV: i="4.04,143,1144036800"; d="scan'208"; a="55448641:sNHT18158828" Received: from alvh.no-ip.org (200.126.99.223) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 443B7DDC00150821; Fri, 21 Apr 2006 00:02:25 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 62BFBC2DC6F; Fri, 21 Apr 2006 00:02:24 -0400 (CLT) Date: Fri, 21 Apr 2006 00:02:24 -0400 From: Alvaro Herrera To: Benjamin Krajmalnik Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Howto: Using PITR recovery for standby replication Message-ID: <20060421040224.GM5426@surnet.cl> Mail-Followup-To: Benjamin Krajmalnik , Tom Lane , pgsql-admin@postgresql.org References: <443F9BF3.4060101@laposte.net> <1145028323.5597.1.camel@localhost.localdomain> <443FDF05.4060600@laposte.net> <20060421014243.GR49405@pervasive.com> <8511B4970E0D124898E973DF496F9B4357E0F4@stash.stackdump.local> <2764.1145588998@sss.pgh.pa.us> <8511B4970E0D124898E973DF496F9B4357E0F5@stash.stackdump.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8511B4970E0D124898E973DF496F9B4357E0F5@stash.stackdump.local> User-Agent: Mutt/1.5.11+cvs20060330 X-Archive-Number: 200604/216 X-Sequence-Number: 21385 Benjamin Krajmalnik wrote: > The particular table which was problematic (and for which I posted > another message due to the unique constraint violation which I am > seeing intermittently) is the one with the high insertion rate. The > sequence is currently being used to facilitate purginf of old records. How are you creating the dumps of the sequence and the table? If you do both separately (as in two pg_dump invocations with a -t switch each), that could explain your problem. This shouldn't really happen however, because the sequence dump should be emitted in a dump of the table, if the field is really of SERIAL or BIGSERIAL type. However I don't see any other way which would make the sequence go out of sync. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support