From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Replication server timeout patch |
Date: | 2011-03-30 13:54:08 |
Message-ID: | AANLkTi=NLYT=8dMcR4fB5qvk2L7JF41KuQB_aDVpE+wN@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 30, 2011 at 4:08 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Mar 30, 2011 at 5:03 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> On 30.03.2011 10:58, Fujii Masao wrote:
>>>
>>> On Wed, Mar 30, 2011 at 4:24 PM, Heikki Linnakangas
>>> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>>> + A value of zero means wait forever. This parameter can only be
>>> set in
>>>
>>> The first sentence sounds misleading. Even if you set the parameter to
>>> zero,
>>> replication connections can be terminated because of keepalive or socket
>>> error.
>>
>> Hmm, should I change it back to "A value of zero disables the timeout" ? Any
>> better suggestions?
>
> I like that. But I appreciate if anyone suggests the better.
Maybe sticking the word "mechanism" in there would be a bit better.
"A value of zero disables the timeout mechanism"?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2011-03-30 13:59:43 | Re: Triggers on system catalog |
Previous Message | Robert Haas | 2011-03-30 13:49:26 | Re: Triggers on system catalog |