[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Replication with non-read-only standby.
From:       Scott Marlowe <scott.marlowe () gmail ! com>
Date:       2016-06-30 14:03:44
Message-ID: CAOR=d=1v6=1fgBs_1z_ymx4vtUuRuhAxWg3vOcgY-XXiczJ8bg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Jun 30, 2016 at 7:15 AM, Nick Babadzhanian <nb@cobra.ru> wrote:
> Setup:
> 2 PostgreSQL servers are geographically spread. The first one is used for an \
> application that gathers data. It is connected to the second database that is used \
> to process the said data. Connection is not very stable nor is it fast, so using \
> Bidirectional replication is not an option. It is OK if data is shipped in batches \
> rather than streamed. 
> Question:
> Is there a way to make the standby server non-read-only, so that it can keep \
> getting updates (mostly inserts) from the 'master', but users are able to edit the \
> data stored on 'slave'? Is there some alternative solution to this?

I'd probably solve this with slony.


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[prev in list] [next in list] [prev in thread] [next in thread]