Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL
- From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Oliver Jowett" <oliver(at)opencloud(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: Fri, 9 Sep 2005 08:14:36 -0400
- Message-id: <6EE64EF3AB31D5448D0007DD34EEB3417DD2CF(at)Herge(dot)rcsinc(dot)local>
Tom Lane wrote:
> > 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.
Correct. In fact, when I posted I did completely miss the log message
due to initdb resetting log_destination. Confirmed:
LOG: setsockopt(TCP_KEEPIDLE) not supported
in server log.
Merlin
Home |
Main Index |
Thread Index