Skip site navigation (1) Skip section navigation (2)

Re: mirroring databases

From: "Derek Barrett" <derekbarrett(at)graffiti(dot)net>
To: "D(dot) Duccini" <duccini(at)backpack(dot)com>, <april(at)i-netco(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: mirroring databases
Date: 2002-07-19 02:09:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
Here is the filesystem method using rsync.

I haven't used this method myself.
----- Original Message -----
From: "D. Duccini" <duccini(at)backpack(dot)com>
Date: Thu, 18 Jul 2002 15:03:14 -0500 (CDT)
To: April L <april(at)i-netco(dot)com>
Subject: Re: [NOVICE] mirroring databases

> > What is the general method for replacing changed records and adding new
> > records, between remote locations? Assume a one-way sync, ie a mirror.
> > Records will only be added or changed at one location.
> make a 'diff' kind of file based on the changed information -- you can
> either send out the changes to a file to be processed remotely by a piece
> of software, or you can create a dump kind of file for direct import 
> of course you could also look at doing a file-level replication using
> something like rsync 
> -----------------------------------------------------------------------------
> david(at)backpack(dot)com            BackPack Software, Inc.
> +1 651.645.7550 voice       "Life is an Adventure.    
> +1 651.645.9798 fax            Don't forget your BackPack!"   
> -----------------------------------------------------------------------------
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly

Get your free email from

Powered by Outblaze


pgsql-novice by date

Next:From: April LDate: 2002-07-19 03:32:35
Subject: Re: mirroring databases
Previous:From: Josh BerkusDate: 2002-07-18 23:10:05
Subject: Re: UNICODE error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group