Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id DF149632CB8 for ; Mon, 5 Apr 2010 09:30:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 73406-02 for ; Mon, 5 Apr 2010 12:29:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by mail.postgresql.org (Postfix) with ESMTP id 047CD6324EC for ; Mon, 5 Apr 2010 09:30:02 -0300 (ADT) Received: from ms5.yyz2.afilias-ops.info ([10.50.129.111] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from ) id 1NylRG-0005TO-4u; Mon, 05 Apr 2010 12:29:58 +0000 Received: from tor-gateway.afilias.info ([199.15.87.4] helo=[10.10.46.12]) by smtp.afilias.info with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NylRG-0003aX-4V; Mon, 05 Apr 2010 12:29:58 +0000 Subject: Re: Migrate postgres to newer hardware From: Brad Nicholson To: =?ISO-8859-1?Q?I=F1igo?= Martinez Lasala Cc: Renato Oliveira , pgsql-admin In-Reply-To: <1270195138.7497.9.camel@deimos> References: <7965A9DCF12CC14984420BCC37B1608F25AB1AED49@Elzar.grant.co.uk> <1269959369.15416.5.camel@deimos> <7965A9DCF12CC14984420BCC37B1608F25AB1AEE48@Elzar.grant.co.uk> <1269962795.15416.26.camel@deimos> <7965A9DCF12CC14984420BCC37B1608F25AB1AEF22@Elzar.grant.co.uk> <1270195138.7497.9.camel@deimos> Content-Type: text/plain; charset="UTF-8" Date: Mon, 05 Apr 2010 08:29:57 -0400 Message-Id: <1270470597.19810.2.camel@bnicholson-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.959 tagged_above=-10 required=5 tests=AWL=0.640, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201004/27 X-Sequence-Number: 34121 On Fri, 2010-04-02 at 09:58 +0200, I=C3=B1igo Martinez Lasala wrote: > I've never worked with Bucardo and Londiste, so I cannot give you any > hint about it. > With slony it's not necessary to restore all database prior staring > sync process. You only have to restore your schema but not data. Slony > will keep them synced with source server. >=20 > Anyway, if you plan to migrate to 8.4 there are some issues with > slony. For 8.3 and higher, you will go with slony 2.X. For 8.2 with > slony 1.X > I'm not sure if Slony 1.x is compatible with Postgres >=3D 8.3, but I'm > sure slony 2.x is not backwards compatible. Slony 1.2.17 and higher is compatible with PG 8.4. I'd go with the latest stable release though. =20 --=20 Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.