Re: bi-directional syncing help request

From: Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: Paula Kirsch <pl(dot)kirsch(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: bi-directional syncing help request
Date: 2013-08-09 15:38:05
Message-ID: CAKwGa__AWC6tGxPJheMMm-Xst25rfb_H6_ZSJGgshK3T8H1p0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmail(dot)com> wrote:

> On Fri, Aug 9, 2013 at 8:12 AM, Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Quentin Hartman 2013-08-09 15:49:25 Re: How To Install Extension Via Script File?
Previous Message Quentin Hartman 2013-08-09 15:33:02 Re: Weird error when setting up streaming replication