Skip site navigation (1) Skip section navigation (2)

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: 2005-09-09 12:14:36
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3417DD2CF@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-hackers-win32pgsql-patches
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



pgsql-patches by date

Next:From: Stephan SzaboDate: 2005-09-09 14:36:15
Subject: Re: [PATCHES] Work-in-progress referential action trigger
Previous:From: Simon RiggsDate: 2005-09-09 10:24:30
Subject: Re: statement logging / extended query protocol issues

pgsql-hackers-win32 by date

Next:From: Chuck McDevittDate: 2005-09-09 18:37:37
Subject: Build with Visual Studio & MSVC
Previous:From: Oliver JowettDate: 2005-09-09 00:11:03
Subject: Re: [PATCHES] Implement support for TCP_KEEPCNT, TCP_KEEPIDLE, TCP_KEEPINTVL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group