Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Oliver Jowett <oliver(at)opencloud(dot)com>
- Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, pgsql-patches(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org
- Subject: Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL
- Date: Thu, 08 Sep 2005 19:48:00 -0400
- Message-id: <26761(dot)1126223280(at)sss(dot)pgh(dot)pa(dot)us>
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Merlin Moncure wrote:
>> More
>> significantly, if you change a tcp parameter from the default, the
>> server rejects connections without a relevant error message :(.
> Could you clarify what you mean by "rejects"? Does it accept them and
> then close the connection, or does it fail to even accept the TCP
> connection?
> If the connection gets accepted, I'd expect *something* in the
> postmaster logs -- can you check?
I suspect Merlin's complaint has to do with the fact that the *user*
doesn't see any error message. The way you've coded this, setsockopt
failure during startup is treated as a communications failure and so
there's no attempt to report the problem to the client.
regards, tom lane
Home |
Main Index |
Thread Index