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