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 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq