Message-ID: <51DDA38F.1040505@zvelo.com>
Date: Wed, 10 Jul 2013 12:10:23 -0600
From: Chris Ernst <cernst@zvelo.com>
Organization: zvelo, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: Upgrading from 9.1 to 9.2 in place, same machine
References: 
 <CAOC+FBUZL60+OzFXoQZFRL42Zn2DDkyhmmOUx3SKE4Xv1y=eYQ@mail.gmail.com>
In-Reply-To: 
 <CAOC+FBUZL60+OzFXoQZFRL42Zn2DDkyhmmOUx3SKE4Xv1y=eYQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 07/10/2013 11:53 AM, Wells Oliver wrote:
> I'd like to move the 9.1 database to 9.2 without any down time, and
> ensuring that no data is lost.
> 
> My original idea was to make 9.2 a slave of 9.1, then switch it over.

You can't do this with streaming replication.  But you can with slony.
Just replicate from 9.1 as master to 9.2 as a slave.  Once they are
fully in sync, promote 9.2 to master.

Note that you will have to restart postgres at least once to move the
9.2 port to the same as the 9.1 port when you switch.  SO it won't be
zero down time, but pretty darn close.

	- Chris


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin