X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 9BE2B9F9D99 for ; Mon, 22 May 2006 13:46:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 70163-03 for ; Mon, 22 May 2006 13:45:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 5F57B9F9B01 for ; Mon, 22 May 2006 13:45:51 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id EC4C556431; Mon, 22 May 2006 11:45:49 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 22 May 2006 11:45:47 -0500 Date: Mon, 22 May 2006 11:45:44 -0500 From: "Jim C. Nasby" To: kah_hang_ang@toray.com.my Cc: pgsql-admin@postgresql.org Subject: Re: Synchronize Backup to another remote database Message-ID: <20060522164543.GU64371@pervasive.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060522:kah_hang_ang@toray.com.my::PL5lM2QIr/ub5IUJ:000000000000 000000000000000000000000I5Wf X-Hashcash: 1:20:060522:pgsql-admin@postgresql.org::gqaaMCeEhrg/7Fho:00000000000 0000000000000000000000000hf4 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/290 X-Sequence-Number: 21822 On Tue, May 16, 2006 at 09:35:57AM +0800, kah_hang_ang@toray.com.my wrote: > Currently we want to upgrade postgresql to 8.1.3 but our current postgresql > database (v7.2.2) is use in the production line so we can't stop the > current database. > So is there any way to synchronize backup the current postgresql database > to another remote postgresql database without interrupt our current > postgresql database? You could maybe, possibly, theoretically hack Slony to run against 7.2. I know someone did this to get slony to run on 7.3. You'd want to use an old version of Slony, which means you'd only be able to go from 7.2 to 7.4. But once you were on 7.4, you could use the most recent Slony to go from 7.4 to 8.1. Another possibility is using a command-based replicator, like pgmirror, or what Continuent offers. But you need to understand the drawbacks of such a method. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461