Re: BUG #7534: walreceiver takes long time to detect n/w breakdown

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Дата
Msg-id CAHGQGwE+vpwh6JteEggpgk5Pq45w+-os5T9OQ5vGUhbO9L8iQw@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #7534: walreceiver takes long time to detect n/w breakdown  (amit.kapila@huawei.com)
Ответы Re: BUG #7534: walreceiver takes long time to detect n/w breakdown  (Amit Kapila <amit.kapila@huawei.com>)
Список pgsql-bugs
On Wed, Sep 12, 2012 at 8:54 PM,  <amit.kapila@huawei.com> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      7534
> Logged by:          Amit Kapila
> Email address:      amit.kapila@huawei.com
> PostgreSQL version: 9.2.0
> Operating system:   Suse 10
> Description:
>
> 1. Both master and standby machine are connected normally,
> 2. then you use the command: ifconfig ip down; make the network card of
> master and standby down,
>
> Observation
> master can detect connect abnormal, but the standby can't detect connect
> abnormal and show a connected channel long time.

What about setting keepalives_xxx libpq parameters?
http://www.postgresql.org/docs/devel/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS

Keepalives are not a perfect solution for the termination of connection, but
it would help to a certain extent. If you need something like
walreceiver-version
of replication_timeout, such feature has not been implemented yet. Please feel
free to implement that!

Regards,

--
Fujii Masao

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: BUG #7534: walreceiver takes long time to detect n/w breakdown
Следующее
От: Mike Toews
Дата:
Сообщение: Re: initdb.exe changes --locale option