Re: Timeout and wait-forever in sync rep
От | Fujii Masao |
---|---|
Тема | Re: Timeout and wait-forever in sync rep |
Дата | |
Msg-id | AANLkTimM1m+k62OU_etqjbJjdc2MG65wzP3RrU=0bC0m@mail.gmail.com обсуждение исходный текст |
Ответ на | Timeout and wait-forever in sync rep (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: Timeout and wait-forever in sync rep
|
Список | pgsql-hackers |
On Fri, Oct 15, 2010 at 9:41 PM, Fujii Masao <masao.fujii@gmail.com> wrote: > The timeout doesn't oppose to 'wait-forever'. Even if you choose 'wait > -forever' (i.e., you set allow_standalone_master to false), the master > should detect the standby crash as soon as possible by using the > timeout. For example, imagine that max_wal_senders is set to one and > the master cannot detect the standby crash because of absence of the > timeout. In this case, even if you start new standby, it will not be > able to connect to the master since there is no free walsender slot. > As the result, the master actually waits forever. This occurred to me that the timeout would be required even for asynchronous streaming replication. So, how about implementing the replication timeout feature before synchronous replication itself? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: