Re: Replication with non-read-only standby.
| От | Sylvain Marechal |
|---|---|
| Тема | Re: Replication with non-read-only standby. |
| Дата | |
| Msg-id | CAJu=pHSxqPNkiwO1g6GHMc+QP8ncCr9MR89yvh_xtHWY9hVLyA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Replication with non-read-only standby. (Nick Babadzhanian <nb@cobra.ru>) |
| Ответы |
Re: Replication with non-read-only standby.
|
| Список | pgsql-general |
2016-06-30 15:15 GMT+02:00 Nick Babadzhanian <nb@cobra.ru>:
Hi Nick,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.
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В списке pgsql-general по дате отправления: