Re: [GENERAL] Replication with non-read-only standby.

uot; To: "Nick Babadzhanian" Cc: "pgsql-general" Sent: Wednesday, July 6, 2016 11:00:05 PM Subject: Re: [GENERAL] Replication with non-read-only standby. 2016-06-30 15:15 GMT+02:00 Nick Babadzhanian : > Setup: > 2 PostgreSQL servers are geographically spread. The fi

Re: [GENERAL] Replication with non-read-only standby.

2016-06-30 15:15 GMT+02:00 Nick Babadzhanian : > 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

Re: [GENERAL] Replication with non-read-only standby.

Il 01/07/2016 05:21, Venkata Balaji N ha scritto: On Thu, Jun 30, 2016 at 11:15 PM, Nick Babadzhanian wrote: Setup: 2 PostgreSQL servers are geographically spread. The first one

Re: [GENERAL] Replication with non-read-only standby.

On Thu, Jun 30, 2016 at 11:15 PM, Nick Babadzhanian 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

Re: [GENERAL] Replication with non-read-only standby.

On Thu, Jun 30, 2016 at 7:15 AM, Nick Babadzhanian 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

[GENERAL] Replication with non-read-only standby.

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 i