Re: bi-directional syncing help request - Mailing list pgsql-general

From Bèrto ëd Sèra
Subject Re: bi-directional syncing help request
Date
Msg-id CAKwGa__AWC6tGxPJheMMm-Xst25rfb_H6_ZSJGgshK3T8H1p0w@mail.gmail.com
Whole thread Raw
In response to Re: bi-directional syncing help request  (bricklen <bricklen@gmail.com>)
List pgsql-general
>A pg_dump from one system or the other will effectively overwrite the database it is restored to, so any changes in one system or the other will be lost 
yes, as said, the pre-condition is that she is the one and only possible data producer.


On 9 August 2013 16:24, bricklen <bricklen@gmail.com> wrote:
On Fri, Aug 9, 2013 at 8:12 AM, Bèrto ëd Sèra <berto.d.sera@gmail.com> wrote:
or you can just take a full dump from one box and import it on the other any time you switch. If it's not a big db it should probably be quicker than any alternative approach.

A pg_dump from one system or the other will effectively overwrite the database it is restored to, so any changes in one system or the other will be lost unless processes are put in place to move that data to a staging area before the reload.
The issue here is that it is a data and structure synchronization problem, which isn't something solved very easily using Postgresql's core tools.  Synchronizing the data using Bash/Python, FDW's etc is reasonably straightforward, but synchronizing the DDL changes will require some care.





--
==============================
If Pac-Man had affected us as kids, we'd all be running around in a darkened room munching pills and listening to repetitive music.

pgsql-general by date:

Previous
From: Quentin Hartman
Date:
Subject: Re: Weird error when setting up streaming replication
Next
From: Quentin Hartman
Date:
Subject: Re: How To Install Extension Via Script File?