From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | bricklen <bricklen(at)gmail(dot)com>, Bèrto ëd Sèra <berto(dot)d(dot)sera(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 21:28:21 |
Message-ID: | 1376083701.37700.YahooMailNeo@web162906.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Not only that, but she mentioned that her laptop is a Mac and the
office machine is a Linux server. A solution would probably need
to use *logical* copies like pg_dump, slony, or Londiste.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-08-09 22:06:21 | Re: plpgsql FOR LOOP CTE problem ? |
Previous Message | Peter Eisentraut | 2013-08-09 21:24:09 | Re: Pl/Python runtime overhead |