Re: PostgreSQL Failback without rebuild - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PostgreSQL Failback without rebuild
Date
Msg-id 20140211194200.GJ2289@momjian.us
Whole thread Raw
In response to Re: PostgreSQL Failback without rebuild  (James Sewell <james.sewell@lisasoft.com>)
List pgsql-hackers
On Fri, Feb  7, 2014 at 03:57:31PM +1100, James Sewell wrote:
> I've just noticed that on PostgreSQL 9.3 I can do the following with a master
> node A and a slave node B (as long as I have set recovery_target_timeline =
> 'latest'):
> 
>  1. Stop Node A
>  2. Promote Node B
>  3. Attach Node A as slave
> 
> This is sufficient for my needs (I know it doesn't cover a crash), can anyone
> see any potential problems with this approach?

I know some people have used rsync to get A to match B after a crash of
A and promotion of B.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [PERFORM] encouraging index-only scans
Next
From: Claudio Freire
Date:
Subject: Re: [PERFORM] encouraging index-only scans