pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Phil Monroe <phil@identified.com>
Cc: pgsql-admin@postgresql.org, Infrastructure <infrastructure@identified.com>
Cc: Vladimir Giverts <vlad@identified.com>
Cc: Tejas <tejas@identified.com>
Cc: Sasha Kipervarg <sasha@identified.com>
Subject: Re: Postgres WAL Recovery Fails... And Then Works...
Date: Tue, 15 Jan 2013 12:51:50 +0200
Message-ID: <50F534C6.4000501@vmware.com> (raw)
In-Reply-To: <50F0CB3E.4080708@identified.com>
References: <50F0CB3E.4080708@identified.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

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..... 
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



view thread (8+ messages)  latest in thread

Message-ID: <50F534C6.4000501@vmware.com>
Permalink:  ../50F534C6.4000501@vmware.com/
Also on:    postgresql.org/message-id/50F534C6.4000501@vmware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: hlinnakangas@vmware.com, phil@identified.com, infrastructure@identified.com, vlad@identified.com, tejas@identified.com, sasha@identified.com
  Subject: Re: Postgres WAL Recovery Fails... And Then Works...
  In-Reply-To: <50F534C6.4000501@vmware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox