Re: Synchronize Backup to another remote database

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: kah_hang_ang(at)toray(dot)com(dot)my
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Synchronize Backup to another remote database
Date: 2006-05-22 16:45:44
Message-ID: 20060522164543.GU64371@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, May 16, 2006 at 09:35:57AM +0800, kah_hang_ang(at)toray(dot)com(dot)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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-22 16:50:27 Re: Updatable view and default sequence values
Previous Message Jim C. Nasby 2006-05-22 16:40:22 Re: Error in Access