Message-ID: <54B00F36.70801@pinpointresearch.com>
Date: Fri, 09 Jan 2015 09:26:14 -0800
From: Steve Crawford <scrawford@pinpointresearch.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Rob Cowell <rob.cowell@transversal.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Replicating from 9.1.10 into 9.3.5
References: <1Y9dC8-0002qL-2Y@l31.mail.transversal.net>
In-Reply-To: <1Y9dC8-0002qL-2Y@l31.mail.transversal.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 01/09/2015 09:17 AM, Rob Cowell wrote:
> Hi,
>
> Is it possible to set up replication from a 9.1.10 master to  a 9.3.5 slave?
For streaming log-based replication the answer is no:
>     FATAL:  database files are incompatible with server
>     DETAIL:  The database cluster was initialized with PG_CONTROL_VERSION 903, but the server was compiled with PG_CONTROL_VERSION 937.
>
> Would I be better off dumping the data from 9.1.10 and re-importing into 9.3.5, then starting replication ?
> (or is there an easier way?) :)
There are lots of options. IIRC, Slony can be used for cross-version 
replication. Pg_upgrade can be used instead of a dump and restore. Which 
is easiest depends on your operational constraints.

Of all the methods, "old-reliable" is a dump and restore. Set up 
replication after that. Be sure to use pg_dump from the *new* version to 
take the dump from the old database. And if you are going through the 
effort to upgrade, consider 9.4.0 at this point.

There is work to support statement-based replication which will probably 
support replication-based upgrades in the future. But not from your version.

Cheers,
Steve


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