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.
pgsql-patches by date
|Next:||From: Stephan Szabo||Date: 2005-09-09 14:36:15|
|Subject: Re: [PATCHES] Work-in-progress referential action trigger|
|Previous:||From: Simon Riggs||Date: 2005-09-09 10:24:30|
|Subject: Re: statement logging / extended query protocol issues|
pgsql-hackers-win32 by date
|Next:||From: Chuck McDevitt||Date: 2005-09-09 18:37:37|
|Subject: Build with Visual Studio & MSVC|
|Previous:||From: Oliver Jowett||Date: 2005-09-09 00:11:03|
|Subject: Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL|