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:10:06 |
Message-ID: | CAKwGa__G=gKjUpb4F4bKM3GqbeXWc_cXeG=0AABgDtTwRdu95g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
not sure having to write stuff any time you do even the smallest thing on
your table is more reasonable of taking the pain to write (or ask friends
to help you writing) a couple of bash scripts that will do the job forever.
But then again, this is true if and only if she is the one and only user
who can create data.
On 9 August 2013 16:06, bricklen <bricklen(at)gmail(dot)com> wrote:
> On Fri, Aug 9, 2013 at 7:36 AM, Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com>wrote:
>
>> --all you need to do is switch master and slave so that "master" is the
>> one box you are currently on
>>
>
> That probably isn't a reasonable solution, considering the OP mentioned
> that she was not a professional DBA. Setting up a hot/warm standby, failing
> over, resetting the slave from the new master, lather, rinse, repeat is
> certainly scriptable but doesn't seem like the best option here.
>
> I don't know of any commercial solutions, but writing some code might be
> required. Synchronizing data isn't that difficult, but synchronizing
> changes to database table structure will be a bit tricky,
>
--
==============================
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bèrto ëd Sèra | 2013-08-09 15:12:05 | Re: bi-directional syncing help request |
Previous Message | bricklen | 2013-08-09 15:06:56 | Re: bi-directional syncing help request |