Re: Sync replication + high latency server
От | Edson Richter |
---|---|
Тема | Re: Sync replication + high latency server |
Дата | |
Msg-id | BLU436-SMTP722280953CAB09B473C240CF7D0@phx.gbl обсуждение исходный текст |
Ответ на | Re: Sync replication + high latency server ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: Sync replication + high latency server
Re: Sync replication + high latency server |
Список | pgsql-general |
Em 13/08/2015 00:40, Joshua D. Drake escreveu: > > On 08/12/2015 05:33 PM, Edson Richter wrote: >> Hi! >> >> I've a situation where I would like to keep sync replication, where >> servers have 10Mbps network connection but high latency (normally, ~20ms >> but sometimes, 1000ms~2000ms, even 3000ms when network is under load). >> >> Considering that I will keep enough WAL files (let's say, 200 WAL >> segments on a server with low write rate): >> >> What happens if I configure timeout in master server for, let's say, 10 >> seconds? >> Will sync replication survive if timeout happens, and then, network >> "recover" it self? > > I think you are misunderstanding how sync rep works. I don't think so: sync replication will force commit on both databases before returning OK to my app server. > >> >> Or will I be obligated to use async replication in such scenario? >> > > async is your friend here. And what about the timeout when using sync replication? What will happen? Thanks, Edson > > JD > >
В списке pgsql-general по дате отправления: