Thanks. I ended up using pglogical, since I don't really need Bi-directional replication and docs for UDR suggest using pglogical instead. Although I ran into a problem there, but pglogical seems to be the answer. Regards, Nick. ----- Original Message ----- From: "Sylvain Marechal" <marechal.sylvain2@xxxxxxxxx> To: "Nick Babadzhanian" <nb@xxxxxxxx> Cc: "pgsql-general" <pgsql-general@xxxxxxxxxxxxxx> Sent: Wednesday, July 6, 2016 11:00:05 PM Subject: Re: Replication with non-read-only standby. 2016-06-30 15:15 GMT+02:00 Nick Babadzhanian <nb@xxxxxxxx>: > 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? > > Regards, > Nick. > > Hi Nick, sorry for this silly question, but I am not sure to understand why BDR is not an option. As far as I know, it was designed to handle such cases. My 2 cents, Sylvain -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
