Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv4Hh-0001qy-Nz for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2013 11:02:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tv4Hg-0000hH-Ph for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2013 11:02:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv4Hg-0000hC-49 for pgsql-admin@postgresql.org; Tue, 15 Jan 2013 11:02:24 +0000 Received: from smtp-outbound-1.vmware.com ([208.91.2.12]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tv4Hd-0007VT-Gm for pgsql-admin@postgresql.org; Tue, 15 Jan 2013 11:02:23 +0000 Received: from sc9-mailhost3.vmware.com (sc9-mailhost3.vmware.com [10.113.161.73]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id D52D3284D0; Tue, 15 Jan 2013 03:02:19 -0800 (PST) Received: from zcs-prod-ext-mta-1.vmware.com (zcs-prod-ext-mta-1.vmware.com [10.113.62.223]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id D104940266; Tue, 15 Jan 2013 03:02:19 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-1.vmware.com (Postfix) with ESMTP id 660281219C4; Tue, 15 Jan 2013 03:04:29 -0800 (PST) X-Virus-Scanned: amavisd-new at zcs-prod-ext-mta-1.vmware.com Received: from zcs-prod-ext-mta-1.vmware.com ([127.0.0.1]) by localhost (zcs-prod-ext-mta-1.vmware.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcf3kSDj4IZV; Tue, 15 Jan 2013 03:04:29 -0800 (PST) Received: from zcs-prod-ext-mta-1.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-ext-mta-1.vmware.com (Postfix) with ESMTP id 7F44912199A; Tue, 15 Jan 2013 02:53:51 -0800 (PST) Received: from [192.168.1.90] (unknown [10.113.62.14]) by zcs-prod-ext-mta-1.vmware.com (Postfix) with ESMTPSA; Tue, 15 Jan 2013 02:53:49 -0800 (PST) Message-ID: <50F534C6.4000501@vmware.com> Date: Tue, 15 Jan 2013 12:51:50 +0200 From: Heikki Linnakangas Organization: VMware User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Phil Monroe CC: pgsql-admin@postgresql.org, Infrastructure , Vladimir Giverts , Tejas , Sasha Kipervarg Subject: Re: Postgres WAL Recovery Fails... And Then Works... References: <50F0CB3E.4080708@identified.com> In-Reply-To: <50F0CB3E.4080708@identified.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -6.9 (------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 12.01.2013 04:32, Phil Monroe wrote: > Hi Everyone, > > So we had to failover and do a full base backup to get our slave database back > online and ran into a interesting scenario. After copying the data directory, > setting up the recovery.conf, and starting the slave database, the database > crashes while replaying xlogs. However, trying to start the database again, the > database is able to replay xlogs farther than it initially got, but ultimately > ended up failing out again. After starting the DB a third time, PostgreSQL > replays even further and catches up to the master to start streaming > replication. Is this common and or acceptable? How did you perform the base backup? Did you use pg_basebackup? Or if you did a filesystem-level copy, did you use pg_start/stop_backup correctly? Did you take the base backup from the master server, or from another slave? This looks similar to the bug discussed here: http://www.postgresql.org/message-id/CAMkU=1wpvYJVEDo6Qvq4QbosZ+AV6BMVCf+XVCG=mJqFRjQ8Pg@mail.gmail.com. That was fixed in 9.2.2, so if you're using 9.2.1 or 9.2.0, try upgrading. - Heikki -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin