Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id E382D632596 for ; Wed, 8 Sep 2010 14:14:26 -0300 (ADT) 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 55774-07 for ; Wed, 8 Sep 2010 17:14:19 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id 96037632450 for ; Wed, 8 Sep 2010 14:14:19 -0300 (ADT) Received: from adsl-63-195-55-98.dsl.snfc21.pacbell.net ([63.195.55.98] helo=[192.168.47.100]) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1OtODv-0001ix-BT for pgsql-testers@postgresql.org; Wed, 08 Sep 2010 10:14:17 -0700 Message-ID: <4C87C461.2010108@agliodbs.com> Date: Wed, 08 Sep 2010 10:14:09 -0700 From: Josh Berkus User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre MIME-Version: 1.0 To: pgsql-testers@postgresql.org Subject: Re: Problem with standby References: <684197.22674.qm@web1207.biz.mail.gq1.yahoo.com> In-Reply-To: <684197.22674.qm@web1207.biz.mail.gq1.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201009/5 X-Sequence-Number: 181 On 09/08/2010 05:28 AM, Jai Soni wrote: > > Dear pgsql-testers > > i have installed postgresql 9.0 beta1 and testing its streaming > replication feature > when i set up the replication env (i.e. primary and standby servers) > everything was fine and the replication goes successful but last > three-four days the standby server does not doing replication i have > appended the log messages that i received in standby server There have been a lot of fixes to Standby since Beta1. Please do try a more recent version, like RC1. The message you are getting indicates that for some reason the standby stopped replicating for a long enough period for the transaction records to be deleted on the Master. If you are not using WAL archiving as a backup for falling behind, then your only choice is to re-clone the standby. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com